Networks

Ask something
Discussion Locked

WLAN - RF OK, but no data

0 helpful
6 replies

by scrass

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I am using WinXP and have two NICs. One is wired and the other is wireless. My wireless card has suddenly stopped connecting through TCP/IP. The RF connection is good, but I cannot connect to anything through TCP/IP. I followed the MS KB article 314067 and determined the folwing:

I can ping the 127.0.0.1 and the IP of the card itself and get responses. I do not get responses from any other IP address. My wired card works fine. I do not get a response when I ping from the WLAN card to the wired card. I do not get a response when I ping the gateway.

The TCP/IP stack is working (since the wired card works). It's only the WLAN card that does not. I did try two other WLAN cards and got the same results. Is there a virus that can cause this?

Someone please save me from having to wipe my drive and reinstall.

6 replies

by jdclyde

Is the wired NIC plugged in while your trying to use the wireless? I have seen on laptops if you try using both, it is almost like windows doesn't understand which it should use so it doesn't use either.

Disable you wired nic and try the wireless again.

Are you using the software for the wireless or the MS software to connect? DON"T use the MS software.

In the MS software there is a check box about connecting to unsecure access points. Is this selected?

Turn off ALL firewalls and try again.

Try the wireless card in a different PC if available. Are the cards NEW? If so, you can all the vendor for support and they may have an answer for you. If you have this problem, odds are someone else has too.

Have you downloaded the most recent drivers and firmware for the wireless nic? Access point?

Last thing I can think of. I HAVE seen adware stop network connections. Load a spyware removeal tool (I use AdAware), boot to safe mode and do a full scan.

Look in msconfig for anything running at bootup that does not HAVE to run at bootup.

by scrass

My wired card was the problem as you said. When I disabled the wired card (I'm not using it anyway), the wireless immediately began working. In my case the wired card was installed but not connected to the network. Windows was still trying to send outgoing requests via the wired card even though it was not connected. Think I should call Bill G. and let him know? :)

I'll have to remember that one. This was a stumper!

Thanks for your help.

This discussion is closed to new replies.