• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 721
  • Last Modified:

Can't ping router, running XP Home

I have a home LAN with four machines.  3 of them cannot connect to the internet.

All four were working fine until a couple of days ago.  One is runing XP media Center and it is fine.  The other 3 are running XP Home and have trouble.

I have a cable connection with a LinkSys WRT54G router.  I am only using the hardwire connections at the moment -- no wireless.  That removes a variable.

Let's pick one of the XP Home machines.  This machine can successfully ping localhost.  It cannot ping the router, or the XP Media Center machine, or an IP address on the net.  Sample shown below.

C:\Documents and Settings\JoeO>ping localhost

Pinging SideWinder [127.0.0.1] with 32 bytes of data:

Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128

Ping statistics for 127.0.0.1:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 0ms, Average = 0ms

C:\Documents and Settings\JoeO>pathping 74.125.19.103

Tracing route to 74.125.19.103 over a maximum of 30 hops

  0  SideWinder.hsd1.ca.comcast.net. [192.168.1.101]
  1  192.168.1.1
  2     *        *        *
Computing statistics for 50 seconds...
            Source to Here   This Node/Link
Hop  RTT    Lost/Sent = Pct  Lost/Sent = Pct  Address
  0                                           SideWinder.hsd1.ca.comcast.net. [1
92.168.1.101]
                                0/ 100 =  0%   |
  1    0ms     0/ 100 =  0%     0/ 100 =  0%  192.168.1.1
                              100/ 100 =100%   |
  2  ---     100/ 100 =100%     0/ 100 =  0%  SideWinder [0.0.0.0]

Trace complete.

On the router, one output cable leads to the Media Center machine and another leads to the XP Home machine.  I have swapped the two cables (at the router).  The problem did _not_ move.

I need help.

0
josgood
Asked:
josgood
  • 9
  • 9
  • 2
1 Solution
 
http:// thevpn.guruCommented:
Might someone have changed the settings on the linksys routers to block requests from your XPs based on MAC address
0
 
http:// thevpn.guruCommented:
Can you ping the media center computer
0
 
http:// thevpn.guruCommented:
Hm..no you cant...
try to restart in safe mode with networking and try again
0
When ransomware hits your clients, what do you do?

MSPs: Endpoint security isn’t enough to prevent ransomware.
As the impact and severity of crypto ransomware attacks has grown, Webroot has fought back, not just by building a next-gen endpoint solution capable of preventing ransomware attacks but also by being a thought leader.

 
josgoodAuthor Commented:
I have restarted the XP Home machine in safe mode.  The ping localhost and pathping commands give the same result.

The Media Center machine is able to do both with no trouble...
C:\Documents and Settings\Joe>ping www.google.com

Pinging www.l.google.com [74.125.19.104] with 32 bytes of data:

Reply from 74.125.19.104: bytes=32 time=20ms TTL=241
Reply from 74.125.19.104: bytes=32 time=57ms TTL=241
Reply from 74.125.19.104: bytes=32 time=20ms TTL=241
Reply from 74.125.19.104: bytes=32 time=18ms TTL=241

Ping statistics for 74.125.19.104:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 18ms, Maximum = 57ms, Average = 28ms

But the XP Home machine times out pinging the same address (I tried the .104 number just to be sure).

I doubt anyone has changed the LinkSys settings.  I have not and my wife is the only other network user.  She doesn't have the technical knowledge...(actually I'd have to go look it up).
0
 
josgoodAuthor Commented:
Started XP Home machine in safe mode with networking.
0
 
http:// thevpn.guruCommented:
Can you ping the computer by using it's IP address instead of using localhost..
0
 
josgoodAuthor Commented:
Yes that is successful.  IP Address is 192.168.1.101

However, pinging that address from the Media Center machine times out.

IPConfig for the media center machine is
C:\Documents and Settings\Joe>ipconfig

Windows IP Configuration


Ethernet adapter Local Area Connection:

        Connection-specific DNS Suffix  . : hsd1.ca.comcast.net.
        IP Address. . . . . . . . . . . . : 76.105.20.10
        Subnet Mask . . . . . . . . . . . : 255.255.248.0
        Default Gateway . . . . . . . . . : 76.105.16.1

IPConfig for the XP Home machine is
C:\Documents and Settings\JoeO>ipconfig

Windows IP Configuration


Ethernet adapter Local Area Connection:

        Connection-specific DNS Suffix  . : hsd1.ca.comcast.net.
        IP Address. . . . . . . . . . . . : 192.168.1.101
        Subnet Mask . . . . . . . . . . . : 255.255.255.0
        Default Gateway . . . . . . . . . : 192.168.1.1
0
 
http:// thevpn.guruCommented:
All right thenn

Your IP configuration is wrong

The media center has the IP address that should be entered into the linkys router
do the following
Configure your linksys router with the ip configuration of the media center PC.
After that configure the XP + media centers to use the IP of the linksys router as the gateway and dns...and change the media center IP to somethin useful such as 192.168.1.210

To test it before changing anything...
just change the media center config ...to IP address 192.168.1.210 and Subnet 255.255.255.0 and ping the XP home machine ...it should reply
0
 
josgoodAuthor Commented:
Well, I scared myself, there.  I configured as you suggested and lost all connectivity.  Then I was able to "obtain a DNS service automatically" and had an internet connection again.

<grin> Had me worried for a moment!  Here's the console window data...
C:\Documents and Settings\Joe>ipconfig

Windows IP Configuration


Ethernet adapter Local Area Connection:

        Connection-specific DNS Suffix  . :
        IP Address. . . . . . . . . . . . : 192.168.1.210
        Subnet Mask . . . . . . . . . . . : 255.255.255.0
        Default Gateway . . . . . . . . . : 192.168.1.1

C:\Documents and Settings\Joe>ping 192.168.1.101

Pinging 192.168.1.101 with 32 bytes of data:

Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 192.168.1.101:
    Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

>>>Note from Joe-- At this point, couldn't connect Firefox to a new page<<<

C:\Documents and Settings\Joe>ipconfig

Windows IP Configuration


Ethernet adapter Local Area Connection:

        Connection-specific DNS Suffix  . : hsd1.ca.comcast.net.
        IP Address. . . . . . . . . . . . : 76.105.20.10
        Subnet Mask . . . . . . . . . . . : 255.255.248.0
        Default Gateway . . . . . . . . . : 76.105.16.1
0
 
http:// thevpn.guruCommented:
Are u using dhcp or static ip addreses
0
 
josgoodAuthor Commented:
When I set the fixed address of 192.168.1.210, I was using a static IP address.

In normal operation I'm using DHCP.
0
 
http:// thevpn.guruCommented:
And have you inserted the internet cable into a WAN or LAN port in the router
0
 
josgoodAuthor Commented:
OK, I feel pretty stupid...No I don't.  And that is a clever question to ask -- you are a man of experience!

I have the Media Center machine in port 2, the cable modem in port 3, and the XP Home machine in port 4.

I quickly tried plugging the cable modem into the WAN port, but lost connectivity.  Moved it back to port 3 and had connectivity again.

How should I proceed?
0
 
josgoodAuthor Commented:
Here's my plan...I don't have recovery steps if anything goes wrong.

I'm expecting to configure all machines for DHCP, if they are not already so configured.

1)  Download the WRT54G user guide from LinkSys.
2)  I can't ping the router from the Media Center machine, which probably means it has a non-standard IP address, so first I'll reset the router by holding the reset button down for about 5 seconds.
3)  Ping 192.168.1.1.  This better work, because otherwise I don't know what to do.
4)  Plug the cable modem's cable into the router's WAN connector (it's in port 3 right now).
5)  Connect to 192.168.1.1 with a browser.  Should be able to use the default password.
6)  Connect to the web with a browser.
7)  If OK so far, then connect to the web with a browser on the XP Home machine.  If any trouble compare network settings against the Media Center machine.
8)  Connect to the Web with browsers on the other two machines.
9)  Then set up security on the router.

Can you make any suggestions?  I'll wait for a while before trying this...I'd like to avoid having something go wrong and then being unable to re-establish connectivity.
0
 
Adrien de CroyCommented:
Normally modems have some method of resetting them in case you lose connectivity to it.  check the manual for your modem for that.  Sometimes it's something like holding the power button down for a while when it powers up.

As for pinging localhost, that doesn't test anything - the packets don't even go below tcpip.sys let alone through NDIS to your ethernet driver, so it's not normally a test for anything useful.

Next thing is check that the other 3 machines are on the same subnet as the one that works.  Same subnet means same range of IP addresses.  If the machine is using DHCP, then you can see the IP information by typing

ipconfig /all

from a command prompt.  That will tell you the DHCP server etc.  If the address starts with 169.254.X.X  then you should change the adapter settings on that machine to manually set an IP address, and choose one adjacent to the IP address on the machine that works, and set a network mask of 255.255.255.0.

If that gets that machine working, try moving on to the next one.

Also, before you start any of this, reboot the linksys to make sure it's not causing the problem.

0
 
http:// thevpn.guruCommented:
I suggest the following :

As you said

1)  Download the WRT54G user guide from LinkSys.
2)  I can't ping the router from the Media Center machine, which probably means it has a non-standard IP address, so first I'll reset the router by holding the reset button down for about 5 seconds.
3)  Ping 192.168.1.1.  This better work, because otherwise I don't know what to do.
4)  Plug the cable modem's cable into the router's WAN connector (it's in port 3 right now).
5)  Connect to 192.168.1.1 with a browser.  Should be able to use the default password.

Now once you are inside the the interface of the linksys router..you have to do two things..one enable DHCP so that you clients will all get their IPs from the router..two setup the ip configuration of the router so that it is the gateway..i.e. configure the IP settings of the router ..my best guess would be that it is allright to set the ip settings of the router to DHCP. Now after doing this..right click on every connection on the XP computers and do a repair...after doing this all the computers should be able to ping each other and the linksys router...if the linksys router is confgured correctly they should also be able to ping the Internet and all is solved.
0
 
Adrien de CroyCommented:
Actually just noticed the ipconfigs.

so the XP media center machine that works has how many network cards?  If just one, then unless it knows of a route to the 192.168.0.x subnet, then the other machines won't be reachable.

In general all your machines should be on the same subnet.
0
 
josgoodAuthor Commented:
Thank you both for the responses.  I won't be able to try them until this evening -- about 11 hr now.   Am just leaving for work.

This gives me enough courage to try it.  Thank you!
0
 
josgoodAuthor Commented:
Success!

I'm communicating through my reconfigured router.

shakoush2001, thank you _very_  much.  Your advice worked perfectly and everything went smoothly.  I am very relieved.

AdriendeC, I appreciate your input.  I didn't know that pinging localhost told so little -- that is good to know.

I'm torn.  I'd like to acknowledge AdriendeC for the data, but shakoush2001 is really the person who solved the problem.

shakoush2001, I'd like to say again that I'm very impressed with your asking the "silly" question -- did I actually have it plugged in.  <Grin>  Thank you.

I think the right thing to do is to award all points to shakoush2001.  I hope that AdriendeC is not offended.
0
 
http:// thevpn.guruCommented:
Thanks alot..Iam glad it is solved
0

Featured Post

2017 Webroot Threat Report

MSPs: Get the facts you need to protect your clients.
The 2017 Webroot Threat Report provides a uniquely insightful global view into the analysis and discoveries made by the Webroot® Threat Intelligence Platform to provide insights on key trends and risks as seen by our users.

  • 9
  • 9
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now