asked on

Extremely slow access to SBS2008 STD from WinXP clients

Recently migrated from SBS2003 to SBS2011, now WinXP clients are extremely slow when browsing mapped drives. Win7 and server 08R2 RDP server access is fine. It is extremely noticeable when adding attachments to outlook via the paperclip (2-3 minute delay). "Drag & Drop" in outlook does NOT experience this slowdown. Also noticeable when uploading items to web-based app.

I've tried:
Turning off SMB2, disabling all "advanced" network functions on NIC, applying latest service packs, clearing mapped drives out of registry, and lots of other things.

Problem affects any user profile on client pc.

R. Andrew Koffron

slow connection issues I've had in all flavors of SBS have been like 90% been related to the AD/DNS/DHCP relationship.

ensure your SBS server is the DHCP server, and the DNS servers, that DHCP is updating the DNS and the SBS server is not using forwarders unless you have a specific business need for controlling DNS requests.

cnptechnologies

ASKER

Thanks for the quick response. The new server IS the AD/DNS/DHCP for the network. the old server has been dcpromo'd and powered off. I'm fairly certain there are no forwarders in DNS but i'll give it another look to confirm.

jaredr80

DNS should be utilizing forwarders in SBS 2011. You want the NIC set as your SBS server for DNS, not an outside DNS. I don't think forwarders would be causing issues, like you are observing.

Have you run the "Fix my Network Wizard" in the SBS console? Also, how are you currently mapping the drives, by script? If so, you should look into newer options including mapping the drives via GPO. It is cleaner and usually faster. Also, I would check event viewer for possible signs. Finally, it may be worth unjoining and rejoining computer to domain.

-Jared

WORKS2011

run dcdiag /test:dns and post the results

cnptechnologies

ASKER

Tried removing/rejoining the domain and that made no difference. Also, there was an incorrect name server setting on a zone in DNS, fixed that as well but the problem remains. Ran the dcdiag and saw the old DC in there (broken delegation). Fixed that and now the dcdiags seem to be okay. But the problems persists. Also, I ran the "fix my network" wizard and allowed it to address the issues it found, but there is not change in the problem. Any ideas?

C:\Users\administrator.COMPANY>dcdiag /test:dns

Directory Server Diagnosis

Performing initial setup:
Trying to find home server...
Home Server = SERVER-SBS
* Identified AD Forest.
Done gathering initial info.

Doing initial required tests

Testing server: Default-First-Site-Name\SERVER-SBS
Starting test: Connectivity
......................... SERVER-SBS passed test Connectivity

Doing primary tests

Testing server: Default-First-Site-Name\SERVER-SBS

Starting test: DNS

DNS Tests are running and not hung. Please wait a few minutes...
......................... SERVER-SBS passed test DNS

Running partition tests on : ForestDnsZones

Running partition tests on : DomainDnsZones

Running partition tests on : Schema

Running partition tests on : Configuration

Running partition tests on : company

Running enterprise tests on : company.local
Starting test: DNS
Test results for domain controllers:

DC: SERVER-SBS.company.local
Domain: company.local

TEST: Dynamic update (Dyn)
Warning: Failed to delete the test record dcdiag-test-record i
n zone company.local

Summary of test results for DNS servers used by the above domain
controllers:

DNS server: 2001:500:1::803f:235 (h.root-servers.net.)
1 test failure on this DNS server
PTR record query for the 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.
0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa failed on the DNS server 2001:500:1::803f:235

DNS server: 2001:500:2d::d (d.root-servers.net.)
1 test failure on this DNS server
PTR record query for the 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.
0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa failed on the DNS server 2001:500:2d::d

DNS server: 2001:500:2f::f (f.root-servers.net.)
1 test failure on this DNS server
PTR record query for the 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.
0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa failed on the DNS server 2001:500:2f::f

DNS server: 2001:500:3::42 (l.root-servers.net.)
1 test failure on this DNS server
PTR record query for the 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.
0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa failed on the DNS server 2001:500:3::42

DNS server: 2001:503:ba3e::2:30 (a.root-servers.net.)
1 test failure on this DNS server
PTR record query for the 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.
0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa failed on the DNS server 2001:503:ba3e::2:30

DNS server: 2001:503:c27::2:30 (j.root-servers.net.)
1 test failure on this DNS server
PTR record query for the 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.
0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa failed on the DNS server 2001:503:c27::2:30

DNS server: 2001:7fd::1 (k.root-servers.net.)
1 test failure on this DNS server
PTR record query for the 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.
0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa failed on the DNS server 2001:7fd::1

DNS server: 2001:7fe::53 (i.root-servers.net.)
1 test failure on this DNS server
PTR record query for the 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.
0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa failed on the DNS server 2001:7fe::53

DNS server: 2001:dc3::35 (m.root-servers.net.)
1 test failure on this DNS server
PTR record query for the 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.
0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa failed on the DNS server 2001:dc3::35

SERVER-SBS PASS PASS PASS PASS WARN PASS n/a
......................... company.local passed test DNS

cnptechnologies

ASKER

Still trying things on this to no avail. Found the "sbsserver" environment variable still pointed to old server and changed this. Tried adding IPv6 to WinXP machines, removed/re-added clients/services on NIC, prayed to Mecca-Nothing is helping.

ASKER CERTIFIED SOLUTION

cnptechnologies

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

cnptechnologies

ASKER

Took months of troubleshooting and research to find this solution. it is likely to save others a lot of frustration should they encounter the same issue.