Re: DNS Settings

Paul wrote:
The environment is NT 4.0 PDC after upgrading the PDC to the Windows
2003 DC, do I have to right away change the DNS settings for the
workstation to the internal DNS that points to the AD DNS. The
clients all have the Workstation using static Ip and Static dns and
DHCP server is not available.

Will the existing NT workstation and Windows xp clients able to
resolve the AD DC using the existing Wins from the PDC environment. I
am planning to run the DC in mixed mode environment where both the NT
and 2003 server will allow authentication. The reason I cannot change
the DNS settings on clients because there are so many and we don't
know the exact locations.

I really apprecaite for your help...

The NT workstations will be fine, but all XP clients must be changed to use
the internal DNS, because that is the only place they can find the Domain
Controller's SRV records. Until the XP clients are changed to using the
internal DNS, you can expect very long startup and logon times.
WINS is fine for finding the DCs A records but WINS does not support SRV
records, once an XP client is authenticated by a Win2k or Win2k3 DC, it will
start looking for SRV records and will not go back.


--
Best regards,
Kevin D. Goodknecht Sr. [MVP]
Hope This Helps
===================================
When responding to posts, please "Reply to Group"
via your newsreader so that others may learn and
benefit from your issue, to respond directly to
me remove the nospam. from my email address.
===================================
http://www.lonestaramerica.com/
http://support.wftx.us/
https://secure.lsaol.com/
===================================
Use Outlook Express?... Get OE_Quotefix:
It will strip signature out and more
http://home.in.tum.de/~jain/software/oe-quotefix/
===================================
Keep a back up of your OE settings and folders
with OEBackup:
http://www.oehelp.com/OEBackup/Default.aspx
===================================


.

Relevant Pages

  • Re: Long Pause when accessing mapped drives -- Please Help
    ... ipconfig/all from server, good workstation and bad workstations. ... both clients experiencing this problem have a public DNS ...
    (microsoft.public.windows.server.sbs)
  • Re: Could this be a DNS issue?
    ... clients literally pull them even though it feels like pushing to the admin ... All internal DNS clients must use STRICTLY the internal ... The RPC server is unavailable.. ...
    (microsoft.public.windows.server.dns)
  • Re: Applying Personal Settings
    ... on the affected workstation, ... Open a cmd prompt, ipconfig /flushdns. ... started setting up everything as i normally do for other clients, ... with ipconfig results pointing gateway & dns to ...
    (microsoft.public.windows.server.sbs)
  • Re: Event ID 5719: No Windows NT or Windows 2000 Domain Controller is available for domain .
    ... The workstation gets its networking information from DHCP that, in turn, ... the DNS has Enable Forwarders and the ... I don't believe the problem to be at the server end though. ... security settings) I messed with and that policy has since been removed. ...
    (microsoft.public.win2000.security)
  • Re: Applying Personal Settings
    ... different workstation and plug it into troubled workstations wall socket. ... started setting up everything as i normally do for other clients, ... with ipconfig results pointing gateway & dns to ...
    (microsoft.public.windows.server.sbs)
Loading