How To
87
Network Guide
When there is a primary server in the local network
Even if a primary server is installed on the local network, an unnecessary dial-up may be
generated depending on the configuration.
The following problems are common to both Print Server mode and Remote Printer mode.
❏
When the power is turned on
Since access is made only to the primary server, no dial-up is generated.
❏
When the network interface is not correctly set
Since access is made only to the primary server, no dial-up is generated. However, if
the file server/print server of the remote network is erroneously set as the primary
server, an unnecessary dial-up might be generated. Correct the settings to avoid this
problem.
❏
During normal operation (standby/printing)
Since access is made only to the primary server, no dial-up is generated.
❏
When the primary server is down during operation
Connection to the primary server is periodically attempted, but no dial-up is generated.
However, if the router is set to pass SAP packets (Find Nearest Server), an
unnecessary dial-up might be generated. To avoid this, turn off the printer once, or do
not allow the router to pass SAP packets (Find Nearest Server).
For Users of Printers Not Supporting NetWare Queue-Based Printing
This section explains how to configure the network interface for NetWare.
To print in a NetWare environment, you need to use NDPS. First, install EpsonNet NDPS
Gateway on the NetWare server, and then set a valid IP address to the network interface
using EpsonNet Config.
Note:
Be sure to set a static IP address to the network interface.
Local network
Printer
Dial-up
router
Dial-up
router
File server
(print server)
Remote network
Primary file server
(primary print server)
