Brother International HL-3400CN Network Users Manual - English - Page 155

LAT Troubleshooting, the /usr/spool directory to make sure that you have created a valid spool

Page 155 highlights

CHAPTER 13 TROUBLESHOOTING LAT Troubleshooting If you cannot print from a VMS system and you have checked the hardware and network as described in the previous steps, then check the following (note that it is always a good idea to try creating a new queue with a different LAT port to reduce the possibility of setup errors): 1. If the queue pauses when you try to print, check that the print server node name and port name (or service name) agree with the names defined for the VMS print queue in LATCP or for ULTRIX print queue in the /etc/printcap file (ts parameter) and lcp -s command. The names MUST EXACTLY agree in order for printing to work. 2. Make sure LAT is enabled for outgoing connections. For VMS, enter LATCP and type SHOW NODE at the Latcp> prompt. The display should show Outgoing Connections Enabled. If it does not, you should type SET NODE/CONNECTIONS=BOTH. If you are using ULTRIX, make sure that you have started LAT with the lcp -s command and that you have enabled host-initiated connections with the lcp -h command. 3. Make sure that there are no duplicate LAT node names or LAT port numbers. Try changing the node name to a different name and/or creating a different LAT port to fix the problem. Also avoid having multiple print queues that use the same LAT port. 4. If you are running ULTRIX, make sure that the /etc/printcap file is typed in correctly. In particular, look for missing ":" and "\" characters, because a small error anywhere in the file can have major consequences. Also check the /usr/spool directory to make sure that you have created a valid spool directory. 5. If you are running ULTRIX, check your tty device to make sure that : • The tty is a valid LAT tty (execute the command file /dev/tty* | grep LAT and observe if the device has a "39" in its description). • The device is in the /etc/ttys file and in the /dev directory. • The same tty number was entered throughout the configuration process. 6. Intermittent random queue pauses can be caused if the VMS LAT port is not set up as spooled device. Type SHOW DEVICE LTAxxx from the VMS console; if the device is not spooled, type SET DEVICE/SPOOL LTAxxx command. (One exception: PATHWORKS for MACINTOSH queues should not be set up with the LTA device set as spooled). 13-19

  • 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
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168

CHAPTER 13 TROUBLESHOOTING
13-19
LAT Troubleshooting
If you cannot print from a VMS system and you have checked the hardware and
network as described in the previous steps, then check the following (note that it is
always a good idea to try creating a new queue with a different LAT port to reduce
the possibility of setup errors):
1.
If the queue pauses when you try to print, check that the print server node
name and port name (or service name) agree with the names defined for the
VMS print queue in LATCP or for ULTRIX print queue in the /etc/printcap
file (ts parameter) and lcp -s command. The names MUST EXACTLY agree
in order for printing to work.
2.
Make sure LAT is enabled for outgoing connections. For VMS, enter
LATCP and type SHOW NODE at the Latcp> prompt. The display should
show Outgoing Connections Enabled. If it does not, you should type SET
NODE/CONNECTIONS=BOTH. If you are using ULTRIX, make sure that
you have started LAT with the lcp -s command and that you have enabled
host-initiated connections with the lcp -h command.
3.
Make sure that there are no duplicate LAT node names or LAT port
numbers. Try changing the node name to a different name and/or creating a
different LAT port to fix the problem. Also avoid having multiple print
queues that use the same LAT port.
4.
If you are running ULTRIX, make sure that the /etc/printcap file is typed in
correctly. In particular, look for missing ":" and "\" characters, because a
small error anywhere in the file can have major consequences. Also check
the /usr/spool directory to make sure that you have created a valid spool
directory.
5.
If you are running ULTRIX, check your tty device to make sure that :
The tty is a valid LAT tty (execute the command file /dev/tty* | grep
LAT and observe if the device has a "39" in its description).
The device is in the /etc/ttys file and in the /dev directory.
The same tty number was entered throughout the configuration process.
6.
Intermittent random queue pauses can be caused if the VMS LAT port is not
set up as spooled device. Type SHOW DEVICE LTAxxx from the VMS
console; if the device is not spooled, type SET DEVICE/SPOOL LTAxxx
command. (One exception:
PATHWORKS for MACINTOSH queues
should not be set up with the LTA device set as spooled).