Get your fill of sci-fi, science, and mockery of stupid ideas
http://stardestroyer.dyndns-home.com/
http://stardestroyer.dyndns-home.com/viewtopic.php?f=24&t=46228
Netgear; damn I hate being new to a certain aspect of technology- makes you a n00b ....Dalton wrote:What brand modem is it? I used to have a problem with my Belkin choking all the time.
This fixed the dropped connections that I was having with my D-Link DI-624.A reader wrote in with a question to which I, too, sought the answer. The question concerns 802.11 wireless connectivity, and persistent connection drops. It's not big enough for a large article, so I'm writing it up here for the community. Alex reports:
I have a problem I know you gurus can help me with. I have a Linksys WRT54G b/g wireless router, and while it worked perfectly for months, now the connection routinely drops every 10 minutes. When it drops, I have to sometimes wait 3-4 minutes before my connection returns. The confusing part about this is that it only happens on one of my laptops, but not on all of them. I have reinstalled everything, but nothing solves the problem. Please help!
It just so happens that one of the laptops in the Orbiting HQ suffers from this very same problem, so I've been able to duplicate this problem on my Linksys WRT54G router, with a Centrino laptop running Windows XP, standing 5 feet from the router. In the quest to help Alex, I started investigating this matter, and sure enough, I found out that people all over various message boards are discussing the problem.
As it turns out, if you use the Microsoft Windows XP SP 1-based Wireless Zero Configuration service to manage your wireless (aka, the "built-in client"), you're probably running into a horrible bug that Microsoft calls "behavior by design." The gist of this is as follows: if your wireless network is set to not broadcast your SSID, Microsoft's wireless manager will periodically drop your non-broadcasting WiFi connection in response to the presence of a broadcasting SSID-based network. You won't fully associate with that network, but the service will pop-up and tell you that there are multiple wireless networks to join, even if you have removed all other networks from your preferred settings (this contradicts Microsoft's report, which says it only affects preferred networks). The upshot of this is that you, the smart user who changes his default SSID and then sets it to not broadcast, now gets dropped off your network when you neighbor shows up with his new D-Link wireless router and not only fails to change the SSID from default to something else, but does not turn off broadcasting, either. And the worst part is that this happens just about every ten minutes or so. What a joy.
Your options are two (2.5, really): you can set your own router to broadcast your SSID, which Alex did and it resolved the problem. Alternatively, you can stop using the Windows Wireless Zero Configuration service and instead opt for another wireless client, namely that which came with your wireless card. Additional testing revealed that if your wireless settings are already configured and correct, you can actually stop and then disable the Wireless Zero Configuration service. The wireless still works, but your Wireless tab will disappear in Networking properties. This solution is not ideal, but it could be used in a bind.
If your connection is dropping and you're not being asked to connect to another network, make sure that you have not checked the "Enable IEEE 802.1x authentication for this network" checkbox, as this can also cause problems (but was not the root cause of this issue).