J
Jimmy
Configuration: 10 system peer-to-peer win2k pro network. All
systems are in a workgroup with the name WORKGROUP. TCP/IP works
fine on all systems. All systems appear to have identical network
settings (aside from fixed IP and network name).
There is *one* system in this network of 10 that cannot be seen
Network Neighborhood. Other systems can _not_ see it, it does _not_
see anyone in Net Neighborhood but itself. All other systems are
fully visible to all other systems.
Also, it cannot connect using the "windows" network name for a shared
connection. However, I *was* able to connect it to a share on one of
the other systems by using \\ip-address\sharename. I *was* also able
to connect to it from another system using \\ip-address\sharename.
What would stop it from showing up in 'network neighborhood' and from
being referenced by windows networking name ?
Thanks,
systems are in a workgroup with the name WORKGROUP. TCP/IP works
fine on all systems. All systems appear to have identical network
settings (aside from fixed IP and network name).
There is *one* system in this network of 10 that cannot be seen
Network Neighborhood. Other systems can _not_ see it, it does _not_
see anyone in Net Neighborhood but itself. All other systems are
fully visible to all other systems.
Also, it cannot connect using the "windows" network name for a shared
connection. However, I *was* able to connect it to a share on one of
the other systems by using \\ip-address\sharename. I *was* also able
to connect to it from another system using \\ip-address\sharename.
What would stop it from showing up in 'network neighborhood' and from
being referenced by windows networking name ?
Thanks,