• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Re-installing the TCP/IP & WINSOCK

nublikescake

Senior member
I am having problems connecting to my wireless router from my laptop. It can detect the wireless networks around my house and also my own wireless router but cannot connect to it. When I go to DOS and run "ipconfig", the "Ethernet adapter Wireless Network Connection" shows up as "Media State ...: Media Disconnected". I have tried to follow the following troubleshooting guide I found on the Internet. I have narrowed it down to the last step which means re-installing the TCP/IP stack. Is there a way to do it without downloading the entire 316MB Service Pack 3? Is there a way I can get just the TCP/IP stack portion from somewhere?

1. Verify everything has power - if either device has no power, windows will report media state disconnected.

2. Verify any NIC is correctly seated in the motherboard, that the BIOS on the motherboard supports it, and that the slot it's in is turned on (you can turn off PCI slots on some mobos.)

3a. If wired, verify wiring is not faulty, the internal wiring correctly paired, does not exceed rated length, and lacks line noise.
3b. If wireless, verify correct frequency and no interference.

4. Verify you're using the correct media and devices. IE, this error will occur if you're using a straight-through CAT5 instead of a cross-over between two computers/NICS. With wireless in mind, if you have the wrong type of wireless NIC, it might be broadcasting on the wrong frequency.

5. Verify devices are free of physical faults (bad RJ45 port, etcetera.)

6. For driver-dependent devices (ex. NIC), make sure software is correctly installed. If you have gotten to this step and there is no link-light on either of the devices, go back to step 1 and start over. If there no link light (no current between RJ45 jack and connector) then neither this step or any of the following steps will resolve the issue.

7. For firmware-dependent devices (ex. router) makes sure latest (or alternatively, least problematic if new firmware is buggy) firmware is correctly installed and working.

8. For driver dependant devices, make sure core operating system files are not corrupted; a corrupted stack may cause windows to incorrectly report the link as disconnected. Note that resetting TCP/IP & WINSOCK settings via netsh only resets the settings and such (ex. registry keys) pertaining to the stack - they do not fix a broken stack. To fix a broken stack, reinstall TCP/IP & WINSOCK (most easily achieved by simply reinstalling the latest service pack.)
 
Problem solved! It was in fact item number 6 in the list that was causing the problem. Re-installed the wireless NIC driver and voila! Thanks for your help though snikt.

Cheers
 
Back
Top