Re: DNS dfs issue

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

I'm afraid we have to go back round the loop, because one of our assumptions
or test results is obviously wrong.
- We excluded the namespace, because the results depend on the dns not the
logon server. But maybe there is a phantom folder in the namespace. We could
check the namespace and also check the physical folders for the namespace.
- It is not sites, because the sites are set up correctly in AD, and the
clients are connecting to the local DC
- It seems to depend on the dns, but they should be the same. Also, not
every client at Site B (presumably with the site B dns) is affected. This
suggests it must be a client setting that affects the ability to resolve the
namespace. We did not confirm that clientA is also slow with the dns at site
B.
Anthony
http://www.airdesk.co.uk



"nntp.aioe.org" <x@xxxxxxxxxxxxx> wrote in message
news:f6jbc9$3q3$1@xxxxxxxxxxx
This is an ADI zone since it is the dns zone for the domain. The zone is
identical across the board and there are no replication issues.

No WINS and network properties are consistent.

The issue is reproducible.


Anthony wrote:
My only thought on this is that 5 minutes sounds like a failure or
timeout on perhaps one of the folders in the namespace. For that to
happen, the contents of the two DNS would have to be different. Assuming
it is an integrated AD zone, and there are no replication errors, I don't
see how that would happen.
You say that some clients are OK. Do you have WINS? Are some of the
clients' network properties different? Is this just an effect of caching
or is it repeatable?
Anthony
http://www.airdesk.co.uk



"nntp.aioe.org" <x@xxxxxxxxxxxxx> wrote in message
news:f6dmn1$pjd$1@xxxxxxxxxxx
Yes, two separate AD sites.

Servers = Server 2003 R2 SP2
Clients = Windows XP SP2

The domain controllers for SiteA are named:
dcA1.domain.local (10.0.0.1)
dcA2.domain.local (10.0.0.2)

The domain controller for SiteB is named:
dcB1.domain.local (10.1.0.1)

The workstation in SiteA is named:
clientA1.domain.local (10.0.0.3)

The workstation in SiteB is named:
clientB1.domain.local (10.1.0.2)

No matter which dns server I use on clientB1 its %logonserver% is always
dcB1.domain.local.

When clientB1 uses 10.1.0.1 as its only dns server, the enumeration is
slow (about 5 minutes).

When clientB1 uses 10.0.0.1 or 10.0.0.2 as its dns server, the
enumeration is peak (about 2 seconds).

No matter which dns server I use on clientA1 its %logonserver% is either
dcA1.domain.local or dcA2.domain.local

When clientA1 uses either 10.0.0.1, 10.0.0.2, or 10.1.0.1 as its dns
server, the enumeration is peak (about 2 seconds).

When clientB1 uses SiteB dns server to resolve UNC paths for the same
folders the enumeration is normal. Only when the servers are added as a
link to the dfs is when the problem arises.

A side note: the issue is not consistent across all workstations in
SiteB. Some workstations use SiteB dns to resolve the dfs root without
any problems.






Anthony wrote:
I was just checking that you actually have two separate Sites set up in
Sites and Services, but it sounds as though you do. What OS version is
it?
When it is slow,
- which site DC are you logged into (%logonserver%)
- is it also slow if you configure a client at site A to use the remote
dns in site B?
- do you have any delay at site B using site B dns to resolve the UNC
path of the same folders?
Anthony
http://www.airdesk.co.uk



"nntp.aioe.org" <x@xxxxxxxxxxxxx> wrote in message
news:f6c0uf$eba$1@xxxxxxxxxxx
The sites have a site link and each subnet set up according to site.
What do you mean in terms of correctness?

Anthony wrote:
Are your two locations set up correctly as two Sites in AD Sites and
Services?
Anthony
http://www.airdesk.co.uk



"nntp.aioe.org" <x@xxxxxxxxxxxxx> wrote in message
news:f6bp0f$h80$2@xxxxxxxxxxx
Seeing an issue with DFS folder enumeration. Here is the design.

Domain name is domain.local

All servers are in the same domain and there are two sites within
the domain.

2 domain controllers are in SiteA with IP addresses of 10.0.0.1 and
10.0.0.2

1 domain controller is in SiteB with an IP address of 10.1.0.1

All three domain controllers are namespace servers for
\\domain.local\files

When I configure a client in SiteB to use its local dc for dns
resolution (10.1.0.1) and try to access \\domain.local\files it
takes up to 2 minutes for the folders to enumerate.

When I configure the same client to use a remote dc for its dns
resolution (10.0.0.1) and access \\domain.local\files then it works
fine.

Netdiag, dcdiag, portqry etc... results successful on all dcs.


.

Relevant Pages

  • Re: Internet Speed
    ... I think what we are trying to say is to use the DHCP from the SBS and NOT ... DNS and WINS point to the SBS. ... as the server IP address. ... it is recommend to configure all SBS client computers' IP and DNS ...
    (microsoft.public.windows.server.sbs)
  • Re: 70-294 next week
    ... to another DNS ... server for at least ... client, which then ... configuration on the client. ...
    (microsoft.public.cert.exam.mcse)
  • Re: Dual NIC vs Single NIC
    ... |> 135919 DNS Server Search Order Functionality in Windows ... Thank you for helping me to correct the misunderstand of DNS query ... Thank you again for your supplement about the client DNS cache issue. ... This newsgroup only focuses on SBS technical issues. ...
    (microsoft.public.windows.server.sbs)
  • Re: Dual NIC vs Single NIC
    ... I will again argue that turning off the client DNS cache (0 refresh ... 261968 Explanation of the Server List Management Feature in the Domain ... Internet when the SBS server is offline. ...
    (microsoft.public.windows.server.sbs)
  • RE: Dynamic Update of A&PTR Records - Best Practice?
    ... The DNS server does not support the DNS dynamic update protocol; ... For Windows Server 2003-based computers, the primary full computer name is ... When one of these events triggers a DNS update, the DHCP Client service, ...
    (microsoft.public.windows.server.dns)