----- Original Message -----
From: "Ian" <[log in to unmask]>
> Toomas, the articles you refer to seem to be directed at NetBIOS problems
> on Win2k setups. As far as I know, my home network cummicates via TCP\IP
> and it's running on XP Pro machines.
>
It is not NetBIOS but (netbios) name resolving service. Names what You see in
Network Neighborhood are NetBIOS names and there must be computer what
maps them to IP addresses. You probably could connect using IP address or
adding name to lmhosts file.
About David Gillet replay. Large systems are Primary Domain Controller
and Backup Domain Controller(s) what automatically come to Master Browser.
So there is much less problems as in LAN with P2P networking based same OS.
Newer OSes has given preference so if here is only one WinXP it comes to
Master Brower.
> However, as I posted to the list, last night, the situation has suddenly and
inexplicably
> righted itself. Unfortunately I have no idea what caused it to recover.
>
You write that there was loose cable what makes me even more think about
Browser
election conflict (aka war). Poor cable or NIC makes response to browser
election slow
and activated computer may make itself to mater browser. When on another
computer
connection gets better it may be another master browser and we have conflict.
In my case
small office LAN without PDC problem was that first person have laptop. He
come
connected ethernet cable and powered computer. All other computers were power
saving
mode and coulnd replay that they are Master Browser or come to Master Browser
(being
Potential Browser) in timeframe. So laptop take itself to Master Browser
level and when
user of computer what also 'think' that it is Master Browser come to work
Network Neighborhood
stopped to work as well as connecting by names.
Toomas
The NOSPIN Group Promotions is now offering
Mandrake Linux or Red Hat Linux CD sets along
with the OpenOffice CD... at a great price!!!
http://freepctech.com/goodies/promotions.shtml
|
