Tip: Run a free scan for common Windows errors ad

re: Do I need DNS Server? Monday, December 4, 2006 at 6:07 am Posted by Curt R (773 messages posted) You have to have DNS in order to have a Windows Active Directory domain......no if's, and's, or but's about it. It should display your username, not your full name, this is normal. Problems logging in like you describe are usually related to improperly configured DNS. Not having an IP for your DNS server would be my first guess as to the cause. As I stated, DNS is integral to an active directory domain and you have to be able to contact the DNS server for it to work properly. On Saturday, December 2, 2006 at 9:51 pm, Jude Nihal Fernando wrote: >Right Now, I have a Master Server, running Domain Controller (Active Directory), >DNS Server, Application Server and File Server. I also have a 2 Extra VMWare Virtual >Servers emulated on the Master Server, 1 runs Windows 2000 Advanced Server and that >is a Exchange Server and a VPN Server, Another one runs Windows Server 2003 and is >a Terminal Server. Now, must I seperate my DNS server from my Active Directory server? >Do I need a DNS Server at all since I have No-IP? The reason I am asking this is >because, when I log into my user, it sometimes takes forever to log in or it logs >me in and then after being on my user long, it freezes my taskbar for a while and >then when I click start, displays my UserID instead of my Full Name. How Do I fix >this problem? [Reply or follow-up to this message] re: Do I need DNS Server? Monday, December 4, 2006 at 11:46 am Posted by Jude Nihal Fernando (113 messages posted) Okay, just to clear things up, I log into the Domain with my username being NIHAL. When I log in, then when I click start in Windows XP, it displays my full name on the top of the blue start menu, which is my full name, Nihal Fernando. Then after some time when I click on the start button, it freezes up the system for a little while and when I click on the start bar, it displays NIHAL instead of Nihal Fernando and then when I log off and then log on again, it takes forever to log in for some odd reason until I restart the computer. I have looked into the event viewer to see the problem and this is what it gave me: Automatic certificate enrollment for local system failed to contact the active directory (0x8007054b). The specified domain either does not exist or could not be contacted. Enrollment will not be performed. Now, is there something wrong with my server that is doing this constantly? Must I reinstall DNS on my server or Active Directory on my server or will it make a mess all over again? Must I create a Static IP on my client to prevent this from happening? This is the only client that has this issue. All the other clients seem to run fine, but the server has DNS errors eversince I have uninstalled Exchange Server, so Exchange Server is still Installed On it, but I don't use it because I have it on another machine. Also I have put a static ip on my server and have set the preferred dns server on my router to the server and I know that if the server doesn't have a static ip and if the prefered dns server is not set to the server, it will take a long time to log in, but I did set it up and it logs in fast sometimes and sometimes takes 1-2 minuites. How do I fix this problem as well? On Monday, December 4, 2006 at 6:07 am, Curt R wrote: > You have to have DNS in order to have a Windows Active Directory domain......no >if's, and's, or but's about it. It should display your username, not your full name, >this is normal. Problems logging in like you describe are usually related to improperly >configured DNS. Not having an IP for your DNS server would be my first guess as >to the cause. As I stated, DNS is integral to an active directory domain and you >have to be able to contact the DNS server for it to work properly. > > > [Reply or follow-up to this message] re: Do I need DNS Server? Tuesday, December 5, 2006 at 6:05 am Posted by Curt R (773 messages posted) The specified domain either does not exist or could not be contacted. Enrollment will not be performed. Now, is there something wrong with my server that is doing this constantly? This usually points at a DNS problem. I would check the TCP/IP information on the client and ensure it's DNS address is your DNS server's IP. See the following web page for more information. I'm not at all sure what's up with the username vs full name but some searching of microsoft's knowledge base will likely help you find and answer. I wouldn't do any removal/reinstalling of anything without checking microsoft's knowledge base and google first in an attempt to troubleshoot the problem. On Monday, December 4, 2006 at 11:46 am, Jude Nihal Fernando wrote: >Okay, just to clear things up, I log into the Domain with my username being NIHAL. >When I log in, then when I click start in Windows XP, it displays my full name on >the top of the blue start menu, which is my full name, Nihal Fernando. Then after >some time when I click on the start button, it freezes up the system for a little >while and when I click on the start bar, it displays NIHAL instead of Nihal Fernando >and then when I log off and then log on again, it takes forever to log in for some >odd reason until I restart the computer. I have looked into the event viewer to see >the problem and this is what it gave me: > >Automatic certificate enrollment for local system failed to contact the active directory >(0x8007054b). The specified domain either does not exist or could not be contacted. > Enrollment will not be performed. > >Now, is there something wrong with my server that is doing this constantly? Must >I reinstall DNS on my server or Active Directory on my server or will it make a mess >all over again? Must I create a Static IP on my client to prevent this from happening? >This is the only client that has this issue. All the other clients seem to run fine, >but the server has DNS errors eversince I have uninstalled Exchange Server, so Exchange >Server is still Installed On it, but I don't use it because I have it on another >machine. > >Also I have put a static ip on my server and have set the preferred dns server on >my router to the server and I know that if the server doesn't have a static ip and >if the prefered dns server is not set to the server, it will take a long time to >log in, but I did set it up and it logs in fast sometimes and sometimes takes 1-2 >minuites. How do I fix this problem as well? > > > [Reply or follow-up to this message] Tip: Use one of the [Reply or follow-up to this message] links above to add a message to this thread Search this forum Start a new thread on a different subject Report abuse of the forum Return to the Windows Server 2003 Discussion Forum