Bada boom, but no ping

[da_grinch]

I have a peer to peer network at home with two pc's. My cable broadband is connected directly to my Belkin 4 port router. The Pc that is plugged into port one of the router is running Windows XP, and it originally was the only PC that I could use to change the internal router settings from. I can not even ping the router from the XP computer now. Long story short, I cannot access the internet from this PC, only with the other PC on the network that is running windows 98se. Now, the XP system seems to know that it is connected to the router, but there is definetily some communication/configuration issues. For example, when I pull out the cable that connects the router and the XP system, windows tells me that a network cable is unplugged.

When I try to ping the XP system from the 98Se system, I get 'request timed out'. I can ping the router from the 98se system though, and connect to the internet. This fact alone tells me that the router is seemingly ok, but the Xp system isn't telling me anything really. I've reinstalled the protocols and client on the the XP system to no avail. I've also used the troubleshooting wizard to try to repair the connection to the router, that also produced no effect. I've changed the cable, reseated the NIC, and manually configured the TCP/IP settings to their initial values, and still no luck connecting to the internet. Any help would be ten times appreciated, thanks.

[tha 4NiK8R]

are you using DHCP? are you getting an IP?

[NooNoo]

Turned off the XP built in firewall?

Created an account on the xp box for the 98 box to login to?

[Matridom]

Originally posted by tha 4NiK8R
are you using DHCP? are you getting an IP?

sounds like an issue with the configuration of the router. I'd set the router back to default and reboot it.

On the XP box, what IP address are you getting?

Is it 169.254.x.x? or is it 192.168.X.X

If it's the first, then your not even getting a DHCP lease from the router and need to diagnose your network card further.

if your gettin a 192.168 IP, then you have an issue with the OS itself, either a firewall program of somesort or a really bad nic.

what i'm thinking the issue may be is that you've turned of the DHCP service in the router and your not able to get online. you may have also assigned the same IP to both computers (that is if your set static) and one computer will knock the other offline.

[da_grinch]

Originally posted by Matridom
sounds like an issue with the configuration of the router. I'd set the router back to default and reboot it.

On the XP box, what IP address are you getting?

Is it 169.254.x.x? or is it 192.168.X.X


I've just reset the router to its default values and I still can not connect to the internet or ping the other Pc on the network. I am getting an IP address of 169.254.103.43. I've uninstalled the network card and tried it again, but that didn't solve anything. Going back over it again, as if I had a choice.

[Gollo]

Originally posted by da_grinch
I've just reset the router to its default values and I still can not connect to the internet or ping the other Pc on the network. I am getting an IP address of 169.254.103.43. I've uninstalled the network card and tried it again, but that didn't solve anything. Going back over it again, as if I had a choice.

Try swapping cables for the two computers. if the problems switches then you need to get a new cable. Also check the firewall on the xp box like noo suggested.

[Matridom]

One other thing you can try is to set a static IP and see if your able to ping then. You may have a bad wire, nic or port.

[da_grinch]

I've got it, the network card is bad. I switched the cables, and the system still didn't work. I also swapped the cables to check if it's the router port that is bad, but it the 98se system works fine in this port. It must be the network card, gotta find a cheap one somewhere. Thanks for all the help.

[Chris_MacMahon]

still might not be the nic...
try to ping the following address

127.0.0.1

if you can ping that address then you are good to go.

another thing that you can try is to disable the card then re-enable the card, i don't know if you router has the cool led's that tell you if something is connected to it or not...look at the light on the back of the card, if it's blinking it's on and goodl

[GreatBlob]

Try flushing the arp table.

arp -f

or look up how to fix a corrupt ip stack.

[SpongeBob]

Open a command Prompt

Format C: /u
Fdisk

Load Linux

Problem solved!


;)


Merry Christmass!!!

[da_grinch]

Originally posted by Chris_MacMahon
still might not be the nic...
try to ping the following address

127.0.0.1

if you can ping that address then you are good to go.

another thing that you can try is to disable the card then re-enable the card, i don't know if you router has the cool led's that tell you if something is connected to it or not...look at the light on the back of the card, if it's blinking it's on and goodl


I haven't bought the new card yet, so I did try to ping 127.0.0.1 and received a reply. However, the led on the nic is on, but not blinking. I have already tried to disable and re-enable the nic but that doesn't solve the problem either. My router has led's on the front that flash when something is connected to it, but in this case all the lights are flashing except for the pc that can't connect to the internet.

[Matridom]

Originally posted by da_grinch
I haven't bought the new card yet, so I did try to ping 127.0.0.1 and received a reply. However, the led on the nic is on, but not blinking. I have already tried to disable and re-enable the nic but that doesn't solve the problem either. My router has led's on the front that flash when something is connected to it, but in this case all the lights are flashing except for the pc that can't connect to the internet.

pinging 127.0.0.1 will only ONLY test the TCP/IP stack, nothing else. if there is an issue with the hardware on the nic, it may not detect it.

Defenitaly try a new nic.

[gazzak]

Why not PROVE if the NIC is faulty or not by swapping it with the 98 box's NIC, might save yourself a few pounds/bucks etc.

[Poseidon]

Originally posted by da_grinch
. . . I have already tried to disable and re-enable the nic but that doesn't solve the problem either. . . .



If you don't have an extra NIC lying around; before you go out and buy a new one you might try physicallyuninstalling and reinstalling it.
If availible, use a different PCI slot. Don't forget to remove it from the Device Manager first.

[phpCypher]

This problem has happened to me several times with XP. Whenever you make a change in the configuration of the network, XP auto-allocates the annoying "169.*.*.*" "AUTO" congfig IP address.

There are several options for you.

1. One is simply swap the nics between the two machines, as per a previous post, so XP will configure it with your new settings that you manually enter. This solves a symptom not the problem as XP will increment your NIC card's number, leaving the misconfigureded NIC card to stink up your registry, and to come back the next time you re-install the original NIC.
Out of the two times this has happened to me, I was once able to remove the initial nic from the registry, and it was all good.

2. Re-install. This method proves to be the best, even if as a last resort. This takes 20 minutes on average, not including making backups. Benifits include clean registry,system files closer to the center of the disc, etc.,etc.

3. Wait around for Auto-config to come out of hiatus.

4. Physically swap pci slots, hoping XP comes to it's senses.

I normally go for option two as it causes less headaches, and requires 0 hardware work. However this may not be convenient for you. I'm not too sure how this Auto-config thing comes out of the woodwork, but it is definetly tedious and time consuming..........

-- -- Hope any of this helps -- --

[da_grinch]

Ok, after about a month of procrastinating, I finally got around to troubleshooting my network card. Here's the deal:

1-the first thing that I did was reseating the card, again.

2-no luck with that, so I swapped the card with a neighboring sound card-ok, i've just confused myself, i basically swapped the network card with a sound card and tested both devices

3-my network card is good! but now my sound card is dead, and the answer is: my dern pci slot is fried! nothing works in this thing! Oh man, motherboardsdirect.com is going to hear from me soon.


First of all, my apologies to everyone who already suggested that I tried a different Pci slot. I was naiive enough to think that a new motherboard would not have a bad pci slot after about 3 months of relatively low usage.

And last but not least, I just want to thank everyone again for their input and feedback, you guys are the best.

[gazzak]

Thanks for updating everyone, it's always nice to know what fixed the problem, or what caused it in the first place. It may help someone in the future.