Windows server 2003 Domain issue

December 2, 2012 at 21:54:10
Specs: Windows 7, 2.5/6

Hi,

My windows 2003 Server based Domain controller taking too mush time to loged in.How can i rectify this issue.

Secondly, their are more than 200 users are joined with that Domain, is this could be the issue??how can i do a health check??


Regards
kaleem


See More: Windows server 2003 Domain issue

Report •


#1
December 3, 2012 at 08:53:28

usual reason for long logon times is workstation dns settings.

are the workstations pointed to the sbs for dns or the internet?
what are the servers specs?
have you reviewed the event viewer logs?

Answers are only as good as the information you provide.
How to properly post a question:
Sorry no tech support via PM's


Report •

#2
December 3, 2012 at 20:18:23

How many GPO's are being applied? What kind of profiles are you using?

Tony


Report •

#3
December 4, 2012 at 05:23:51

Thnaks for your replies.

@wenderer: Yes clients are pointed to Domain Contrller for DNS. This is IBM x3650 intel Xeon based Server. what to see in LOGs?? and under which category??Application?Security??information??

@Tony: Never applied any type of GPO. Why u are asking about profile. From worksations all the user can loged in to Domain, but when i reboot or Remote Desktop the DC, it takes too much time, and am not able to install any antivirus on it.


Report •

Related Solutions

#4
December 4, 2012 at 14:25:18

do a nslookup yourdomainname from a workstation and post the results for review

Answers are only as good as the information you provide.
How to properly post a question:
Sorry no tech support via PM's


Report •

#5
December 4, 2012 at 16:50:38

I've experienced something similar in Windows Server 2008 R2 if you disable IPv6 on your NIC. I doubt that's the case here but it's something to check.

Post the output of ipconfig /all from your client machine and your DC. If you aren't using any GPO's, what about logon scripts? You may also want to post a dcdiag.

Tony


Report •

#6
December 5, 2012 at 00:36:51

@wanderer:

C:\>nslookup
Default Server: neurodc.nsh.com
Address: 192.168.1.10

> nsh.com
Server: neurodc.nsh.com
Address: 192.168.1.10

Name: nsh.com
Addresses: 192.168.1.4
192.168.1.16
192.168.1.2
192.168.1.10


Report •

#7
December 5, 2012 at 15:02:34

You've checked to ensure DNS forwarding is correctly configured and also checked to ensure your provider hasn't changed anything with regard to it's DNS server(s)?

It matters not how straight the gate,
How charged with punishments the scroll,
I am the master of my fate;
I am the captain of my soul.

***William Henley***


Report •

#8
December 5, 2012 at 16:54:44

I don't see how external DNS would affect logging onto a local server.

We have yet to see his TCP/IP settings. Can you post an ipconfig /all?

Tony


Report •

#9
December 6, 2012 at 09:46:20

That would be a ipconfig /all from both a workstation and the Domain Controllers.

Also what is your topology? How many switches connect to how many switches which connect to the servers?

Answers are only as good as the information you provide.
How to properly post a question:
Sorry no tech support via PM's


Report •


Ask Question