S
steve.anon
This one is puzzling (and frustrating!) me. Any help or pointer would
be greatly appreciated. In a nutshell, the 'master browser election'
message in the event log ALWAYS (and this is reprocible) triggers my
wireless router to emit at a very low signal. Read on...
I have a buffalo WBR2-G54S wireless router. I used with 2
laptops running buffalos WLI-CB-G54S cards and a WLI2-PCI-G54S pci card
for my desktop machine. All running xp sp2 with latest official drivers
and all the patches. It works perfectly fine for 24-72 hours until...
.... one of the laptop gets the 'master browser election' message... and
5 seconds later ALL the machines on the network lose connection to the
router with a nice "Wireless LAN Adapter was disconnected from the
network" message in system log. That's ALL at the same time, and ALL
after exactly 5 seconds following the 'master browser error'.
Now I know few people would beleive me, so I waited for this to happen
3 times in row to post this message. And to make things even weirder, a
quick test with netstumbler shows that the router doesn't just go dead,
it simply starts broadcasting a very weak signal very sporadically
(every 3 minutes for 1 second or so).
Very obviously the election of the master browser kills the router. Any
pointer or help would be appreciated.
Steve.
be greatly appreciated. In a nutshell, the 'master browser election'
message in the event log ALWAYS (and this is reprocible) triggers my
wireless router to emit at a very low signal. Read on...
I have a buffalo WBR2-G54S wireless router. I used with 2
laptops running buffalos WLI-CB-G54S cards and a WLI2-PCI-G54S pci card
for my desktop machine. All running xp sp2 with latest official drivers
and all the patches. It works perfectly fine for 24-72 hours until...
.... one of the laptop gets the 'master browser election' message... and
5 seconds later ALL the machines on the network lose connection to the
router with a nice "Wireless LAN Adapter was disconnected from the
network" message in system log. That's ALL at the same time, and ALL
after exactly 5 seconds following the 'master browser error'.
Now I know few people would beleive me, so I waited for this to happen
3 times in row to post this message. And to make things even weirder, a
quick test with netstumbler shows that the router doesn't just go dead,
it simply starts broadcasting a very weak signal very sporadically
(every 3 minutes for 1 second or so).
Very obviously the election of the master browser kills the router. Any
pointer or help would be appreciated.
Steve.