Lantronix MPS100 EPS Reference Manual - Page 41

TCP/IP Server Parameters

Page 41 highlights

Server Configuration TCP/IP Server Parameters By default, the Server will only query local fileservers, but this may still be too many in a large network. The Clear/Purge Protocol NetWare Access command allows you to remove items from the access list. The Set/Define Protocols NetWare Reset command can be used if necessary to force the Server to rescan all fileservers for pending jobs. This is useful after rebooting or after configuring new queues on the fileservers to ensure that the Server recognizes queues directed to it. Keep in mind that fileservers cannot tell if the Server is not polling them due to access restrictions. There will be no error messages if a valid fileserver cannot print to the Server due to the access list. 4.5 TCP/IP Server Parameters If you want TCP/IP connectivity (Telnet, Rlogin, LPR, and RTEL support), you must configure IP parameters on the Server. First and foremost, the Server must have a unique IP address. If this was set at boot time (by BOOTP, DHCP, or RARP), it does not need to be reset. Other parameters are explained in this section. Note: An IP address is also required for EZWebCon use. 4.5.1 IP Address To configure the Server's IP address, use a command of the following form. Figure 4-10: Setting the IP address Local> DEFINE SERVER IPADDRESS 192.0.1.228 One of the most common problems is that of duplicate IP addresses on the network. Signs of this problem are Telnet/Rlogin connections that fail soon after connecting and ARP requests that do not find a known host. If the server either loses its IP address when booting or will not allow a new IP address to be configured, another host might be using the same address. If any of these problems occur, double check to make sure that your Server has a unique IP address on the network. Note: See your Installation Guide for more information on configuring the IP address. 4.5.2 Other TCP/IP Parameters Users can set a gateway host, which allows TCP/IP connections to other connected network segments, and a loadhost (if not done already) from which to download operational code. Figure 4-11: Setting TCP/IP Parameters Local> DEFINE SERVER GATEWAY 192.0.1.188 Local> DEFINE SERVER LOADHOST 192.0.1.33 You can also configure a backup host in case the primary one fails. Figure 4-12: Configuring Backup Hosts Local> DEFINE SERVER SECONDARY GATEWAY 192.0.1.195 4-5

  • 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

Server Configuration
TCP/IP Server Parameters
4-
5
By default, the Server will only query local fileservers, but this may still be too many in a large network.
The
Clear/Purge Protocol NetWare Access
command allows you to remove items from the access list.
The
Set/Define Protocols NetWare
Reset
command can be used if necessary to force the Server to rescan
all fileservers for pending jobs. This is useful after rebooting or after configuring new queues on the
fileservers to ensure that the Server recognizes queues directed to it.
Keep in mind that fileservers cannot tell if the Server is not polling them due to access restrictions. There
will be no error messages if a valid fileserver cannot print to the Server due to the access list.
4.5
TCP/IP Server Parameters
If you want TCP/IP connectivity (Telnet, Rlogin, LPR, and RTEL support), you must configure IP
parameters on the Server. First and foremost, the Server must have a unique IP address. If this was set at
boot time (by BOOTP, DHCP, or RARP), it does not need to be reset. Other parameters are explained in
this section.
Note:
An IP address is also required for EZWebCon use.
4.5.1
IP Address
To configure the Server’s IP address, use a command of the following form.
Figure 4-10:
Setting the IP address
One of the most common problems is that of duplicate IP addresses on the network. Signs of this problem
are Telnet/Rlogin connections that fail soon after connecting and ARP requests that do not find a known
host. If the server either loses its IP address when booting or will not allow a new IP address to be
configured, another host might be using the same address. If any of these problems occur, double check to
make sure that your Server has a unique IP address on the network.
Note:
See your Installation Guide for more information on configuring the IP address.
4.5.2
Other TCP/IP Parameters
Users can set a gateway host, which allows TCP/IP connections to other connected network segments, and
a loadhost (if not done already) from which to download operational code.
Figure 4-11:
Setting TCP/IP Parameters
You can also configure a backup host in case the primary one fails.
Figure 4-12:
Configuring Backup Hosts
Local> DEFINE SERVER IPADDRESS 192.0.1.228
Local> DEFINE SERVER GATEWAY 192.0.1.188
Local> DEFINE SERVER LOADHOST 192.0.1.33
Local> DEFINE SERVER SECONDARY GATEWAY 192.0.1.195