CiP

Hello everyone, I am having major problems with DNS and Active Directory on my client PCs with XP Pro and my server Windows Server 2003. This is getting so aggravating. I feel I am getting close to the solution, but as of yet, I still get Userenv and Autoenrollment errors in my Event Viewer. I have to shut down Windows Time in services due to W32Time errors. Here is my network set up: 1 Linksys Router running as a Gateway and using my cable company as my internet provider. DHCP disabled. IP scheme is the same I am using on my domain. 1 Windows Server 2003 set up as a domain with the domain name as Example: (mycompany.local). When I set it up originally, I only used ex. mycompany and the .local was added for DNS purposes I assume. I use a static IP of 192.168.1.100 with the sub-net mask 255.255.255.0. My default gateway is 192.168.1.1 same as the Default Gateway of my Linksys router. And the DNS's are what my ISP provides. There are 2. Should I be putting another DNS here???? It seems like my domain does not like my IPS's DNS's. 6 PC's running XP Pro on static IP addresses connecting to the domain server. I use the same DNS's as on the server and router. Default Gateway is the 192.168.1.1. I have internet access on all PC's no problem. For some reason, I get the Userenv and Autoenrollment errors in my Event Viewer when logging in to the server domain. I also get NETLOGON errors. It also takes a quite long time to log into the server. When I log in from a client PC into its local domain (same name as the PC, not the domain) I log on in 3 seconds, yet I still have access to the server domain and files. Actually the PC's run better connecting this way. I want each PC to log into the domain though, but these problems are getting ridiculous! Can anyone please help? If you need more info on my configuration, please ask. Thanks in advance for anyone who can help me. Cip :/

When logging into the domain (Windows Server 2003) from a workstation (Windows XP Professional), I get long login times. Much longer than the previous Windows 2000 Server. It goes through the personal settings, Network settings, etc. and hangs for about 1-2 minutes before finally logging in. When I have a wokstation log in locally and not on the domain, it logs in instantly. Yet, I still can access all the same files on the server after I enter the network password (one time only). Does anyone have this problem and know how to speed up the process? I know that Windows Server 2003 has a lot of security features added, but this log in time is much too long to be normal. Thanks.

Again, thanks rion for all your help. I will try it out.

Hi Rion, Ok thanks, I am going to try that. Before I do though, is there any other way besides going into the registry to do it? Thank again!

Using: Windows Server 2003 and XP Pro clients Hello, Does anyone have the problem of shared drives losing their connection and having the Login / Password come up? This is happening after being logged on for a while. I keep my PC's on overnight and when I come in in the morning, the connection is usually lost. Usually not to the server, but to other PC clients. I am using a Linksys router running as a Gateway, not a router. My network is on Static IP addresses, not DHCP. Also I am not running DHCP on the router. Thanks!

Here I am with one of my babies.

Thanks everyone! That helped me out too! I was a little sceptical at first, but now I will install it.