I could be mistaking, but have you checked your DNS setings for the
computers with the issues? The DNS server should be your domain
controller's IP address. Active Directory and DNS are very
intertwined technologies. If a computer is booting up and cannot use
DNS to get it's AD information, it takes a long time to accomplish the
logon process.
Re: Home to Pro upgrade issues with AD domain ... >> computers that when purchased were running XP home. ... >This usually indicates a DNS misconfiguration problem.... > They should NOT be pointing an an ISP's DNS server.... and 'Root Hints'... (microsoft.public.windowsxp.network_web)
Re: Getting Terminal Services to work ... In an AD domain all of the workstations need to be using an AD DNS server and no other DNS servers. ... This will allow XP to sort of work with Active Directory but Vista will fail miserably. ... All the computers are on a workgroup "Fred". ... (microsoft.public.windows.vista.networking_sharing)
Re: AD, DHCP or maybe DNS problem? ... gateway machine can you get to the internet?... Does dns on the clients point ... Does the AD DNS server forward DNS requests it ... I have a 2003 Server Running as DHCP and DNS, I have 3 cleint computers.... (microsoft.public.windows.server.active_directory)
RE: DNS and 2k3 to 2k3 migration ... "The problems that I see so far DHCP server on old domain as most users are ... I manually fix this by setting my DNS to new domain This would cause ... the DNS Server IP address obtained from DHCP Server is pointed to ... you couldn't initial VPN connection from computers... (microsoft.public.windows.server.migration)
Re: No DC in Active Directory ... I still show no computers or DCs in AD Computers and Users on Srvr1 and they ... The primary DC points to itself as the DNS.... The second server... the first server now shows no DCs in the Active Directory... (microsoft.public.windows.server.active_directory)
