A
anonymous
I have two XP machines on my home network. The Event Viewer on XP box#1
shows a rash of attempts by XP box#2 to declare itself the Master Browser,
forcing an election. What causes this rebellious behavior?
I'd prefer box#1, which is my desktop and hard-networked to the router, to
remain Master over the other stations, which are wireless laptops. (All
boxes stay on roughly 24x7). I'm reluctant to override the "AUTO" parameters
and declare one the master...but I will if its important.
The only other clue I have is that box#2 was having trouble maintaining its
wireless connection -- and maybe, failing to hear the Master but knowing its
part of a network, tries to step in -- and then regains its connection, so
that box#1 hears the declaration? Is that how it works?
Is there significant degradation due to this contention, or is this normal
sausage-making that I just shouldn't worry about?
shows a rash of attempts by XP box#2 to declare itself the Master Browser,
forcing an election. What causes this rebellious behavior?
I'd prefer box#1, which is my desktop and hard-networked to the router, to
remain Master over the other stations, which are wireless laptops. (All
boxes stay on roughly 24x7). I'm reluctant to override the "AUTO" parameters
and declare one the master...but I will if its important.
The only other clue I have is that box#2 was having trouble maintaining its
wireless connection -- and maybe, failing to hear the Master but knowing its
part of a network, tries to step in -- and then regains its connection, so
that box#1 hears the declaration? Is that how it works?
Is there significant degradation due to this contention, or is this normal
sausage-making that I just shouldn't worry about?