Lurid tale of sex and wireless connection not surviving system stand by sleep mode!!!

[robrecht]

OK, all you smart computer guys (& gals?), our ancient D-Link b wireless network from the early 21st century is still serving the Robrecht family well.

EXCEPT, my wireless connection no longer reconnects after stand by sleep mode (don't like to reboot). It says I have a good connection but no Internet or email.

Any simple things I can try?

Free beer for anyone who can come up with a simple solution.



Here's a little bit of history (for those that dare):

I recently re-installed XP (SONY partition problem, don't ask), and Windows didn't seem to be able to configure my wireless network so I let D-Link tech support walk me through it using their air utility software (latest driver for wireless card installed). Everything was fine until the little automatic update guy who lives in the bottom right corner of my computer screen decided it was finally time to install Service Pack 2. Now, for some reason, the wireless connection works fine every time I reboot my computer, but it doesn't come back on if I put my computer into system stand by sleep mode and then start it back up again. OK, not the end of the world, but I tend to be rather impatient and don't like waiting around for my computer to reboot when I could be already reading and posting here at HondaPilot.org. Called nice friendly D-Link technical support back and they're getting a little impatient with me, referring me to some pay computer help line. What do I expect from out of date equipment that cost me nothing after rebates (actually I think I made money on the deal)? Well, I could update the router firmware again but I'm afraid of trying to set up my network with Windows again and D-Link doesn't seem to be enjoying our late night chats as much as before. Besides, this was never an issue before with the old firmware. The real issue must be incompatibility between the old firmware and Service Pack 2 so I guess I should update my firmware--who knows maybe Windows will then be able to automatically configure my network when I have new firmware? But maybe not. What the hell is firmware anyway? It's obviously not software but it can't be hardware or at least it would have to be really small to fit through the cable modem wire or cable for short. And there was a driver for the wireless card but I don't remember having to install anything for the router in the first place, so why should I have to update what never had to be installed in the first place? It might be an Internet conspiracy. So I'm kind of opposed to firmware in principle. But mostly I don't want to get up off the couch and connect to the wired network in the kitchen and go through hours of grief. So somebody please tell me there's a simple solution, some little toggle switch buried underneath 5 or 6 different layers of arcane and labyrinthicical menus. Come on, an easy solution, please?

Don't forget the free beer and lurid sex:

[robrecht]

Originally posted by LChisum in another thread
robrecht, I've experienced something similar with my laptop (different hardware maker). If you have a tray icon for DLink, try right clicking on that. It may then display your network, and you can click on it to restart it. Another variation is that from the tray icon, you can disconnect, then reconnect to your network again.

Larry

EDIT: robrecht, where the heck did your post go? You must have found an easy answer.

I decided to start a new thread before I saw your post 'cause I didn't think anyone would read it at the end of that other long thread, which really wasn't that specific.

[N_Jay]

Have you tried teh "Repair" button on the network adapters properties window (and a few other places).

You may also try assigning it a fixed IP.

[john802]

Maybe the firewall of XP sp2 is the problem. Try reconfiguring the settings of the firewall of XP sp2.

[robrecht]

Originally posted by LChisum
robrecht, I've experienced something similar with my laptop (different hardware maker). If you have a tray icon for DLink, try right clicking on that. It may then display your network, and you can click on it to restart it. Another variation is that from the tray icon, you can disconnect, then reconnect to your network again.

Larry

Oh no, tried that, hit "Quit" and then "Wireless Network" and now I can't connect even after rebooting (posting this from my PDA). Larry, can you come over?

[ipomoea]

Originally posted by john802
Maybe the firewall of XP sp2 is the problem. Try reconfiguring the settings of the firewall of XP sp2.

Robrecht,

I'm with john802 on this one. We also have a D-Link (DI-614+-I know, I know, old technology 11 Mbps B-class Wi-Fi not as fast as your wireless G stuff, but I am saving up every penny for that new Honda truck that is out there, but that's another story).

Back to the Wi-Fi problems and sp2. DESPITE stern warnings from my employer's IT people, I went ahead and installed sp2 on my office desktop (XP Pro) as well as my home system (XP pro-desktop/XP home-personal laptop, XP tablet officelaptop)--identical D-Link-based systems. Sure enough, lost my Wi-Fi connectivity. Googled a few times and came across several hits. Basically, if you haven't already done it, 1) turn off Windows XP's firewall (I have Kerio installed on all my systems, so I have that part covered). Then, 2) if you have a laptop, there is a setting somewhere that enables you to turn off Windows XP sp2's wireless feature and let your own hardware's software utility do the connectivity for you. My laptop is powered down right now, but I will update this when I when I check on the settings later and if I forgot to document other steps that need to be performed, including what N_Jay cited as the "Repair" network button somewhere in the network settings. I think that's all I attempted to fiddle with---after that, wireless connections were seamlessly established. NB: anecdotal observation --- Wi-Fi seems to be a little bit snappier post sp2, pre wireless-G equipment, regardless.

[robrecht]

Originally posted by N_Jay
Have you tried teh "Repair" button on the network adapters properties window (and a few other places).

You may also try assigning it a fixed IP.

Repair doesn't seem to work I'm guessing because the network was configured with the D-Link utility after the Windows utility didn't seem to work. When I try Repair, I'm told that it could not be completed because the disabling of the wireless network could not be completed. Make sure the network adapter is properly installed (by Bill Gates personally).

Haven't tried a fixed IP, but it used to work fine on the dynamic IP. Don't want to ignore your advice, though, just not desperate enough to contact my ISP for a fixed IP yet. I don't think they know what that is, and I sure as hell don't!

[robrecht]

Originally posted by ipomoea


Robrecht,

I'm with john802 on this one.

I had already turned off the Windows firewall several days ago when SP2 came on the scene 'cause it seemed to be fighting with my Trend Micro Internet Security firewall , which is on but I'm not sure how to turn that off yet or if I really should. This is getting complicated.

[john802]

Do not turn off the Trend Micro Internet Security firewall. Once you turn off the xp sp2 firewall and reboot, just go the the network settings and check the repair button.

[robrecht]

Originally posted by ipomoea

Basically, if you haven't already done it, 1) turn off Windows XP's firewall (I have Kerio installed on all my systems, so I have that part covered).

Already did that several days ago when SP2 invaded my peaceful home.

Originally posted by ipomoea

Then, 2) if you have a laptop, there is a setting somewhere that enables you to turn off Windows XP sp2's wireless feature and let your own hardware's software utility do the connectivity for you.

I'm almost certain that's what the D-Link tech support did to get my wireless network up and running prior to the SP2 invasion (but after some 24 other pre-sp2 security updates had decided to implant themselves).

[robrecht]

Well, by disconnecting and then disabling the wireless connection, refreshing the connection, and a doing a few other things in a purely random and proprietary fashion, I have been able to run repair to completion and get connected again. Not hopeful that it will survive reboot, though, but here goes ...

Stay tuned for the never ending drama of lurid sex and wireless connectivity ...

Here goes ...

[robrecht]

Nope, still not surviving reboot ...

But if I run the D-Link Air Utility everytime after rebooting, I can get temporarily connected. When I first reboot, can't run the D-Link utility by clicking on it but rather need to right click to open. Think that means there's a conflict. Micro Trend firewall conflicting now when it wasn't before? Hmmm ...

No free beer yet

[mliechty]

IIRC, we always had problems with a wireless connection being 'bridged' in XP with our d-link AP. Look at network connections and see if there is a bridge configured. If there is, try un-bridging the connections and disabling the bridge.

Also, if you can get a temporary connection, open a cmd window and type "ipconfig /all" to see what is being configured at that point. When you lose the connection, try it again and see what has changed.

Edit: I would also try disabling _all_ firewalls to see if that is where the conflict really is. If this helps, try enabling one firewall at a time. I currently run both XP firewall and the d-link firewall without problems. It also seems to work with XP, Zone alarm, & d-link firewall.

[robrecht]

Originally posted by mliechty
IIRC, we always had problems with a wireless connection being 'bridged' in XP with our d-link AP. Look at network connections and see if there is a bridge configured. If there is, try un-bridging the connections and disabling the bridge.

I too have had this problem in the past, but by letting D-Link configure the wireless connection, that problem did not arise this time.

Originally posted by mliechty
Edit: I would also try disabling _all_ firewalls to see if that is where the conflict really is. If this helps, try enabling one firewall at a time. I currently run both XP firewall and the d-link firewall without problems. It also seems to work with XP, Zone alarm, & d-link firewall.

I wasn't aware that there was a D-link firewall, perhaps not on my antiquated system?

But I did, thanks to a couple of PMs from john802, disable my Micro Trend firewall (and antivirus) by uninstalling Micro Trend Internet Security. Then I rebooted and things were working again as they should, but it was pretty dicey there for a few minutes out there on the World Wide Web without any virus protection or firewall at all--I could've been killed! Then I reinstalled Micro Trend (whew!) and re-enabled the firewall (sigh of relief), updated the virus database (feeling pretty secure now) and, lo and behold, my wireless connection is now re-establishing itself after re-booting and ...

... drum roll please ...

... after stand by sleep mode!

So, I guess the moral of the story is that my antivirus firewall was bullying my wireless connection because it was there first. But when you put it in it's place by showing it who's boss (sorry if some of you non-geeks can't follow this highly technical explanation), then it behaves better and plays well with the wireless connection.

[robrecht]

So, john802, come on over tonight for all the free beer you want and we'll listen to Prairie Home Companion!



Not exactly lurid sex, but you'll still respect yourself in the morning.