Slow browsing and file opening/saving

[Guest]

I've just replaced a number of old Win 95 pcs at a client's with Windows XP
Pro. However, these new machines are extremely slow at browsing the local
subnet and opening/saving any files to the local server.

The client still has some Windows 98 pcs which do not have any problem.

All machines are running the same client applications - only the operating
system differs.

All machines have point to external DNS servers to allow them to browse the
internet. NetBIOS over IP is enabled for all pcs and LMHOSTS file is enabled.
There is a WINS server in the main office.

I cannot see what might be causing the XP machines to browse in such a slow
manner. Any ideas?

Cheers

 

[Malke]

I've just replaced a number of old Win 95 pcs at a client's with
Windows XP Pro. However, these new machines are extremely slow at
browsing the local subnet and opening/saving any files to the local
server.

The client still has some Windows 98 pcs which do not have any
problem.

All machines are running the same client applications - only the
operating system differs.

All machines have point to external DNS servers to allow them to
browse the internet. NetBIOS over IP is enabled for all pcs and
LMHOSTS file is enabled. There is a WINS server in the main office.

I cannot see what might be causing the XP machines to browse in such a
slow manner. Any ideas?

You don't mention what operating system the server is running, but your
DNS is set up incorrectly on the XP machines. They should only be
looking to the server for DNS, not to any external sources. Here is
information on that from MVP Ron Lowe. The instructions reference a
server running Win2k server but are applicable to Win2003 server also:

XP differs from previous versions of windows in that it uses DNS as it's
primary name resolution method for finding domain controllers:

If DNS is misconfigured, XP will spend a lot of time waiting for it to
timeout before it tries using legacy NT4 sytle NetBIOS. ( Which may or
may not work. )

1) Ensure that the XP clients are all configured to point to the local
DNS server which hosts the AD domain. That will probably be the Win2k
server itself. They should NOT be pointing to an ISP's DNS server. An
'ipconfig /all' on the XP box should reveal ONLY the domain's DNS
server. You should use the DHCP server to push out the local DNS server
address.

2) Ensure DNS server on Win2k is configured to permit dynamic updates.

3) Ensure the Win2k server points to itself as a DNS server.

4) For external ( internet ) name resolution, specify your ISP's DNS
server not on the clients, but in the 'forwarders' tab of the local
Win2k DNS server.
not on the clients, but in the 'forwarders' tab of the local win2k
DNS

On the DNS server, if you cannot access the 'Forwarders' and 'Root
Hints' tabs because they are greyed out, that is because there is a
root zone (".") present on the DNS server. You MUST delete this root
zone to permit the server to forward unresolved queries to yout ISP or
the root servers. Accept any nags etc, and let it delete any
corresponding reverse lookup zones if it asks.

How Domain Controllers Are Located in Windows XP -
http://support.microsoft.com/default.aspx?scid=kb;en-us;314861
Setting Up the Domain Name System for Active Directory -
http://support.microsoft.com/default.aspx?scid=kb;en-us;237675
HOW TO: Configure DNS for Internet Access in Windows 2000 -
http://support.microsoft.com/default.aspx?scid=kb;en-us;300202
DNS and AD FAQs - http://support.microsoft.com/?id=291382

Malke

 

[Guest]

Sorry Malke, I forgot to mention the server.

The firm's server is running MS SBS 4.5 and is located in the main office
where apporximately 25 users access it. It is not running NT4's version of
DNS. The firm has two remote offices of 3/4 users each. The remote offices do
not have dedicated servers.

The XP machines in the main office are configured as members of the NT4
domain. The XP machines in the remote office are configured as workgroup
machines and not members of any domain.

All three sites are linked via a VPN through which the remote offices access
the Exchange Server facilities on the main office server.

It is unlikely that the server will be upgraded with Win 2003 Server anytime
soon. Nor will the remote offices be getting their own dedicated server.

There is no need for the remote offices to browse the network other than
their own local subnet. Drive mapping, using the 'net use' command works
perfectly well for all machines on each subnet. However, even accessing those
drives, the XP machines are slow.

Is it not possible to force XP machines to use either WINS, LMHOSTS or
NetBIOS name resolutions first, or in some way, turn off DNS for name
resolutions other than that required for Internet browsing?

Cheers

 

[Malke]

Sorry Malke, I forgot to mention the server.

The firm's server is running MS SBS 4.5 and is located in the main
office where apporximately 25 users access it. It is not running NT4's
version of DNS. The firm has two remote offices of 3/4 users each. The
remote offices do not have dedicated servers.

The XP machines in the main office are configured as members of the
NT4 domain. The XP machines in the remote office are configured as
workgroup machines and not members of any domain.

All three sites are linked via a VPN through which the remote offices
access the Exchange Server facilities on the main office server.

It is unlikely that the server will be upgraded with Win 2003 Server
anytime soon. Nor will the remote offices be getting their own
dedicated server.

There is no need for the remote offices to browse the network other
than their own local subnet. Drive mapping, using the 'net use'
command works perfectly well for all machines on each subnet. However,
even accessing those drives, the XP machines are slow.

Is it not possible to force XP machines to use either WINS, LMHOSTS or
NetBIOS name resolutions first, or in some way, turn off DNS for name
resolutions other than that required for Internet browsing?

Unfortunately (for me), I don't have much experience with NT4. If you
don't get an answer from someone else in this group, try posting here:
microsoft.public.windows.server.general

The regulars are sysadmins and network gurus. Otherwise, with such a big
network I'm sure you have a support contract with MS. I'd give server
tech support a call. Yes, this will cost (last time I called it was
$245 usd), but my experience with them was excellent and I felt it was
totally worth the business expense since it quickly solved my problem.

Good luck,

Malke