Lexmark E322 User's Guide - Page 103

Troubleshooting, Settings, Control Panel, Network, Protocols. Look for TCP/IP or DLC LexLink.

Get Lexmark E322 - Printer - B/W PDF manuals and user guides
UPC - 734646512169
View all Lexmark E322 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 103 highlights

Troubleshooting At the server, do these steps in the order shown before you call the Customer Support Center. 1 Make sure you are using TCP/IP for communications between the Windows server and the MarkNet print server. For Windows NT Server 4.x or Windows 2000, use either TCP/IP or LexLink. 2 Press the operator panel button with a brief button press to print a network settings page. Look under the TCP/IP heading on the network setup page to see if the TCP/IP protocol is turned on (activated) in the print server. If TCP/IP is turned off, use the IPX protocol to activate it. Select the printer and then select the TCP/IP task. Check the Enable box to activate TCP/IP. 3 Verify that the protocol that you are trying to use is installed properly on the server. (Hint: Start, Settings, Control Panel, Network, Protocols). Look for TCP/IP or DLC (LexLink). 4 Issue a ping command to the print server. ping 157.184.8.231 5 Establish an FTP session with the print server. ftp 157.184.8.231 6 Using the FTP "put" command, print a file. The file you use with FTP can be in PCL or PostScript emulations, PDF, HTML or any other language the printer understands. If the file prints, this confirms the TCP/IP protocol is working properly in the MarkNet print server. put mytest.ps or put mytest.txt 7 Reset both the print server and the printer. 8 If possible, shut down Windows NT Server and restart the server. There could be a spooler problem that requires a restart. 9 Try printing again. 101

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
101
Troubleshooting
At the server, do these steps in the order shown
before
you call the Customer Support Center.
1
Make sure you are using TCP/IP for communications between the Windows server and the
MarkNet print server. For Windows NT Server 4.x or Windows 2000, use either TCP/IP or
LexLink.
2
Press the operator panel button with a brief button press to print a network settings page.
Look under the TCP/IP heading on the network setup page to see if the TCP/IP protocol is
turned on (activated) in the print server.
If TCP/IP is turned off, use the IPX protocol to activate it. Select the printer and then select the
TCP/IP task. Check the Enable box to activate TCP/IP.
3
Verify that the protocol that you are trying to use is installed properly on the server. (Hint: Start,
Settings, Control Panel, Network, Protocols). Look for TCP/IP or DLC (LexLink).
4
Issue a ping command to the print server.
ping
157.184.8.231
5
Establish an FTP session with the print server.
ftp
157.184.8.231
6
Using the FTP “put” command, print a file. The file you use with FTP can be in PCL or
PostScript emulations, PDF, HTML or any other language the printer understands. If the file
prints, this confirms the TCP/IP protocol is working properly in the MarkNet print server.
put mytest.ps
or
put mytest.txt
7
Reset both the print server and the printer.
8
If possible, shut down Windows NT Server and restart the server. There could be a spooler
problem that requires a restart.
9
Try printing again.