IBM 6400-I15 User Manual - Page 110

Is the Ethernet Interface

Get IBM 6400-I15 PDF manuals and user guides View all IBM 6400-I15 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 110 highlights

• When defining a new "printer name" within PCONSOLE, did you use a pre-defined destination/queue rather than a name of your own? By default, the Ethernet Interface only recognizes names like "d1prn." All other names will be ignored by the device. • Is the Ethernet Interface in Bindery mode as seen under the "list pserver" output on the device? If servicing only a NetWare 3.x file server, it must be set to handle Bindery services. The default setting is Bindery. • Is there an available NetWare user license for the Ethernet Interface to use while it acts as a PSERVER? Every PSERVER takes up one user license since it logs in to the Novell file server. • Have you given the connection process some time after repowering the Ethernet Interface? In larger Novell environments, the file server identification and connection process can take several minutes. NetWare 4.x - No PSERVER Connection • Has the Ethernet Interface been power cycled once the PCONSOLE steps were completed? This will make the print server boot up and realize which print queue and file server it needs to service. • Is the Ethernet Interface already servicing a queue on another file server? If so, it can not service another file server at the same time. • When defining a new "print server" within PCONSOLE, did you use the correct name for the Ethernet Interface (e.g. M_071C1A)? By default, it only recognizes itself as "M_xxxxxx" where "xxxxxx" equals the last six digits of its ethernet address found on the configuration printout. • When defining a new "printer name" within PCONSOLE, did you use a pre-defined destination/queue rather than a name of your own? By default, the Ethernet Interface only recognizes names like "d1prn." All other names will be ignored by the device. • Is the Ethernet Interface in Bindery mode as seen under the "list pserver" output on the device? If servicing only a NetWare 4.x file server, it must be set to handle Bindery services. The default setting is Bindery. 6-12 Novell Configuration

  • 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
6–12
Novell Configuration
•
When defining a new “
printer name
” within PCONSOLE, did you use a
pre–defined destination/queue rather than a name of your own? By
default, the Ethernet Interface only recognizes names like “
d1prn
.
” All
other names will be ignored by the device.
•
Is the Ethernet Interface in
Bindery
mode as seen under the “
list
pserver
” output on the device? If servicing only a NetWare 3.x file
server, it must be set to handle Bindery services. The default setting is
Bindery.
•
Is there an available NetWare user license for the Ethernet Interface to
use while it acts as a PSER
VER? Every PSER
VER takes up one user
license since it logs in to the Novell file server.
•
Have you given the connection process some time after repowering the
Ethernet Interface? In larger Novell environments, the file server
identification and connection process can take several minutes.
NetWare 4.x – No PSERVER Connection
•
Has the Ethernet Interface been power cycled once the PCONSOLE
steps were completed? This will make the print server boot up and
realize which print queue and file server it needs to service.
•
Is the Ethernet Interface already servicing a queue on another file
server? If so, it can not service another file server at the same time.
•
When defining a new “
print server
” within PCONSOLE, did you use the
correct name for the Ethernet Interface (e.g. M_071C1A)? By default, it
only recognizes itself as “M_
xxxxxx
” where “
xxxxxx
” equals the last six
digits of its ethernet address found on the configuration printout.
•
When defining a new “
printer name
” within PCONSOLE, did you use a
pre–defined destination/queue rather than a name of your own? By
default, the Ethernet Interface only recognizes names like “
d1prn
.
” All
other names will be ignored by the device.
•
Is the Ethernet Interface in
Bindery
mode as seen under the “
list
pserver
” output on the device? If servicing only a NetWare 4.x file
server, it must be set to handle Bindery services. The default setting is
Bindery.