Tech Support Forum banner
Status
Not open for further replies.
1 - 6 of 6 Posts

· Registered
Joined
·
2 Posts
Discussion Starter · #1 ·
I know some people have posted on similar issues but my issue is a little different and I thought someone might be able to help.

I am running Win2k Pro SP4 on a P3 Dell Latitude with Mini PCI 1150 series wireless card. I have a linksys wireless router that has worked great for the last couple of years.

My wireless and wired connections were working great on this computer until a couple of weeks ago when I installed the sygate personal firewall. I had isuess getting on the internet when the program was intalled so I uninstalled it. Ever since that, my wireless card refuses to pick up a wireless connection. Other computers can connect wirelesslly but my wireless card won't even see the network. Netstumbler also fails to see the network (which tells me it's a problem with the wireless card)

I have re-installed drivers, removed the card (both physically and in windows), re-installed services and protocols but nothing seems to be working. I am not sure if the personal firewall corrupted my connection (or if it's still restricting it) or if that's a coincidence. The kicker is that the WIRED connection works fine on the laptop. It's the wireless connection that seems to have major issues.

The error message associated with the wireless card is the dreaded "Network Cable Unplugged"

Any thoughts? Any help would be greatly appreciated.

Regards,
John
 

· Global Moderator
Electronic Design
Joined
·
52,684 Posts
Are you sure the "Network Cable Unplugged" isn't simply because you have the network cable disconnected when you're running wirelessly?

If this is XP-SP2, let's try a couple of fixes.

TCP/IP stack repair options for use with Windows XP with SP2.

For these commands, Start, Run, CMD to open a command prompt.

Reset WINSOCK entries to installation defaults: netsh winsock reset catalog

Reset TCP/IP stack to installation defaults. netsh int ip reset [log_file_name]

Note: the log_file_name needs to be specified, e.g. netsh int ip reset reset.log

If that fails, you could also try the WINSOCK fix.

Automated WINSOCK Fix for XP

Automated WINSOCK Fix all Windows Versions
 

· Registered
Joined
·
2 Posts
Discussion Starter · #3 ·
Nope, the "network cable unplugged" message is associated with my wireless connection. My regular ethernet connection shows up normal, and I have it connected right now.

I'm running Windows 2000 SP 4 so the netsh winsock command doesn't work.

I tried to fix the TCP/IP stack with that program but it found no issues.

-John
 

· Registered
Joined
·
96 Posts
Right clik the wireless conection and go to advanced. See if use windows to control connection is checked or unchecked.
If you are using 3rd party software it should be unchecked. if not it should be checked.
Also if you have not entered the correct WEP key and are using WEP it wont work either.
 
1 - 6 of 6 Posts
Status
Not open for further replies.
Top