Lantronix MPS100 EPS Reference Manual - Page 61

TCP/IP Host Setup

Page 61 highlights

7: TCP/IP Host Setup The EZWebCon configuration software is the easiest way to configure teh Server. See your Installation Guide for more information on using the EZWebCon software. Servers servicing TCP/IP print queues must have the TCP/IP protocol enabled (the default). To verify that TCP/IP is enabled, enter the List Protocols command. The server must have an IP address before configuration; see your Installation Guide for more information. Any host wishing to access the Serverwill have to be informed of this IP address, which is typically configured in the UNIX /etc/hosts file or via a nameserver. Note: One of the most common causes of IP network problems is duplicate IP addresses. Please make sure that your Server has a unique IP address. 7.1 Selecting A Printing Method The Server provides three major TCP/IP printing methods: Berkeley remote LPR and Reverse Telnet (RTEL) host software and sockets. All methods provide queueing of jobs if the Server is busy with another job. If custom queueing software has been designed, raw TCP/IP or Telnet socket connections can be made directly to the Server ports. Instructions for all three methods are provided in the following sections. Please read through the entire configuration procedure before beginning. Note: See the man pages included with the distribution CD-ROM for a full discussion of RTEL functionality and configuration. LPR LPR allows the Server to look like a UNIX host that can print files. It is the recommended way of printing because it is easy to set up and requires no additional host software. However, not all machines support the lpr system (notably machines running UNIX based on System V instead of BSD). Note: The Server cannot implement all lpr options; the print job information is not available until the print job is completed. Printing with LPD is also easy to set up, but LPD has a few significant restrictions. First, control information about the print job is sent after the print data has been sent, so options like binary characteristics and formatting cannot be applied. Second, the banner page is printed after the job instead of before it. Finally, because the Server is not actually spooling the print data locally, only one copy of the job will be printed regardless of the number of copies requested. 7-1

  • 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

7-
1
7:
TCP/IP Host Setup
The EZWebCon configuration software is the easiest way to configure teh Server. See your
Installation
Guide
for more information on using the EZWebCon software.
Servers servicing TCP/IP print queues must have the TCP/IP protocol enabled (the default). To verify that
TCP/IP is enabled, enter the
List Protocols
command.
The server
must
have an IP address before configuration; see your
Installation Guide
for more information.
Any host wishing to access the Serverwill have to be informed of this IP address, which is typically
configured in the UNIX
/etc/hosts
file or via a nameserver.
Note:
One of the most common causes of IP network problems is duplicate IP
addresses. Please make sure that your Server has a unique IP address.
7.1
Selecting A Printing Method
The Server provides three major TCP/IP printing methods: Berkeley remote LPR and Reverse Telnet
(RTEL) host software and sockets. All methods provide queueing of jobs if the Server is busy with another
job. If custom queueing software has been designed, raw TCP/IP or Telnet socket connections can be made
directly to the Server ports. Instructions for all three methods are provided in the following sections. Please
read through the entire configuration procedure before beginning.
Note:
See the man pages included with the distribution CD-ROM for a full discussion
of RTEL functionality and configuration.
LPR
LPR allows the Server to look like a UNIX host that can print files. It is the
recommended way of printing because it is easy to set up and requires no
additional host software. However, not all machines support the lpr system
(notably machines running UNIX based on System V instead of BSD).
Note:
The Server cannot implement all lpr options; the print job information is not
available until the print job is completed.
Printing with LPD is also easy to set up, but LPD has a few significant
restrictions. First, control information about the print job is sent after the print
data has been sent, so options like binary characteristics and formatting cannot
be applied. Second, the banner page is printed after the job instead of before it.
Finally, because the Server is not actually spooling the print data locally, only
one copy of the job will be printed regardless of the number of copies
requested.