Unsolved

This post is more than 5 years old

7 Posts

35535

June 20th, 2007 13:00

Wireless keeps disconnecting.

I have a D600 with the intel pro wireless 2100.  It is connecting to a Linksys WAP4400N.  The Linksys access point has power over ethernet and is connected to a Linksys SRW224P 24-port 10/100 + 2-Port Gigabit Switch.  I have configured the WAP4400N to only allow mac addresses that I have entered in the configuration to connect to it wirelessly.  I have updated the driver of the wireless card and installed Microsoft KB 917021 enabled WPA2 security.  All firmware has been updated on the switch and access point.  It initially connects fine and I get a good signal strength, then it kicks me off within a few minutes and my wireless network is no longer available.  I can search for wireless networks again, it will find it again, connect, and once again after a few minutes it kicks me off.  I have tried all the power settings as mentioned on Intel's website, also tried uninstalling everything including the adapter itself, tried different channels on the access points, still getting the same result.  Does anyone have any ideas why it would be doing this or what I need to do to get it to stay connected.  Any insight would be greatly appreciated.  Thanks.

2 Intern

 • 

7.9K Posts

June 20th, 2007 13:00

hard to say with disconnects.  sounds like you have SSID broadcast on (which you should!).  you might try generic things like changing the channel or using netstumbler to examine signal quality.
 
also, avoid mac filtering.  it's nearly worthless in terms of security and can at times create problems.  turn it off -- at the very least as a troubleshooting step.
 
are you using any other form of encryption?  I'm pretty sure the pro2100 doesn't support WPA2 but I could be wrong.

7 Posts

June 20th, 2007 14:00

I've tried changing the channels and still getting the same results. 
 
The odd thing is that this is only happening to my D600 with the intel pro wireless 2100 card.  I have a D620 with a intel pro wireless 3945 card and it does not have any problems at all--it can find the network, connect, and stay connected. 
 
Not using any other forms of encryption. 
 
The 2100 will support WPA2 if you have the latest updated drivers and have MS KB 917021 update installed.
 
I will try to turn off mac addressing just to see if it makes any difference.  Thanks.

2 Intern

 • 

7.9K Posts

June 20th, 2007 14:00

you're right on the wpa2, just rechecked.  i just assumed (incorrectly) that since you could use the 8through 10 series of drivers with that card that it wouldn't be supported.
 
and hey, once you get it working, you might as well switch to WPA2 to keep those pesky neighbors out.
 
edit: forgot to ask, are you using the latest driver from dell site or from intel (though they may be the same at this point).


Message Edited by NemesisDB on 06-20-2007 10:20 AM

7 Posts

June 20th, 2007 16:00

Changing the channels had no effect.
 
I believe the latest drivers can only be downloaded from Intel's website not Dell's--I could be wrong, but if I recall correctly there was only one version on Dell's website and the one on Intel's website had a later revision date so I would assume that it's a later version.
 
Still just disconnecting on the D600 with the 2100 card.  My D620 is fine and does not.
 
Could it be that the 2100 are just not fully compatible with the linksys equipment.

2 Intern

 • 

7.9K Posts

June 20th, 2007 17:00

well, if you're bored and really want to troubleshoot I suppose you could put the 2100 in the other machine.  personally I think I'd be too lazy to take that step given that you'd have to remove and reinstall drivers several times.

7 Posts

June 20th, 2007 18:00

I have noticed after doing some searching in the Dell forum and online, that I'm not the only one that seems to have this problem with the 2100 card.  Majority of the people have tried the power saving options and settings suggested on Intel's website and it has worked for them or they switch channels and it worked. 
 
I guess I will have to just keep tinkering around until I find a workaround that will hold the connection.
 
 
No Events found!

Top