On Jan 26, 6:32am, "Ace Fekay [MVP]" <PleaseAs...@SomeDomain.com>
wrote:
> Innews:7a500506-b9e8-4db8-9f9d-2a12701e70b6@e25g2000prg.googlegroups.com,
> pink0.pall...@libero.it <pink0.pall...@libero.it> typed:
>
>
>
>
>
> > thank you for the reply and sorry if my question was not clear.
> > So, we have a class C dns so we are not ISP dependent and infact we do
> > not have any AD errors on this side
> > back to my question:
> > two servers:
> > A (192.168.1.200) is fast B (192.168.1.199) is slow
> > DFS-RDC share on both servers
> > DNS AD integrated on both servers
>
> > what suddnley happens is that my.domain.com is sometimes seen by
> > workstation as 192.168.1.200 and sometimes as 192.168.1.199
> > this means that the DFS share becomes \\192.168.1.200\share\myprofile
> > or \\192.168.1.199\share\myprofile
>
> > this means that clients resolvs my.domain.com as 192.168.1.199 use
> > the server B (slow) as file server
> > my question is if there is a way to have 192.168.1.200 as default
> > answer if a client request for this query
> > and use the .199 only if the server A is unavailable.
> > Looking inside the DNS configuration I saw that "priority" value to
> > check, but it seems not to work
> > now I am trying playing with the netlogon GPO settings but I don't
> > know if it the right way
>
> > thanks
> > (i used 192.168.1.x only as example, we have real addresses)
>
> Your AD DNS domain IP will show up as both 192.168.1.200 and 192.168.1.199..
> Why? That is the domain LdapIpAddress. That can be found under the
> mydomain.com zone as:
> (same as parent) A 192.168.1.200
> (same as parent) A 192.168.1.199
>
> Do not delete them. The netlogon service registers one for each DC in teh
> domain. Besides, you are using DFS, which relies on fault tolerance by
> having more than on esource. If one server is down, your DFS shares will
> still be available.
>
> If you want 192.168.1.200 to always answer, you have to make some reg
> changes to the netlogon reg keys.
>
> 306602 - How to Optimize the Location of a DC or GC That Resides Outside of
> a Client's Site [Includes info LdapIpAddress and GcIpAddress]: Use this to
> set the good DC's LdapIpAddres priority higher than the bad one.http://support.microsoft.com/?id=306602
>
> Download details Windows Server 2003 Active Directory Branch Office Guide
> v1.1:http://www.microsoft.com/downloads/d...D=9353a4f6-a8a...
>
> Ace- Hide quoted text -
>
> - Show quoted text -

Ace, thank you for your reply.
I have been told how roughly DFS works: it seems that at logon the
workstation asks which are the DC that act as DFS namespace holder,
then with a simple ping the workstation uses the "nearest" DC
Ok, It is true I am using the DFS technology as backup server which
maybe is not properly correct, but I think it works fine, but if the
workstation pings the nearest server how can I choose the "primary"
and "secondary" ?

I think your hints are good for DCs located in different sites, while
my ones are in the same site, same subnet, same switch. I know this is
bad but we have to wokr with the resources we have :P

thanks