Baffling Router problem

[Furr]

Hi

Trying to fix a friends PC. This is the Problem. Their computer can't connect to the Voyager 205 Router they use.

So I've test their computer and hooked it up to my Router, works fine. Hooked the 205 router to my computer. Works fine!

So any ideas as to why their computer can't talk to the Router?!?! in the event log i keep getting these errors

------------------------

Your computer was not able to renew its address from the network (from the DHCP Server) for the Network Card with network address 000C764FDCF4. The following error occurred:
The operation was canceled by the user. . Your computer will continue to try and obtain an address on its own from the network address (DHCP) server.

------------------------

The server could not bind to the transport \Device\NetBT_Tcpip_{C831FF65-DEBD-485B-B2D6-E192F0A84B10}.

------------------------

Your computer was not able to renew its address from the network (from the DHCP Server) for the Network Card with network address 000C764FDCF4. The following error occurred:
The semaphore timeout period has expired. . Your computer will continue to try and obtain an address on its own from the network address (DHCP) server.

------------------------

 

[inactionman]

Does it work when you set a static IP address on the computer?

 

[Furr]

Well i have given it static details, and it doesn't compain but it can't even ping the router.

Something seems to be stopping the computer and this particular router talking to each other....

Sometimes it won't connect at all and other times limited connectivity. Im stumped

 

[inactionman]

Ok, basic ethernet troubleshooting.

Do you see link lights on both ethernet connections. If not, check cable/connections. Try a crossover lead (some cheap network cards designed to connect to an ethernet router used crossed interfaces instead of a crossed lead, stupid eh!).

If you get lights, do a 'arp -a' on the computer, do you see a physical address with an IP address for the router. If not, change the cable, if that doesn't work, try the next thing.

Boot the computer using a knoppix cd, if that works, windows is hosed. Try reinstalling the ethernet drivers, or windows. If knoppix fails to connect, it's a hardware thing!

From the error code it looks like it's the driver/windows, but it's always best to test these things from the ground up, else you jump ahead and miss the key to the problem.

 

[smurkin]

Sounds a lil like winsock is corrupted. Had similar myself recently. Try this (I dont think it could hurt)...

Step 6: Repair Winsock and TCP/IP (FOR WINDOWS XP!!!)
1. Click Start, click Run, type netsh winsock reset, and then press ENTER.
2. When the Command Prompt window flashes, restart the computer.

Warning Programs that access or monitor the Internet, such as antivirus, firewall, or proxy clients, may be negatively affected when you run the netsh winsock reset command. If you have a program that no longer functions correctly after you use this resolution, reinstall the program to restore functionality.

 

[Furr]

Going to download the Linux thing.

Its definitly a windows problem.

Have stuck another network card in and it won't gain an IP from the Voyager router but will from my Dlink thats connected via a linksys router acting like a switch....

Oh and this also works

their voyager troublesome router --- My Linksys Router - Their troublesome computer

but not this

their voyager troublesome router --- Theirtroublesome computer

but this does

their voyager troublesome router --- My own computers

 

[inactionman]

Sounds like both the computer and the routers are POS! I hate shite equipment. I mean you can't get much more simple than an implementation of DHCP, to cock it up...

And it didn't work when you set everything on the computer to be static addressing? That's what I'd normally do to avoid spending money on this problem. It must be a really cheap network card!

 

[smurkin]

Did you repair winsock?

 

[Furr]

Yup didn't fix it...

Installed a new NIC network card and disabled the onboard network device and it works now...

Took the easy option.

 

[smurkin]

n1

 

[SheepCow]

Out of interest, what make is the onboard NIC?