Name resolution

I have 3 locations A, B and C running Windows Server
2003. I can see site A and B ms explorer and I can ping
their names. However, I can not see site C from B or C
and I can see them through ms explorer, I can ping the IP
addresses. Any idea what is not set up properly on Server
at site C?

What do you mean by "see"? Are you refering to using the Windows Explorer
Network Places? If so, that process uses the Browser service. Do you have
a WINS server configured and all clients pointing to it?

-ds

"KM" <(E-Mail Removed)> wrote in message
news:834c01c43222$3147c340$(E-Mail Removed)...
>I have 3 locations A, B and C running Windows Server
> 2003. I can see site A and B ms explorer and I can ping
> their names. However, I can not see site C from B or C
> and I can see them through ms explorer, I can ping the IP
> addresses. Any idea what is not set up properly on Server
> at site C?

Not really enough info here to say! How are these locations connected?

Basically, just debug it one step at a time. Check the routing. Ensure
that you can ping any machine from any other machine. When that works, move
on to name resolution. If ping by name fails, start looking at DNS.

"KM" <(E-Mail Removed)> wrote in message
news:834c01c43222$3147c340$(E-Mail Removed)...
> I have 3 locations A, B and C running Windows Server
> 2003. I can see site A and B ms explorer and I can ping
> their names. However, I can not see site C from B or C
> and I can see them through ms explorer, I can ping the IP
> addresses. Any idea what is not set up properly on Server
> at site C?

Sounds like you have a NetBIOS name space problem. When you use MS Explorer or the Network places icon to drill down to the servers it pulls the names of the servers from a local broadcast or via a WINS server. You can review the name services in the any one of the resource kit docs for a full run down

The issue then is what is either blocking the remote servers name from entering into WINS or being broadcast acros the network. This could be a failure of the server loging to the correct Domain or if your using a workgroup not part of the correct group. The other direction is a device filtering NetBIOS name services

If you can't locate the problem you could just enter a static entry into WINS. Leave this as your last option.