Lantronix MPS100 EPS Reference Manual - Page 22

NetWare

Page 22 highlights

NetWare Concepts Note: Netstat Ping To see a list of Server processes, enter the command "finger finger." Displays the status of the routing tables and current network sessions. Sends a TCP/IP request for an echo packet to another network host to test network connections. 2.7 NetWare Novell's NetWare software allows you to link computers together and provide file and printer sharing. It is typically used to network DOS-based PCs, but is starting to appear under UNIX and other operating systems. NetWare is built around file servers, which handle user logins, provide network resources, and control security. At least one file server, such as a PC or UNIX host, is required in any NetWare environment. NetWare users typically have to log into a file server to enjoy the networked (shared) benefits. The Server supports a significant subset of the NetWare functionality, most notably print spooling. Fileservers can be configured to send queued print jobs to printers attached to the Server. No special software is required on the fileserver; configuration uses the EZWebCon Configuration software or the standard PCONSOLE utility. Any user or application that can use NetWare print queues can spool jobs to the Server. The Server must periodically query the file servers for pending jobs. To do so, it logs into a file server to access the print spooler, and will try to connect to all file servers on the local network (subject to access lists, explained later) to check for such jobs. See Set/Define Server NetWare Loadhost on page 12-43 for more information. NetWare support also allows logins from fileservers to the Server (for configuration) and file downloading (to download the system software at boot time). 2.7.1 Networking Each NetWare node uses its hardware address as its node ID. In addition, the Server gets all the networking information it needs from periodic broadcasts sent by NetWare routers on the network. It will learn its own network number as well as routes to non-local file servers. No further configuration is needed. The NetWare protocol can use all four Ethernet frame formats. It will listen for all frame formats, and then use the correct one for the connection. The different frame types are treated as different networks, and thus each frame type has a different network number. If there is only one frame format in use on the LAN, the Server will use the network number for that frame type. If there are multiple frame types, limitations to the NetWare protocol require that the Server use a different network number for each frame type on which it wants to advertise itself. The Server can use multiple frame types by creating a new, unique "internal network number" and advertising itself as a router to the internal network. Any nodes or fileservers that need to communicate with the Server use this new network number, and treat the Server as a router to that network. If this behavior is not desired, the Server can be forced to use only one frame type (and thus not need an internal network number). 2-8

  • 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
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204
  • 205
  • 206
  • 207
  • 208
  • 209
  • 210
  • 211
  • 212
  • 213
  • 214
  • 215
  • 216
  • 217
  • 218
  • 219
  • 220
  • 221
  • 222
  • 223

NetWare
Concepts
2-
8
Note:
To see a list of Server processes, enter the command “finger finger.”
Netstat
Displays the status of the routing tables and current network sessions.
Ping
Sends a TCP/IP request for an echo packet to another network host to test
network connections.
2.7
NetWare
Novell’s NetWare software allows you to link computers together and provide file and printer sharing. It is
typically used to network DOS-based PCs, but is starting to appear under UNIX and other operating
systems. NetWare is built around file servers, which handle user logins, provide network resources, and
control security. At least one file server, such as a PC or UNIX host, is required in any NetWare
environment. NetWare users typically have to log into a file server to enjoy the networked (shared) benefits.
The Server supports a significant subset of the NetWare functionality, most notably print spooling.
Fileservers can be configured to send queued print jobs to printers attached to the Server. No special
software is required on the fileserver; configuration uses the EZWebCon Configuration software or the
standard PCONSOLE utility. Any user or application that can use NetWare print queues can spool jobs to
the Server.
The Server must periodically query the file servers for pending jobs. To do so, it logs into a file server to
access the print spooler, and will try to connect to all file servers on the local network (subject to access lists,
explained later) to check for such jobs. See
Set/Define Server NetWare Loadhost
on page 12-43 for more
information.
NetWare support also allows logins from fileservers to the Server (for configuration) and file downloading
(to download the system software at boot time).
2.7.1
Networking
Each NetWare node uses its hardware address as its node ID. In addition, the Server gets all the networking
information it needs from periodic broadcasts sent by NetWare routers on the network. It will learn its own
network number as well as routes to non-local file servers. No further configuration is needed.
The NetWare protocol can use all four Ethernet frame formats. It will listen for all frame formats, and then
use the correct one for the connection. The different frame types are treated as different networks, and thus
each frame type has a different network number. If there is only one frame format in use on the LAN, the
Server will use the network number for that frame type. If there are multiple frame types, limitations to the
NetWare protocol require that the Server use a different network number for each frame type on which it
wants to advertise itself.
The Server can use multiple frame types by creating a new, unique “internal network number” and
advertising itself as a router to the internal network. Any nodes or fileservers that need to communicate with
the Server use this new network number, and treat the Server as a router to that network. If this behavior is
not desired, the Server can be forced to use only one frame type (and thus not need an internal network
number).