EtherPath-X4 User’s Guide
Can't Connect via the LAN
P1
:
Can't connect to the EtherPath using Telnet or Web Browser.
S1:
Check the following:
•
Start troubleshooting from a known state. Power the EtherPath and other equipment OFF and
ON to reboot.
•
“Ping” the EtherPath to see if it responds. From the Windows command prompt or “Run”
dialog box, use the command:
ping IP_Address
Where
IP_Address
is the IP Address of the EtherPath (e.g.
ping 192.168.1.1
). If it does
not respond, then check all LAN connections. If the workstation can not ping the EtherPath,
nothing else will work… fix this first. If the LAN connection are OK, the problem is in the LAN
addresses or routing. You should be able to ping both EtherPaths in a Client/Server pair.
•
If using a LAN without routers, you can connect to the EtherPath ONLY IF your PC and the
EtherPath are using IP Addresses from the same address block. The EtherPaths default IP Address
(192.168.1.1) requires that your PC is using an address from the address block 192.168.1.2 to
192.168.1.254, and a
Network Mask
of 255.255.255.0. If a router is between the devices, a
gateway address must be configured in both devices.
Check your PC's IP Address using
Control Panel - Network - TCP/IP (Adapter) Properties o
r
similar commands appropriate for your computer. If you are using a different Address block, use
Terminal Mode
configuration to set a compatible IP Address in the EtherPath.
•
Check that you have used the correct port address. The default address is “3000” for normal
operation and “8000” for configuration.
•
Is there a firewall in the Ethernet path. If so, it must be configured to pass the ports in use by
the EtherPath. Many trouble calls are the result of firewall changes that block the EtherPath ports.
•
Are you trying to connect to the EtherPath data port with a web browser? That only works for
configuration on port 8000.
•
Web Browsers often are configured to use a proxy server. The browser might need to be
configured to NOT use the proxy when connecting to the EtherPath, or the proxy server may be
configured to pass the requests correctly.
•
MOST EtherPath connection problems are due to incorrect RS-232 wiring. The second most
common errors are incorrect IP addressing on either the EtherPath or on the PC used for testing.
40
