Intel driver kills the DHCP on router?

Hi,
I have my Intel card for months, solved the usual issues (exchanged it with my brother's card - the same model, and everything and it works flawlessly in his notebook ) and had no issues so far with 9 and 10 drivers.
SO I used to have Intel ProSet 10 driver and client and everything worked great for a week or so. And then in the middle of my work I lost my connection, IP etc. The weird thing was that ALL COMPUTERS IN MY WIRELESS NETWORK (4) including my MDA PRO with 11b wi-fi, LOST THEIR WiRELESS CONNECTIONS! And could not reconnect. I mean every minute or so the router DHCP would try to set the IP addresses and computers would connect and then in a matter of seconds would loose connection again. I repeat ALL OF THEM! So I thought my Siemens Gigaset 515 router had joined his ancestors, but NO. The story goes on. Accidentally I forgot to turn on the wireless card on my notebook. Network was suddenly LIVE and kicking. Working as usual. All computers got their IP and no problems at all. I turned on my network card and everything happened again.
So I uninstalled Intel drivers, restarted, installed 9.0.3.0 and now everything is ok!

How in the name of the God my network card could mess the router so the whole DHCP on it went mad? And all that happened out of the blue sky. No reason whatsoever.

I have Intel 2915, router is Siemens Gigaset 515. Channel is 4, WPA-PSK, TKIP. No turbo. 54g link. I have set the key resend for every 30 secs, because my 11b MDA PRO wi-fi card won't work otherwise.

Any comments? Nick?

Cheers,

 

Not a single post. And I thought that it was interesting...

Well the last thing is that I reinstalled Proset version 10 back because somehow Intel Proset has lost all my profiles in the middle of normal work. It said it cannot access the profile database anymore. Now that is definetly the worst piece of software that I used to have on my notebook. I installed driver only and use Windows client now. It is faster, less memory used. I know some things are not supported, but I will deal with it when the need comes. Darn programmers.

 

Hmm, im not really sure.

I have been busy the last week, so i haven't been keeoing up with wireless as i would like to more.

Ill think on this issue, see if anything comes to mind.

Oh, and expect to see me back in wireless 24/7 again in the next few days

 

Hey Nick ! Looking forward to your post. Looks quite interesting to me. And it never happened again. I cannot recreate it again too. It just happened. Just in case someone stumbles on this thing - reinstallation fixes it.

Cheers,

 

It could just be a firmware fart. You know how software can have its hiccups.

Could also be an attack by a hacker. Maybe, just maybe.

ikovac you have an Intel card? I'm shocked~! I thought a guy like you would have gotten himself an Atheros by now.

If it happens again try reinstalling the firmware and do some reading on which firmware has which bugs, since new doesn't mean good.

Cheers,
Mike

 

Yeah Mike,
Have you read my weird experience post with switching the cards? Check here:
http://forum.notebookreview.com/showthread.php?t=35476

And it fixed my problem. Now I wanted to buy an atheros (quite cheap overhere too), but since I have fixed it it worked flawlessly. Now hacker attack? That should have come from my notebook, right? I didn't hack my network... Hm... Although that would be quite an experiment...

Firmware - you mean the router firmware - did that. Didn't change a thing before.

The strange thing is that my router was messed up and its DHCP went mad. I reset it and it didn't change - that means my notebook somehow managed to kill DHCP regardless the resets and network configuration. That is very dangerous in my opinion. Imagine large networks with such a client. It would be a nightmare. DHCP killer - the worst beast from the deeps of networking.

Cheers,

 

I think Mike is correct - possible possesion of some sort - might have even been your ISP having issues and your fix was coincidental (as I agree - the fix does not fit the problem resolution) - Overheating ...power spike , a plethora of maybes, as others have eluded to

I hate not being able to reproduce something - but if it is gone - I would likley leave it until it / if it happens again.

Good luck

PS: - Might be wise to get an old priest and a young priest

 

Guys, it happened again.

This time I just turned on my comp, did the first thing in the morning (read posts on NBR) and puff, wireless died - the same thing - all other computers in the house lost their connection. And after a minute or two here it is again, and then again dies. I turned off my wireless - all others working like before. The Ghost of DHCP came back. OK drivers ver 10 were installed first and the second time. No problems, I have 9.0.3.
Uninstalled 10. Installed 9.0.3. - the same. Restarted. The same. Uninstalled. Turned off. Installed 9.0.3. Works.

So it must be something with the 10 drivers and does it on a hardware level, because I had to turn off my comp completely in order to have it installed and working again.

Now both times I turned on the comp out of the hibernate with the MS unofficial patch for over 1GB ram hibernation issue. Both times my MDA PRO was synchronizing over USB hub. I had the external disk connected and Dreamweaver opened. On both occasions. I suspect something must be with the darn ActiveSync synchronization too, because it also creates a network of its own, and I don't have a clue how it does it.
But the main question remains - HOW DOES MY NOTEBOOK WHEN IS SCREWED FOR THAT OR THAT REASON MANAGE TO MESS UP THE DHCP ON MY ROUTER AND THEN ALL NETWORK COMPUTERS LOOSE THEIR IP?
I have never heard of it. I would bet one month ago that it is not possible and would loose all my money...

Cheers,

 

Guys, I think I have solved it.

I installed the Vista beta 2 as a dual boot and guess what - there the same thing happened on more occassions. No Activesync, no other software... So I was mad already and thought it must be the hardware problem and that did lead me to the problem. I checked the driver and the advanced settings. It was set to the ad hoc channel 11 by default for b and g networks. That reminded me that the router was also set to the channel 11 by default. And now my router for some reason was set to work on channel 4 as I wrote in the first post! The adhoc channel has nothing to do with my AP network of course.

I changed the router channel to 11 and since then no issues in XP or Vista.
Is it possible that different channels produce such behaviour with Intel cards and not any other? What is so magical about channel 11? Why Broadcom, Atheros and whatever it is in my MDA PRO work flawlessly on channel 4? Strange.

Cheers,

 

Intel just seems to be really, REALLY, sensitive to things. I say trash it and get yourself an atheros. DO IT, JUST DO IT~!!!!!!!!!!!!



Cheers,
Mike

 

Trust me Mike - I already went to the site and tried to buy - and it said out of stock. . Now it works. (Still)
Even in Vista. After resets and all kind of stuff with drivers and everything. Works.

And you'll be the first one to know if I ever buy an Atheros!

Cheers,