Slow performance when opening file or right clicking desktop

  • Thread starter Thread starter Richard Roati
  • Start date Start date
R

Richard Roati

We have a Windows 2000 domain with Windows 2003 and Windows 2000 Servers, and
Windows XP SP2 clients. On more than ten XP clients, it takes 15 seconds for
a file to load when double clicking on it. It takes the same amount of time
when right clicking on the desktop or right clicking on a file. If we
disable netBios, the same actions are instantaneous. If we bring the same
computer to a different subnet, it still has the issue. There are many XP
computers that do not have this issue. We have been unable to determine the
cause of the slowness. Unfortunately, we have a few applications that still
rely on browsing/netBios. Thanks very much for helping us!
 
Richard Roati said:
We have a Windows 2000 domain with Windows 2003 and Windows 2000 Servers,
and
Windows XP SP2 clients. On more than ten XP clients, it takes 15 seconds
for
a file to load when double clicking on it. It takes the same amount of
time
when right clicking on the desktop or right clicking on a file. If we
disable netBios, the same actions are instantaneous. If we bring the same
computer to a different subnet, it still has the issue. There are many XP
computers that do not have this issue. We have been unable to determine
the
cause of the slowness. Unfortunately, we have a few applications that
still
rely on browsing/netBios. Thanks very much for helping us!
Click to expand...


This appears it may be due to a DNS configuration on the clients. If you
have an external DNS (your ISP's, the router or some other outside DNS)
address in a client's IP configuration (or set in DHCP Option 006), what you
are seeing will happen.

To better help, please post an ipconfig /all from your DC and a sample
client machine. We can evaluate the configs and make recommendations if
needed.

FYI, other issues that will cause this:

Multihomed DC (more than two NICs and/or IP addresses).
RRAS installed on a DC (such as for VPNs, etc).
AD DNS Domain name is a single label name ("domain" vs the minimal of
"domain.something").

Also, if there are any errors in the event logs, please post them as well.
Post the eventID# and Source name, please.


--
Ace

This posting is provided "AS-IS" with no warranties or guarantees and
confers no rights.

Please reply back to the newsgroup or forum for collaboration benefit among
responding engineers, and to help others benefit from your resolution.

Ace Fekay, MCT, MCTS Exchange, MCSE, MCSA 2003 & 2000, MCSA Messaging
Microsoft Certified Trainer

For urgent issues, please contact Microsoft PSS directly. Please check
http://support.microsoft.com for regional support phone numbers.
 
Hi Mr. Fekay,
Thank you for your posting, and sorry for the delay in my reply. In answer
to your first question, I don't believe this issue is due to handing out
external DNS to our clients, as we only hand out internal DNS to our clients,
and our servers are setup the same way. Nor do we have RRAS setup on our
servers, nor is our DNS name a single name. However, we do have multihomed
servers.

Here is the ipconfig /all from a typical client:

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
U:\>ipconfig /all
Windows IP Configuration
Host Name . . . . . . . . . . . . : prov-wrk-122
Primary Dns Suffix . . . . . . . : Corporate.Providence.com
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : Corporate.Providence.com
corporate.providence.com
Providence.com
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . : corporate.providence.com
Description . . . . . . . . . . . : Intel(R) 82566DM-2 Gigabit
Network C
onnection
Physical Address. . . . . . . . . : 00-1A-A0-DB-C2-EB
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 10.12.2.108
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 10.12.2.1
DHCP Server . . . . . . . . . . . : 10.12.10.1
DNS Servers . . . . . . . . . . . : 192.168.1.1
192.168.1.7
Primary WINS Server . . . . . . . : 192.168.1.72
Secondary WINS Server . . . . . . : 192.168.1.1
Lease Obtained. . . . . . . . . . : Tuesday, September 22, 2009
3:02:02
PM
Lease Expires . . . . . . . . . . : Wednesday, September 23, 2009
3:02:0
2 PM
U:\>

Here is the ipconfig /all from the PDC Emulator:

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

Windows IP Configuration

Host Name . . . . . . . . . . . . : prov-dc-01
Primary Dns Suffix . . . . . . . : Corporate.Providence.com
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : Corporate.Providence.com

Ethernet adapter WEBAPPS - Intel PRO1000MT:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) PRO/1000 MT Network Connection
Physical Address. . . . . . . . . : 00-14-22-13-5B-B9
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.1.23
Subnet Mask . . . . . . . . . . . : 255.255.255.0
IP Address. . . . . . . . . . . . : 192.168.1.99
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :

Ethernet adapter LAN - Intel PRO1000MT #2:

Connection-specific DNS Suffix . : corporate.providence.com
Description . . . . . . . . . . . : Intel(R) PRO/1000 MT Network
Connection #
2
Physical Address. . . . . . . . . : 00-14-22-13-5B-B8
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.1.1
Subnet Mask . . . . . . . . . . . : 255.255.255.0
IP Address. . . . . . . . . . . . : 192.168.1.72
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.251
DNS Servers . . . . . . . . . . . : 192.168.1.72
192.168.1.7
Primary WINS Server . . . . . . . : 192.168.1.72

Also,

C:\Documents and Settings\jpochily>nslookup
Default Server: prov-dc-01.corporate.providence.com
Address: 192.168.1.72
prov-dc-01
Click to expand...
Server: prov-dc-01.corporate.providence.com
Address: 192.168.1.72

Name: prov-dc-01.Corporate.Providence.com
Addresses: 192.168.1.72, 192.168.1.1

Thanks again for your help!
 
Richard Roati said:
Hi Mr. Fekay,
Thank you for your posting, and sorry for the delay in my reply. In
answer
to your first question, I don't believe this issue is due to handing out
external DNS to our clients, as we only hand out internal DNS to our
clients,
and our servers are setup the same way. Nor do we have RRAS setup on our
servers, nor is our DNS name a single name. However, we do have
multihomed
servers.

Here is the ipconfig /all from a typical client:

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
U:\>ipconfig /all
Windows IP Configuration
Host Name . . . . . . . . . . . . : prov-wrk-122
Primary Dns Suffix . . . . . . . : Corporate.Providence.com
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : Corporate.Providence.com
corporate.providence.com
Providence.com
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . : corporate.providence.com
Description . . . . . . . . . . . : Intel(R) 82566DM-2 Gigabit
Network C
onnection
Physical Address. . . . . . . . . : 00-1A-A0-DB-C2-EB
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 10.12.2.108
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 10.12.2.1
DHCP Server . . . . . . . . . . . : 10.12.10.1
DNS Servers . . . . . . . . . . . : 192.168.1.1
192.168.1.7
Primary WINS Server . . . . . . . : 192.168.1.72
Secondary WINS Server . . . . . . : 192.168.1.1
Lease Obtained. . . . . . . . . . : Tuesday, September 22, 2009
3:02:02
PM
Lease Expires . . . . . . . . . . : Wednesday, September 23, 2009
3:02:0
2 PM
U:\>

Here is the ipconfig /all from the PDC Emulator:

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

Windows IP Configuration

Host Name . . . . . . . . . . . . : prov-dc-01
Primary Dns Suffix . . . . . . . : Corporate.Providence.com
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : Corporate.Providence.com

Ethernet adapter WEBAPPS - Intel PRO1000MT:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) PRO/1000 MT Network
Connection
Physical Address. . . . . . . . . : 00-14-22-13-5B-B9
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.1.23
Subnet Mask . . . . . . . . . . . : 255.255.255.0
IP Address. . . . . . . . . . . . : 192.168.1.99
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :

Ethernet adapter LAN - Intel PRO1000MT #2:

Connection-specific DNS Suffix . : corporate.providence.com
Description . . . . . . . . . . . : Intel(R) PRO/1000 MT Network
Connection #
2
Physical Address. . . . . . . . . : 00-14-22-13-5B-B8
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.1.1
Subnet Mask . . . . . . . . . . . : 255.255.255.0
IP Address. . . . . . . . . . . . : 192.168.1.72
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.251
DNS Servers . . . . . . . . . . . : 192.168.1.72
192.168.1.7
Primary WINS Server . . . . . . . : 192.168.1.72

Also,

C:\Documents and Settings\jpochily>nslookup
Default Server: prov-dc-01.corporate.providence.com
Address: 192.168.1.72
prov-dc-01
Click to expand...
Server: prov-dc-01.corporate.providence.com
Address: 192.168.1.72

Name: prov-dc-01.Corporate.Providence.com
Addresses: 192.168.1.72, 192.168.1.1

Thanks again for your help!
Click to expand...

Hello Mr. Roati,

Apparently the problem is multihoming the DCs and the fact the DC has
additional IP addresses. This is extermely problematic with AD
functionality. This is due to DNS registration of the additional IPs of both
the extra IPs, and the extra NICs. When querying DNS, it may provide the
clients an IP that they cannot connect to, hence the problems you are
seeing. The nslookup result is evident of this.

I would suggest to disable one of the NICs, delete the additional IP
address, and simply use the infrastructure's routing functions to
communicate across subnets.

If you are reluctant on following my suggestions, you can also opt to alter
the domain controller's default registration and the Netlogon service's
functionality. It requires multiple steps and registry alterations. To see
how it is done, please read my blog on the steps involved, including
additional information on why the issues are occuring.

Multihomed DCs with DNS, RRAS, and/or PPPoE adapters
http://msmvps.com/blogs/acefekay/ar...-dcs-with-dns-rras-and-or-pppoe-adapters.aspx

And you are welcome for the help!

Ace
 
Back
Top