DFS Share Publishing

[Guest]

Hello
I have setup two windows 2003 AD Controllers, AD gets replicated OK. Both are global catalogs as well
Have setup DFS which replicates fine as well, DFS share is \\mydomain.com\Dat

I am testing this thing now on how it is redundant and notice this
When 2 AD Controllers switched on all goes good. When one of them gets disconnected,
workstations can no longer access \\mydomain.com\Data for upto 3 minutes and then it starts working
I have noticed whenever i ping mydomain.com it resolves to one of the domain controllers(second DC

Should DFS Published share be constantly available after one of the servers dies? Perhaps i have not configured something.
Or is it normal for it go offline and then come back few minutes after one of the controllers dies

Thanks

 

[ptwilliams]

The DFS client caches the DFS referral -and you set this value in DFS.
Perhaps this is the issue?

Also, resolving the domain name, and choosing a referrer, are a different
thing...


Paul.
_______________________________

Hello!
I have setup two windows 2003 AD Controllers, AD gets replicated OK. Both are global catalogs as well.
Have setup DFS which replicates fine as well, DFS share is \\mydomain.com\Data

I am testing this thing now on how it is redundant and notice this:
When 2 AD Controllers switched on all goes good. When one of them gets disconnected,
workstations can no longer access \\mydomain.com\Data for upto 3 minutes and then it starts working.
I have noticed whenever i ping mydomain.com it resolves to one of the domain controllers(second DC)

Should DFS Published share be constantly available after one of the

servers dies? Perhaps i have not configured something..

 

[igor]

Ah yes, checked that too, made it to one second. Still, same effect.

What it looks like is this:
Say for example, a workstation has authenticated through AD Controller 1,
(and you check by 'set L'),
if this AD Controller goes down then the workstation loss access even to
other AD Controller's shares.
Same thing happens if it has authenticated through AD Controller 2 and if
this one goes down.

I guess the problem lies in here:
IF Windows XP workstation authenticates through one of the domain
controllers, then it sees this Controller as the only Controller available.
If this controller goes down, then it may take even a couple of reboots
before this workstation gets quick access back into Domain and the DFS
Share.

Is there a way to make it so that it knows there are two Controllers
simultaneously?

Thanks

 

[ptwilliams]

I assume, that DFS roots are located through DNS Subnet Prioritisation and
DNS Round Robin when in the same site; after all, you're just querying the
DNS server for an address of the DNS name. I've seen many people ask the
question of how they can force DFS to use a specific root server to no
avail; this simply cannot be done (in 2k at least, I've yet to get to grips
with 2003 DFS).

What you are describing seems to me to be a lack of redundancy in DNS. If
the logon server goes down, where is the client pointing for it's DNS? That
is, in the TCP/IP settings, how many alternate DNS servers are listed.
There should be a minimum of two for redundancy purposes -if one goes down,
the resolver will look to the other one.

It's not that the client sees only the logon server, it is down to how sites
are configured. If there's only one DC in a site, then yes, this will
always be accessed first. If there are two, it comes down to Round Robin
DNS, and Subnet Prioritisation if there are multiple subnets to a site.


--

Paul Williams
_________________________________________
http://www.msresource.net - Under construction, but coming soon...


Join us in our new forums!
http://forums.msresource.net
_________________________________________