Router Issue

Is it possible for a router's wired connections to fail, yet still have the wireless function of the router working correctly? I have a wireless linksys router that is also hardwired to a PC and Vonage phone system. I can access the internet from two different laptops in my home, but all of a sudden my phones are down and I can not connect to the internet from my desktop (indicates network cable is unplugged).

I have checked all wiring (which has not been touched in 2 years), rebooted, unplugged my cable modem, router and vonage device.... all to no avail. The wireless function of the router is still effective, but not the phones or wired desktop.

Could a local technician test the router and would it be cost effective, or is it a safe assumption the router has died and simply purchase another router?

Thanks

 

Try cable swaps, and then replace the router if still issues, generaly its not worth repairing or having a router looked at for repairs.

 

After further troubleshooting, I’ve found my router to be in good order. I believe I have 2 separate issues/problems. 1) My VoiP device is shot, and I’ll need to replace it through Vonage. 2) The Ethernet plug on my 8-10 year old XP system is shot… the small light doesn’t even come on when the cable is plugged in.

I purchased a new Gigabit PCI Adapter, installed it and the software… and have another problem <grin>. Although I now see a light when the Ethernet cable is plugged in, and Device Manager reflects the Broadcom 440 10/100 Integrated Controller is working properly… Network Connections states “Network cable unplugged”

I can take that cable out of the desktop and connect it to either of my laptops (disconnecting my wireless connections first) and quickly connect to the Internet. That alone tells me the router and cables are fine. Any ideas why my desktop keeps telling me the cable is unplugged?

Thanks

 

http://www.ezlan.net/faq.html#unplugged

 

Thanks. Mystery resolved. What a dummy I am. I didn't install the new ethernet PCI Adapter correctly. It wasn't set properly on the motherboard. It only took me a few hours <grin> of troubleshooting before I decided to open up the CPU again and check the socket.