w2000 server with xp client issue

Dna_boy · 02-21-2008, 06:49 AM

For the last few days I have been having trouble login into Windows. When I turn the computer on, all seems fine. Windows comes up nice and fast, right up to the login screen.
From then, once I chose my own account, it takes about 10min to log in.

The odd is, that happens in several xp clients when loggin in to 2000server. I installed comodo free firewall a couple weeks ago, but they worked fine with it until this week.
I looked into event viewer and it seems to have 2 errors:

Details
Product: Windows Operating System
ID: 15
Source: AutoEnrollment
Version: 5.2
Symbolic Name: EVENT_FAIL_BIND_TO_DS
Message: Automatic certificate enrollment for %1 failed to contact the active directory (%2). %3 Enrollment will not be performed.

-----------------------------------------------

Details
Product: Windows Operating System
ID: 1053
Source: Userenv
Version: 5.2
Symbolic Name: EVENT_FAILED_USERNAME
Message: Windows cannot determine the user or computer name. (%1). Group Policy processing aborted.

----------------------------------------------

Can you tell me why this happens and what can i do besides re-install ?

**XtabbedoutX** · 02-21-2008, 07:01 AM

Are you using roaming profiles? Does the long log in time apply to all users in the domain? Does it apply to the Domain Admin account?

Dna_boy · 02-21-2008, 09:04 AM

Quote:

Originally Posted by XtabbedoutX

Are you using roaming profiles? Does the long log in time apply to all users in the domain? Does it apply to the Domain Admin account?

Roaming files?

It applys to all it seems, but i need to verify that. In the server it's quick, as it should be, but if i try to log in with admin account elsewhere, same thing.

**XtabbedoutX** · 02-21-2008, 09:06 AM

Check your DNS setup. Your workstations and member servers should be
pointing only to your internal DNS servers. If you're using AD-integrated
DNS, the DCs should point to themselves, and use forwarders for external
name resolution.

Frequently asked questions about Windows 2000 DNS and Windows Server 2003
DNS
http://support.microsoft.com/default...b;en-us;291382

Also check AD and make sure the computers are listed and are not disabled.

Dna_boy · 02-22-2008, 03:14 AM

So in each computer, i change the ISP ip dns to server's ip?I had it like that when i had an internet access controler firewall. But will they be able to access internet like that? They couldn't before..

Check if they're listed where? In users and computers?

**XtabbedoutX** · 02-22-2008, 05:58 AM

All of your internal computers should point to the server for DNS. Your server should be doing the leg work for outside name resolution. Try setting up 1 client to look at the server for DNS, This will check to see if the server has all the correct settings to function as a name server.

Dna_boy · 02-22-2008, 10:45 AM

The DNS was not configured.. It is now, i'll put his ip in the clients primary dns. But the thing is, it didn't had this problem before.

**XtabbedoutX** · 02-22-2008, 11:42 AM

Some things work even if they are configured improperly. And then one day you do an update or something and it magically breaks.

Dna_boy · 02-25-2008, 08:11 AM

Update, problem apparently solved, With this : net time /setsntp:Server

But i will keep an eye on it.

**XtabbedoutX** · 02-25-2008, 08:19 AM

Let us know after you monitor it for a few days.

02-21-2008, 06:49 AM	#1 (permalink)
Dna_boy Registered User Join Date: Feb 2008 Posts: 5 OS: win2000 server	w2000 server with xp client issue For the last few days I have been having trouble login into Windows. When I turn the computer on, all seems fine. Windows comes up nice and fast, right up to the login screen. From then, once I chose my own account, it takes about 10min to log in. The odd is, that happens in several xp clients when loggin in to 2000server. I installed comodo free firewall a couple weeks ago, but they worked fine with it until this week. I looked into event viewer and it seems to have 2 errors: Details Product: Windows Operating System ID: 15 Source: AutoEnrollment Version: 5.2 Symbolic Name: EVENT_FAIL_BIND_TO_DS Message: Automatic certificate enrollment for %1 failed to contact the active directory (%2). %3 Enrollment will not be performed. ----------------------------------------------- Details Product: Windows Operating System ID: 1053 Source: Userenv Version: 5.2 Symbolic Name: EVENT_FAILED_USERNAME Message: Windows cannot determine the user or computer name. (%1). Group Policy processing aborted. ---------------------------------------------- Can you tell me why this happens and what can i do besides re-install ?

02-21-2008, 07:01 AM	#2 (permalink)
XtabbedoutX TSF Enthusiast Join Date: Sep 2007 Location: Oklahoma City Posts: 1,189 OS: Server 2K3 R2 SP 2, Server 2K SP4, XP PRO SP 3, Mac OS X 10.5, iPhone My System	Re: w2000 server with xp client issue Are you using roaming profiles? Does the long log in time apply to all users in the domain? Does it apply to the Domain Admin account?

02-21-2008, 09:06 AM	#4 (permalink)
XtabbedoutX TSF Enthusiast Join Date: Sep 2007 Location: Oklahoma City Posts: 1,189 OS: Server 2K3 R2 SP 2, Server 2K SP4, XP PRO SP 3, Mac OS X 10.5, iPhone My System	Re: w2000 server with xp client issue Check your DNS setup. Your workstations and member servers should be pointing only to your internal DNS servers. If you're using AD-integrated DNS, the DCs should point to themselves, and use forwarders for external name resolution. Frequently asked questions about Windows 2000 DNS and Windows Server 2003 DNS http://support.microsoft.com/default...b;en-us;291382 Also check AD and make sure the computers are listed and are not disabled.

02-22-2008, 03:14 AM	#5 (permalink)
Dna_boy Registered User Join Date: Feb 2008 Posts: 5 OS: win2000 server	Re: w2000 server with xp client issue So in each computer, i change the ISP ip dns to server's ip?I had it like that when i had an internet access controler firewall. But will they be able to access internet like that? They couldn't before.. Check if they're listed where? In users and computers?

02-22-2008, 05:58 AM	#6 (permalink)
XtabbedoutX TSF Enthusiast Join Date: Sep 2007 Location: Oklahoma City Posts: 1,189 OS: Server 2K3 R2 SP 2, Server 2K SP4, XP PRO SP 3, Mac OS X 10.5, iPhone My System	Re: w2000 server with xp client issue All of your internal computers should point to the server for DNS. Your server should be doing the leg work for outside name resolution. Try setting up 1 client to look at the server for DNS, This will check to see if the server has all the correct settings to function as a name server.

02-22-2008, 10:45 AM	#7 (permalink)
Dna_boy Registered User Join Date: Feb 2008 Posts: 5 OS: win2000 server	Re: w2000 server with xp client issue The DNS was not configured.. It is now, i'll put his ip in the clients primary dns. But the thing is, it didn't had this problem before.

02-22-2008, 11:42 AM	#8 (permalink)
XtabbedoutX TSF Enthusiast Join Date: Sep 2007 Location: Oklahoma City Posts: 1,189 OS: Server 2K3 R2 SP 2, Server 2K SP4, XP PRO SP 3, Mac OS X 10.5, iPhone My System	Re: w2000 server with xp client issue Some things work even if they are configured improperly. And then one day you do an update or something and it magically breaks.

02-25-2008, 08:11 AM	#9 (permalink)
Dna_boy Registered User Join Date: Feb 2008 Posts: 5 OS: win2000 server	Re: w2000 server with xp client issue Update, problem apparently solved, With this : net time /setsntp:Server But i will keep an eye on it.

02-25-2008, 08:19 AM	#10 (permalink)
XtabbedoutX TSF Enthusiast Join Date: Sep 2007 Location: Oklahoma City Posts: 1,189 OS: Server 2K3 R2 SP 2, Server 2K SP4, XP PRO SP 3, Mac OS X 10.5, iPhone My System	Re: w2000 server with xp client issue Let us know after you monitor it for a few days.