xp pro messes up the network

[u]

Our peer-to-peer network (containing my Win2000Pro desktop
that shares the dsl internet connection and assigns IP
addresses to the other computers, seven 98SE desktops, one
ME laptop, and one XP home desktop) works great, until an
additional XP Pro laptop is connected. Then all of a
sudden, the computer listing in the network neighborhood
disappears from every computer. We can still get around
the network either via mapped drives or via searching for a
specific computer name. The XP pro laptop has no shared
files or folders. Why does it do this to our network?

 

[Jack Turner]

You can try turning off the Browser Service on the other
machines (Right-click on My Computer, and select Manage,
expand Services and Applications, then click on
Services. Right-click on Computer Browser, and click on
Stop and set the startup type to Disabled.

Or you could edit the registry:
HKEY_LOCAL_MACHINE\System\ControlSet001
\Services\Browser\Parameters. Change IsDomainMaster to
FALSE, and MaintainServerList to No.

Repeat for ControlSet002.

Don't know if this will help, but it might be work a try.

Thanks, Jack

 

[Chuck]

Our peer-to-peer network (containing my Win2000Pro desktop
that shares the dsl internet connection and assigns IP
addresses to the other computers, seven 98SE desktops, one
ME laptop, and one XP home desktop) works great, until an
additional XP Pro laptop is connected. Then all of a
sudden, the computer listing in the network neighborhood
disappears from every computer. We can still get around
the network either via mapped drives or via searching for a
specific computer name. The XP pro laptop has no shared
files or folders. Why does it do this to our network?

Is there a firewall on the offending computer? Firewalls, if not properly
configured, will screw up the browser services, and file sharing. Configure the
firewall to allow file and printer sharing by opening the following ports: TCP
139, 445; UDP 137, 138, 445.

Cheers,
Chuck
Paranoia comes from experience - and is not necessarily a bad thing.

 

[Helen Megan]

Possibly because it is firewalled. We found we had to
strip the firewalls out to make XP Pro and 200 talk to
each other. You also have to have the right permissions
in Users and passwords.

 

[Hans-Georg Michna]

Or you could edit the registry:
HKEY_LOCAL_MACHINE\System\ControlSet001
\Services\Browser\Parameters. Change IsDomainMaster to
FALSE, and MaintainServerList to No.

Repeat for ControlSet002.

Jack,

whatever you do, do it only to the CurrentControlSet. The others
are only backups and will get overwritten soon.

Hans-Georg