Re: Inplace Upgrade

in a AD environment DNS is needed! No DNS means troubles and performance
issues

also see:
http://blogs.dirteam.com/blogs/jorge/archive/2006/05/01/912.aspx

--

Cheers,
(HOPEFULLY THIS INFORMATION HELPS YOU!)

# Jorge de Almeida Pinto # MVP Windows Server - Directory Services

BLOG (WEB-BASED)--> http://blogs.dirteam.com/blogs/jorge/default.aspx
BLOG (RSS-FEEDS)--> http://blogs.dirteam.com/blogs/jorge/rss.aspx
------------------------------------------------------------------------------------------
* This posting is provided "AS IS" with no warranties and confers no rights!
* Always test before implementing!
------------------------------------------------------------------------------------------
#################################################
#################################################
------------------------------------------------------------------------------------------
"Paul" <Paul@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:48A9F8AE-283F-4579-8552-60CA58B13E56@xxxxxxxxxxxxxxxx
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...


.

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: 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: 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)
  • Re: URLs and Sets do not mix - DNS lookups are compulsory
    ... and the DNS resolution was taking some time to ... the hostname is specified. ... the environment, with no access to the internal DNS servers. ... Store the string verion of the URL instead of the URL itself. ...
    (comp.lang.java.programmer)
  • Re: DNS Settings
    ... do I have to right away change the DNS settings for the ... workstation to the internal DNS that points to the AD DNS. ... Will the existing NT workstation and Windows xp clients able to ... the internal DNS, because that is the only place they can find the Domain ...
    (microsoft.public.windows.server.dns)