View Full Version : File Sharing/Name Resolution problem


Arthur Smith
10-20-2005, 04:32 PM
Here's my layout:

3 Windows Server 2003 Domain Controllers, all Global Catalog servers,
all same domain. All servers CAN ping all other servers by name.
However, Server2 cannot SMB browse or map network drives (by name) to
Server1. This works from Server1 to Server2, and all other
combiniations. Server1 is the PDC holder.

When i browse "My Network Places" on Server1 or Server3, i see all
comptuers in the domain. When i browse "My Network Places" on Server2,
however, i see only Server2.

I thought this was a DNS issue, and did fix some DNS problems along the
way, but I still have the original issue of not being able to get to
shares on Server1 by name, from Server2.

I CAN browse to the IP of Server1, AND the FQDN, Server1.domain.wan...

I don't know what else to check...


thanks in advance,

--acorn

Diane Walker
10-27-2005, 09:16 PM
Arthur,

Make sure you setup WINS entry at these servers.

"Arthur Smith" <arthur@somethingcool.com> wrote in message
news:OnEr6sY1FHA.1564@tk2msftngp13.phx.gbl...
> Here's my layout:
>
> 3 Windows Server 2003 Domain Controllers, all Global Catalog servers, all
> same domain. All servers CAN ping all other servers by name. However,
> Server2 cannot SMB browse or map network drives (by name) to Server1. This
> works from Server1 to Server2, and all other combiniations. Server1 is the
> PDC holder.
>
> When i browse "My Network Places" on Server1 or Server3, i see all
> comptuers in the domain. When i browse "My Network Places" on Server2,
> however, i see only Server2.
>
> I thought this was a DNS issue, and did fix some DNS problems along the
> way, but I still have the original issue of not being able to get to
> shares on Server1 by name, from Server2.
>
> I CAN browse to the IP of Server1, AND the FQDN, Server1.domain.wan...
>
> I don't know what else to check...
>
>
> thanks in advance,
>
> --acorn