Login times to my 2003 Server are very slow

May 3, 2011 at 08:41:56
Specs: Windows Svr 03/R2, Quad/Xeon
Hello again everyone. =)

For the last week or so, login times to our 2003 R2 server are far too slow. This just started happening, and before, you could log in instantly. Both console logins and RDC logins are the same. I'm not very good with DNS, and all of the articles I've read after searching seem to blame DNS for these sorts of issues.

All workstations are pointed to the server for DNS. The server's TCP/IP properties show DNS is pointed at itself.

In the DNS panel, under Forward Lookup Zones, it shows 2 zones -- _msdcs.classic.local and classic.local

Our domain is named CLASSIC. Under the classic.local zone, I have all workstations listed as well as _msdcs, _sites, _tcp, _udp, DomainDnsZones, and ForestDnsZones.

Looks like:
_msdcs
_sites
_tcp
_udp
DomainDnsZones
ForestDnsZones
--- Start of Authority (SOA) --- (1108), server.classic.local., hostmaster.
--- Name Server (NS) --- server.classic.local
--- Host (A) --- 10.0.1.2 (Which is what all workstations are pointed to)
--- Host (A) --- 169.254.218.138 (No idea what this IP is)
--- Computer1 -- 10.0.1.xx
--- Computer2 -- 10.0.1.xx
--- and so on for each workstation

Any ideas on what is going on here? Should the classic.local zone be above the _msdcs.classic.local zone??

Any help is appreaciated. I can post more info if needed!

Thanks guys!


See More: Login times to my 2003 Server are very slow

Report •

#1
May 3, 2011 at 10:25:53
the 169x ip is a auto assigned which means some device did not get a ip address from the local dhcp server [or someone assigned this ip to the device] and had "register this with dns" check in tcp/ip properties.

Lets see a ipconfig /all from the server as well as a workstation.

Have you review the event viewer logs?\
When was the last time you ran;
chkdsk /f
disk cleanup
disk defragmenter ?

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
May 6, 2011 at 11:01:06
Here is the ipconfig results from the server and my workstation. I run a defrag, chkdsk /f and cleanup a couple of times a month on the server and workstations. As for the event logs, they show no entries during times when I've tried to login to the server via RDC or the console. In fact, no DNS entries exist for today at all.

Server IPCONFIG:


C:\Documents and Settings\Administrator>ipconfig /all

Windows IP Configuration

Host Name . . . . . . . . . . . . : Server
Primary Dns Suffix . . . . . . . : classic.local
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : classic.local

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Broadcom BCM5708C NetXtreme II GigE (NDIS
VBD Client)
Physical Address. . . . . . . . . : 00-19-B9-CD-2A-AF
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 10.0.1.2
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 10.0.1.1
DNS Servers . . . . . . . . . . . : 10.0.1.2

Workstation IPCONFIG:


C:\Documents and Settings\Corey>ipconfig /all

Windows IP Configuration

Host Name . . . . . . . . . . . . : it-tech
Primary Dns Suffix . . . . . . . : classic.local
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : classic.local

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Broadcom NetLink (TM) Gigabit Ethern
et
Physical Address. . . . . . . . . : BC-30-5B-C4-FE-21
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 10.0.1.8
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 10.0.1.1
DNS Servers . . . . . . . . . . . : 10.0.1.2

C:\Documents and Settings\Corey>


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

the 169x ip is a auto assigned which means some device did not get a ip address from the local dhcp server [or someone assigned this ip to the device] and had "register this with dns" check in tcp/ip properties.

Lets see a ipconfig /all from the server as well as a workstation.

Have you review the event viewer logs?\
When was the last time you ran;
chkdsk /f
disk cleanup
disk defragmenter ?


Report •

#3
May 6, 2011 at 11:08:03
ipconfigs look good.

please do a nslookup server from the workstation and post the results.

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


Report •

Related Solutions

#4
May 6, 2011 at 11:15:44
Hmmmmmmmmmmmmmmm.... nslookup doesn't look right?

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\Corey>nslookup server
*** Can't find server name for address 10.0.1.2: Non-existent domain
*** Default servers are not available
Server: UnKnown
Address: 10.0.1.2

Name: server.classic.local
Address: 10.0.1.2


C:\Documents and Settings\Corey>


Report •

#5
May 9, 2011 at 12:14:31
I took a look at my DNS config again and under reverse lookup zones, I have 3 zones listed. They are as follows:

0.in-addr.arpa - std primary - running
127.in-addr.arpa - std primary - running
255.in-addr.arpa - std primary - running

All 3 zone have a NS record pointed to server.classic.local and a SOA record pointed to [1], server.classic.loca, hostmaster

The only exception is that the 127.in-addr.arpa entry has a folder named 0 under the NS and SOA records. Inside of that folder is another folder named 0. Inside of the 2nd 0 folder, there is a PTR record pointed at localhost and named 1.

Does this seem right? Our setup is using the 10.0.1.x numbering.

There is a screenshot of my DNS config below, if that helps. Anyone have an idea on this?

http://i1192.photobucket.com/albums...


Report •

#6
May 9, 2011 at 12:53:20
Lets see a pic of the top of this page where the NS entries are listed.

It does appear that dns was installed with a root zone which is incorrect. But lets see the pic before doing anything.

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


Report •

#7
May 9, 2011 at 13:13:07
Is this what you're looking for?

http://i1192.photobucket.com/albums...


Report •

#8
May 9, 2011 at 13:43:26
yes and no.

I was hoping to see NS records with the server's name associated with it.

You need to remove the root zone for starts
http://support.microsoft.com/kb/323380

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


Report •

#9
May 9, 2011 at 15:21:25
The delete option is greyed out when I try to delete the root zone in Cached Lookups. Where do I find the NS information you are looking for? I don't see that anywhere.

Report •

#10
May 9, 2011 at 16:25:31
Did you review this section in the article?

This root zone indicates to your DNS server that it is a root Internet server. Therefore, your DNS server does not use forwarders or root hints in the name-resolution process.

Click Start, point to Administrative Tools, and then click DNS.
Expand ServerName, where ServerName is the name of the server, click Properties and then expand Forward Lookup Zones.
Right-click the "." zone, and then click Delete.

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


Report •

#11
May 9, 2011 at 17:02:23
Yes sir, I read it. Something still isn't jiving though. All i have is .(root) listed under Cached Lookups, it is not listed under Forward Lookup Zones. The article says to open the DNS snap-in, then expand the server and click properties. If I click properties, the server properties dialogue box opens. There are tabs, not branches there. I clicked the Forwarders tab - nothing there to delete. If I right click on .(Root), delete is not an option.

http://i1192.photobucket.com/albums...

That shows the properties box open.


Report •

#12
May 9, 2011 at 17:12:51

Report •

#13
May 10, 2011 at 14:26:54
What is under classic.local looks correct except that NS record doesn't belong under _msdcs but under classic.local in the right pane along with SOA and all the Host A records.

I have no idea what is up with the _msdcs.classic.local which looks like an additional forward lookup zone
It looks like what should be under _msdcs got moved to _msdcs.classic.local

I have the following:

Forward Lookup Zone
domainname.net
_msdcs
_sites
_tcp
_udp
DomainDNSzones
ForestDNSzones

Any idea how we got to this state?

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


Report •

#14
May 11, 2011 at 13:57:45
No idea whatsoever. I just took over as the IT Manager here, and I've never had anythying DNS related stump me. Typically, I would have set it up myself, but this one is a little odd. Check these screenshots out and let me know what you think. I'm wondering if I should just delete the _msdcs.classic.local zone alltogether and just create the needed records in the classic.local zone.

http://i1192.photobucket.com/albums...

http://i1192.photobucket.com/albums...


Report •

#15
May 11, 2011 at 15:08:21
What you suggest is the course of action I would take.

Delete the _msdcs.classic.local and just just the classic.local zone.
delete any 169.x.x.x. host/ptr records you see.

Guess there is no chance contacting the former admin to get the details on this dns setup. Sure would be helpful to know how the _msdcs.... was created. Like is this a leftover due to a domain migration?

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


Report •

#16
May 12, 2011 at 00:21:09
Hmmm, now that you mention it. I have seen remnants of an old domain here and there. I really want to say that the old server was outdated and they purchased this new one - since it did the DNS duties, maybe they just transfered everything over to a new domain...I'm sure you understand... So let me see if I can get in touch with the guy, it's a longshot - but I'd definately like to know.

Hey, I really appreciate your help on this. It's not a critical issue, but one that's been irritating the $#!^ out of me. I'm wondering if this DNS issue is to blame for a couple of other things going on around here. The more I think about it, the more I think it is.


Report •

#17
June 22, 2011 at 21:29:12
@Wanderer:

When you said:

"What you suggest is the course of action I would take.
Delete the _msdcs.classic.local and just just the classic.local zone.
delete any 169.x.x.x. host/ptr records you see."

--- I didn't quite follow. Delete the _msdcs.classic.local and ...what the classic.local zone? You said "just just" so I couldn't tell if that was supposed to be "just leave" or "just delete" =) Please clarify when you have a moment to post.

I've been tied up with a few other projects, but I have some free time this week so I thought I'd just back on this and see if I could resolve it with a little bit more help. I was able to get in touch with the tech who originally configured the newest server which handles everything,, including DNS. I actually wanted to talk to you before I called him to see if there is anything specific you think I should ask him about the situation -- other than asking how the _msdcs... was created and if it was a leftover due to a domain migration. If there is anything else you can think of, please advise. Thanks again for all of your input on this. I truly believe this is what is preventing our scanner/copier machines from working properly on the network. I would very much love to resolve the issue since my employer has been having it for well over a year now. I started only 3 months ago, so it would definitely make them happy.

If I get a raise or a bonus out of this, I'll split it with ya. =) <grin>

-Cor


Report •

Ask Question