105
W I r e l e s s L A N U s e r ’ s G u i d e
IP packet isn’t reach-
ing its destination
Run the PING
command to check
the connection
Perform the following steps to run the PING command to check if the
IP packet is correctly delivered to the destination.
To run the PING command, the TCP/IP protocol must be installed.
First you will determine your IP address, then you will make sure your
IP address can respond, and then you will make sure other computers
can be addressed.
1. Windows 98: Click [Start] -> [Programs] -> [MS-DOS Prompt].
Windows 2000: Click [Start] -> [Programs] -> [Accessories] ->
[Command Prompt].
Windows XP: Click [Start] -> [All Programs] -> [Accessories] ->
[Command Prompt].
2. Type: ipconfig >
directory\filename
where
directory
and
filename
represent the location at which you
want to find the IP address.
3. Click [Enter], then go to the location you specified above. The IP
address for your system will be contained in the file.
4. To check that your IP address is functioning properly, go back to
the DOS prompt and type: ping
<IP address>
, then press [Enter].
You will receive several replies, followed by the PING statistics
(similar to below).
5. To check that your system is communicating with other systems,
go to the DOS prompt and type:
\>ping XXX.XXX.XXX.XXX. (With the destination IP address in
place of XXX.XXX.XXX.XXX).
Example: if the destination IP address is 10.0.1.3:
C:\>ping 10.0.1.3
A message similar to the following appears if the connection is
successful.
Pinging 10.0.1.3 with 32 bytes of data:
Reply from 10.0.1.3: bytes=32 time=1ms TTL=32
Reply from 10.0.1.3: bytes=32 time<10ms TTL=32
Reply from 10.0.1.3: bytes=32 time=4ms TTL=32
Reply from 10.0.1.3: bytes=32 time<10ms TTL=32
If the connection fails, [Request timed out], [Destination host
unreachable], or a similar message appears. In this case, refer to the
“Other computers are not displayed” portion of this chapter.
Cannot connect to
the network
There are several
possible causes, as
listed to the right.
Refer to the
specific section of this
manual or your user’s
manual.
The following causes are possible. Check each one of them.
■
The network name or encryption key is not right.
■
The driver has not correctly started.
■
The destination computer is not turned on.
■
You do not have the access privilege to the destination computer.
■
The card has failed.
■
Hardware conflict.
Problem
Possible Cause
Possible Solution
B Series.book Page 105 Thursday, April 11, 2002 4:34 PM
Summary of Contents for LifeBook B Series
Page 2: ...L i f e B o o k B S e r i e s B Series book Page 2 Thursday April 11 2002 4 34 PM ...
Page 6: ...L i f e B o o k B S e r i e s B Series book Page 6 Thursday April 11 2002 4 34 PM ...
Page 7: ...1 1 Preface B Series book Page 1 Thursday April 11 2002 4 34 PM ...
Page 8: ...2 L i f e B o o k B S e r i e s B Series book Page 2 Thursday April 11 2002 4 34 PM ...
Page 11: ...5 2 Getting to Know Your LifeBook B Series book Page 5 Thursday April 11 2002 4 34 PM ...
Page 31: ...25 3 Getting Started B Series book Page 25 Thursday April 11 2002 4 34 PM ...
Page 41: ...35 4 User Installable Features B Series book Page 35 Thursday April 11 2002 4 34 PM ...
Page 55: ...49 5 Troubleshooting B Series book Page 49 Thursday April 11 2002 4 34 PM ...
Page 71: ...65 6 Care and Maintenance B Series book Page 65 Thursday April 11 2002 4 34 PM ...
Page 77: ...71 7 Specifications B Series book Page 71 Thursday April 11 2002 4 34 PM ...
Page 83: ...77 8 Glossary B Series book Page 77 Thursday April 11 2002 4 34 PM ...
Page 94: ...88 L i f e B o o k S S e r i e s B Series book Page 88 Thursday April 11 2002 4 34 PM ...