Slow browsing on new Server 2003 / AD network

I recently went from NT4 to Server 2003 on a network with around 20
computers (XP Pro). FOr the most part, everything is working, but
browsing shares on the file server is annoyingly slow. From past posts,
I understand this could be a DNS thing but I'm not sure how to prove it
or to solve it.

I'd appreciate pointers on how to troubleshoot it.

Here's the IPconfig /all from the file server (which is the DC) and
from a typical client:

Server IPConfig
Windows IP Configuration

Host Name . . . . . . . . . . . . : server1
Primary Dns Suffix . . . . . . . : DI.local
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : DI.local

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) PRO/1000 MT Network
Connection
Physical Address. . . . . . . . . : 00-13-72-FE-A1-3C
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.1.15
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1
DNS Servers . . . . . . . . . . . : 127.0.0.1


XP Pro Ipconfig
Windows IP Configuration

Host Name . . . . . . . . . . . . : TOSHIBA-XP4
Primary Dns Suffix . . . . . . . : DI.local
Node Type . . . . . . . . . . . . : Peer-Peer
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : DI.local

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Realtek RTL8139/810x Family
Fast Ethernet NIC
Physical Address. . . . . . . . . : 00-A0-D1-B7-C6-66
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.1.49
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1
DHCP Server . . . . . . . . . . . : 192.168.1.1
DNS Servers . . . . . . . . . . . : 192.168.1.15
Primary WINS Server . . . . . . . : 192.168.1.15
Lease Obtained. . . . . . . . . . : Tuesday, November 21, 2006
3:30:26 PM
Lease Expires . . . . . . . . . . : Wednesday, November 21,
2007 3:30:26 PM

Yes, it is DNS issue. The DNS server should point its IP address instead of 127.0.0.1. this search result may help too.

Troubleshooting DNSCan't Find Server Name for Address 127.0.0.1 when running nslookup ... Common DNS settings mistakes Can't ping a remote computer by using FQDN ...
www.chicagotech.net/dnstroubleshooting.htm


Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on http://www.HowToNetworking.com
<(E-Mail Removed)> wrote in message news:(E-Mail Removed) oups.com...
I recently went from NT4 to Server 2003 on a network with around 20
computers (XP Pro). FOr the most part, everything is working, but
browsing shares on the file server is annoyingly slow. From past posts,
I understand this could be a DNS thing but I'm not sure how to prove it
or to solve it.

I'd appreciate pointers on how to troubleshoot it.

Here's the IPconfig /all from the file server (which is the DC) and
from a typical client:

Server IPConfig
Windows IP Configuration

Host Name . . . . . . . . . . . . : server1
Primary Dns Suffix . . . . . . . : DI.local
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : DI.local

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) PRO/1000 MT Network
Connection
Physical Address. . . . . . . . . : 00-13-72-FE-A1-3C
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.1.15
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1
DNS Servers . . . . . . . . . . . : 127.0.0.1


XP Pro Ipconfig
Windows IP Configuration

Host Name . . . . . . . . . . . . : TOSHIBA-XP4
Primary Dns Suffix . . . . . . . : DI.local
Node Type . . . . . . . . . . . . : Peer-Peer
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : DI.local

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Realtek RTL8139/810x Family
Fast Ethernet NIC
Physical Address. . . . . . . . . : 00-A0-D1-B7-C6-66
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.1.49
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1
DHCP Server . . . . . . . . . . . : 192.168.1.1
DNS Servers . . . . . . . . . . . : 192.168.1.15
Primary WINS Server . . . . . . . : 192.168.1.15
Lease Obtained. . . . . . . . . . : Tuesday, November 21, 2006
3:30:26 PM
Lease Expires . . . . . . . . . . : Wednesday, November 21,
2007 3:30:26 PM

Robert L [MVP - Networking] wrote:
> Yes, it is DNS issue. The DNS server should point its IP address instead of 127.0.0.1. this search result may help too.
>
> Troubleshooting DNSCan't Find Server Name for Address 127.0.0.1 when running nslookup ... Common DNS settings mistakes Can't ping a remote computer by using FQDN ...
> www.chicagotech.net/dnstroubleshooting.htm

I didn't see anywhere to change it in the DNS server settings, so I
changed it in the TCP/IP settings for the server's network card. I
don't see any real improvement in share browsing speed tho.

Here's the new server ipconfig:

Windows IP Configuration

Host Name . . . . . . . . . . . . : server1
Primary Dns Suffix . . . . . . . : DI.local
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : DI.local

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) PRO/1000 MT Network
Connection
Physical Address. . . . . . . . . : 00-13-72-FE-A1-3C
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.1.15
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1
DNS Servers . . . . . . . . . . . : 192.168.1.15

Any error if using nslookup? Then check this link for troubleshooting.

NslookupNslookup.exe is a tool for testing and troubleshooting DNS servers. ... If you have no DNS server configured on your client, Nslookup will. default to . ...
www.chicagotech.net/nslookup.htm


Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on http://www.HowToNetworking.com
<(E-Mail Removed)> wrote in message news:(E-Mail Removed) ups.com...
Robert L [MVP - Networking] wrote:
> Yes, it is DNS issue. The DNS server should point its IP address instead of 127.0.0.1. this search result may help too.
>
> Troubleshooting DNSCan't Find Server Name for Address 127.0.0.1 when running nslookup ... Common DNS settings mistakes Can't ping a remote computer by using FQDN ...
> www.chicagotech.net/dnstroubleshooting.htm

I didn't see anywhere to change it in the DNS server settings, so I
changed it in the TCP/IP settings for the server's network card. I
don't see any real improvement in share browsing speed tho.

Here's the new server ipconfig:

Windows IP Configuration

Host Name . . . . . . . . . . . . : server1
Primary Dns Suffix . . . . . . . : DI.local
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : DI.local

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) PRO/1000 MT Network
Connection
Physical Address. . . . . . . . . : 00-13-72-FE-A1-3C
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.1.15
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1
DNS Servers . . . . . . . . . . . : 192.168.1.15

Robert L [MVP - Networking] wrote:
> Any error if using nslookup? Then check this link for troubleshooting.

No errors in nslookup. Lookup is quick and succeeds for various web
site names.