Re: Win2003DC and NT 4.0 BDC login trouble

Tech-Archive recommends: Fix windows errors by optimizing your registry

From: Tyler (Tyler_at_discussions.microsoft.com)
Date: 11/23/04 

Date: Tue, 23 Nov 2004 11:33:03 -0800

That was what I was thinkg but I wanted to check. When I go to upgrade my
production server my DNS will be located on an existing server so I won't
have this problem.

Currently all my clients and servers point to an external DNS source (ISP).
When we go to win2003 AD I am going to have an internal DNS. Is there any
way to push the new DNS settings out to all the clients or will I have to
touch all of them?

Once I have all my clients/servers pointing to the AD DNS do I need/should
add my ISP DNS server as secondary DNS servers? Is so on all machines or
just certain ones?

"Danny Sanders" wrote:

> > If I turn off the win2003DC I am unable to log into the domain from the XP
> > machine, I get the following error: The system cannot log you on now
> because
> > the domain XXXX is not available.
>
>
> Win 2k and XP clients MUST find the SRV records housed in the DNS server in
> order to "find" the domain.
>
> hth
> DDS W 2k MVP MCSE
>
> "Tyler" <Tyler@discussions.microsoft.com> wrote in message
> news:0AA7E5E8-F710-40E8-9EC8-FB0DDDADB870@microsoft.com...
> > In my test lab I have a win2003 DC which was upgraded from a NT 4.0 PDC.
> > (The PDC originally came from my production NT 4.0 domain as an extra NT
> 4.0
> > BDC). I also have a NT 4.0 BDC, win 2000 server with exchange 5.5 and a
> > Windows XP SP2 client.
> >
> > Win2003DC-DNS loaded here
> > WinNT 4 BDC
> > Win2000
> > WinXP
> > All three machines are pointing to the win2003 DC for DNS.
> >
> > If I turn off the win2003DC I am unable to log into the domain from the XP
> > machine, I get the following error: The system cannot log you on now
> because
> > the domain XXXX is not available.
> >
> > There is no DNS or wins on the NT 4.0 bdc.
> >
> > Any suggestions?
>
>
>

Relevant Pages

  • RE: VPN Clients Not Registering in AD DNS
    ... via VPN, the DNS records of the VPN clients are unable to be registered. ... Windows 2003 server? ... please let me know whether the clients get the IP ...
    (microsoft.public.windows.server.sbs)
  • Re: Permissions across 2 Forrest
    ... Primary DNS server on 1.x and the 18.x network along with DHCP and WINS. ... For instance ForrestA DNS is now a secondary for Forrest B and vise versa. ... WINS clients must use the same "WINS Database"* ...
    (microsoft.public.windows.server.active_directory)
  • Re: Still strange not fully working DNS server
    ... On none of the computers (both DC and clients) no firewall software is ... For the rest nothing happens in the DNS forward lookup zone. ... Is the new server Global catalog? ... The config you mentioned was not configured so I have configured ...
    (microsoft.public.windows.server.dns)
  • Re: Client installation frustration.
    ... not, apparently, any DNS lookup issues on my network. ... connection's addresses in DNS" and "Use this connection's DNS suffix in DNS ... is a file and print server that we have at one of our secondary sites. ... Is there any way to cancel all current requests to install clients? ...
    (microsoft.public.sms.admin)
  • Re: problem with xp clients and windows 2003
    ... We now have the cross cable running from the room's switch ... >> policy but logs into the server. ... >> aware that this is a DNS issue but I have TRIPLE checked the DNS ... >> If I do NSlookup from the problematic clients, ...
    (microsoft.public.windows.server.networking)