RE: Multihomed DC

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

Hi

I have already unchecked that box and it still appeared to reregister
itself, do I need to manually delete this record from every single DNS AD
integrated server or should the removal replicate automatically - I don't
think we did that last-time, just deleted it from that server's DNS server
and assumed it would replicate automatically, could it have replcated back
from one of the other servers?

Regards
Chris

"Dragos CAMARA" wrote:

hi,
on the nic wich you dosen't want to be register on dns go to tcp/ip
properties advanced tcp/ip settings dns tab and unchek Register this
connection's addresses in DNS.
--
Dragos CAMARA
MCSA Windows 2003 server


"Christopher Haydon" wrote:

"Christopher Haydon" wrote:

Hi

We have network of 9 DC and 140 XP Pro PCs linked by a MPLS VPN, one of the
DCs is our Exchange server and is in managed hosting at our ISP and is
multihomed as 172.16.16.3 (MPLS) and 192.168.17.53 (datacentre management
subnet). When you try to contact the server some of the time it is resolving
to the wrong IP address, thus because 192.168.17.x is unroutable from the
MPLS it doesn't work.

We have modified the hosts files on the DCs so that they read

172.16.16.3 server-02
172.16.16.3 server-02.network.local

this has fixed the problem on the DCs but the workstations are still getting
the wrong address part of the time, short of doing this on all the
workstations is there a more practical solution.

Kind regards
Chris

I should probably add that the only thing that the management interface is
used for is for the ISP's staff to get access for updates etc, all the rest
of the traffic goes onto the MPLS, either to us or the internet.

In the DNS records there are 2 A records for the exchange server one for
each IP address, we tried removing the erronious one and it resolved it
briefly until it presumably reregistered in the DNS. I can't however find how
you would stop a 2003 DC registering all its interfaces.
.

Relevant Pages

  • Issues migrating SBS 2003 domain to Server 2008 Standard
    ... We are stuck migrating our SBS 2003 domain to Server 2008. ... Fatal Error:DsGetDcName (SRV-EXCH) call failed, ... Verify your Domain Name Sysytem (DNS) is ... network connectivity to a domain controller. ...
    (microsoft.public.windows.server.sbs)
  • Re: AD management snap in cannot find DC (netdiag /v workstation)
    ... The name.local entries are used by my apache server to implement ... change button, more button, the "Primary DNS suffix of this ... Attr: subschemaSubentry ... Owner of the binding path: ...
    (microsoft.public.windows.server.active_directory)
  • Re: AD management snap in cannot find DC (netdiag /v workstation)
    ... button, more button, the "Primary DNS suffix of this computer", it should ... The Security System could not establish a secured connection with the server ... Attr: subschemaSubentry ... Owner of the binding path: ...
    (microsoft.public.windows.server.active_directory)
  • Re: AD management snap in cannot find DC (netdiag /v workstation)
    ... DNS Host Name: tonyb-pc.imageproc.imageproc.com ... Testing IpConfig - pinging the DHCP Server... ... Attr: subschemaSubentry ... Owner of the binding path: ...
    (microsoft.public.windows.server.active_directory)
  • Re: Issues migrating SBS 2003 domain to Server 2008 Standard
    ... Since you have migrated to standard server 2008 you would be better served posting in a Standard server NG. ... Event String: ... Verify your Domain Name Sysytem (DNS) is ... network connectivity to a domain controller. ...
    (microsoft.public.windows.server.sbs)