Slow Win2k access to Win2003 server (Win98 -> Win 2003 is fine)

[Danny Frencham]

I'm having a problem with slow network access to a Windows
2003 server.

The network has mixed Windows 98 and 2000 clients, all
accessing files and running
apps from the Win 2003 server. The new Win2003 server is
extremely slow with win2k clients,
but fast for the Win98 clients.

The clients are opening a drawing package from the server,
and manipulating other files on the server.

Both the Win2k and 98 boxes are lightening fast with the
old NT server.

Other details:

- Neither the Win2k box or the NT server are DNS servers.
- network clients are using external ISP DNS servers
- Win2k3 box is a fileserver only
- there is no domain (to be added in the future)
- all clients have accounts on the file server

----

The Windows 2k boxes are using Service pack 3, except for
one, which is using 4 (and yes, it has the same problem).

I've forced the NIC to 100MBit full duplex on the 2003
Server.

The server has 2 HDDs running in RAID1 (mirroring) with a
Promise Raid Controller.


The speed problem is noticable when opening files in
drawing packages - Photoshop, etc. On a 2000 client it'll
kinda sit there for a few seconds, then start opening the
file (and at a slower rate than the 98 machines).

I've tried adding the server to the hosts file on one of
the machines to eliminate DNS problems, but it made no
difference.

This problem is preventing them from switching to the new
server

 

[Marina Roos]

Install DNS-server on the server.
Clients should obtain IP and DNS from your server. How many nics in the
server? DNS on the nic(s) should point to your server-IP. The
ISP-DNS-numbers should be set in the forwarders of the DNS-server.

Marina

 

[Danny Frencham]

The company is currently using external DNS servers (their
ISPs servers).

(Forgot to mention that there is a preexisting NT4 domain -
server and clients are joined to it)

The server only has one nic.

Would this make a difference?
1) Install DNS service on server (they don't have a
domain, use .local or something?)
2) set the DNS server up as a forwarder to the external
servers
3) Set the clients to point at the local DNS server, and
register themselves in the DNS.

Is there anything I've missed?

 

[Marina Roos]

DNS is very vital in a W2K-domain.
All your points are right. Put the server-IP in the DNS-field of your nic
and put the ISP-DNS-numbers in the forwarders of your DNS-server.
Let the clients obtain an IP automatically from your DHCP-server and also
obtain the DNS automatically.

Marina