3com 3C840 Guía Del Usuario
4-16
C
HAPTER
4: C
ONFIGURING
IP R
OUTING
The name could not be resolved. Either no DNS server was located or
the server(s) did not have the name in the host table list. However, this
error will also appear if the user entered an IP address incorrectly -
such as 100.100.100.256 (an invalid IP address) so it is interpreted as a
name to be resolved by DNS.
the server(s) did not have the name in the host table list. However, this
error will also appear if the user entered an IP address incorrectly -
such as 100.100.100.256 (an invalid IP address) so it is interpreted as a
name to be resolved by DNS.
■
Network Name: <name> could not be resolved due to a timeout
on the request.
on the request.
No response was received from the DNS server to which the DNS
request was sent. This could be due to a network connection problem
or a very slow line.
request was sent. This could be due to a network connection problem
or a very slow line.
Option 2: DOS Ping to
ISP or Remote Site
Network
From the a workstation on the local LAN, get to an MS-DOS prompt and
type ping <remote IP address> <Enter> where the remote IP address is
the address of a host on the remote network (Ex: ping 10.0.0.12). If no
address was provided, contact the ISP or the remote site administrator for
an IP address to ping.
type ping <remote IP address> <Enter> where the remote IP address is
the address of a host on the remote network (Ex: ping 10.0.0.12). If no
address was provided, contact the ISP or the remote site administrator for
an IP address to ping.
The OfficeConnect Remote 840 will call the ISP and send the PING
information. A reply from 10.0.0.12 indicates success
information. A reply from 10.0.0.12 indicates success
An example script of a failed ping is:
C:\ping 10.0.0.12
Pinging 10.0.0.12 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
An example script of a successful ping is:
C:\ping 10.0.0.12
Pinging 10.0.0.12 with 32 bytes of data:
Reply from 10.0.0.12 bytes=32 time=140ms TTL=240
Reply from 10.0.0.12 bytes=32 time=147ms TTL=240
Reply from 10.0.0.12 bytes=32 time=140ms TTL=240
Reply from 10.0.0.12 bytes=32 time=135ms TTL=240
840ug.book Page 16 Friday, July 7, 2000 2:23 PM