Re: W2K3 DC not playing with member W2K3 Server

The member server (DNS is *not* installed on this machine) takes AGES
to log on to the DC and intermittently loses connection to the DC. I
have checked every conceivable KB article for this issue but nothing
strikes me. I have checked and re-checked the ipconfig and nothing.


AD client MUST point to the DNS server set up for the AD domain ONLY. This
member server *is* an AD client. The symptoms you describe indicate that
this member server is NOT pointing to the DNS server set up for the AD
domain (DC1). Of course DC1 *is* a member of the AD domain and it has DNS
installed so it should also point to itself for DNS in the properties of
TCP/IP for DNS resolution so it can register the SRV records AD clients MUST
find in order to *find* the domain.

Your clients are looking for those srv records. That is what is taking so
long to log in, it appears they are looking in the wrong place.

hth
DDS W 2k MVP MCSE

<carltoncl@xxxxxxxxx> wrote in message
news:1155754278.696850.253610@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
I have two servers, both identical Dell 1950 Poweredges, both running
W2K3 R2. One is a DC (10.10.61.2, machine name "DC1") running
integrated DNS the other is a plain vanilla member server (10.10.61.5,
machine name "CRM"). I have two NICs on each box but I have disabled
one controller on each for now.

The AD DC works fine, no errors logged, ipconfig/netdiag/dcdiag all
great, nothing wrong at all, life is lovely with it.

The member server (DNS is *not* installed on this machine) takes AGES
to log on to the DC and intermittently loses connection to the DC. I
have checked every conceivable KB article for this issue but nothing
strikes me. I have checked and re-checked the ipconfig and nothing.

The errors reported in the event log on the member server include:

1. Netlogon (5719)
2. W32Time (29)
3. SMTP (7022)
4. Userenv (1053)

But it takes a long, long time (10+ minutes) for the member server to
join the DC. All A and PTR records are created and accurate.

On those occasions when it does connect succesfully, the connection
will sometimes disappear for a few minutes and come back.

I do not have any other programs installed on the servers except W2K3
R2. Connection is via a Dell 2724 switch in unmanaged mode. All
hardware has been tested and is clean and operational.

This is driving me nuts - anyone?



.

Relevant Pages

  • Re: Remote Web Workspace
    ... Your DNS is definitely wrong. ... the Client computers should point to the server LAN NIC. ... > Ethernet adapter Server Local Area Connection: ...
    (microsoft.public.windows.server.sbs)
  • Re: Lost Resources
    ... Sorry, but i am talking about the client in the site, not your connection. ... This posting is provided "AS IS" with no warranties, ... Connection-specific DNS Suffix. ...
    (microsoft.public.windows.server.active_directory)
  • Re: Basic, yet detailed, Tor questions.
    ... tor client residing on your machine securely encrypts everything ... anyone observing your connection) can see is encrypted data traveling ... between you and your first tor node. ... Ideally, and typically in socks4a, the tor exit node does DNS ...
    (alt.privacy)
  • Re: Applying computer settings - SLOW
    ... automatically from the SBS DHCP server. ... > far as adding the client machines to dns I had to manually add them ... > they are pre-windows 2000 and do not register themselves in dns. ... > adapter Local Area Connection: ...
    (microsoft.public.windows.server.sbs)
  • Re: Creating a Virtual Domain
    ... "ipconfig /all" results for the DC and client virtual PCs respectively at ... Ethernet adapter Local Area Connection: ... Connection-specific DNS Suffix. ... > In general domain controller must also use Active Directory DNS (and _not_ ...
    (microsoft.public.windows.server.networking)