Two things to check first.
1st. Name Resolution. Win2k uses DNS and Win9x uses WINS. (And MACS, I
believe want to use DNS as well, although don't quote me). Unless you have
both a primary DNS and WINS setup for "Your Network" (not your ISPs DNS)
some of the machines are going to run slow as they search "Your Network" for
the info they need.
I would assume that you do not have a DNS server on "Your Network" and the
Win2k machines are querying your ISPs DNS for your local network info. But
of course your ISP has no such information.
You may want to check out HOSTS or LMHOSTS as an option.
First we have had HOSTS files all along to help with the name
resolutions. But we now have a DNS server that is caching and has
reverse lookup as well. That has certainly sped up internet surfing
for users, as well as some of the network access. But they are still
experiencing other slow access, like pulling up printers and saving
files, etc.
2nd. Is an issue with the default set of protocols. By default Win9x loads
NetBuie & SPX (which you do not need unless you have a UNIX server on "Your
Network"). While Win2k only loads TCP. Make sure all machines have the same
Protocol set.
100% Win2k clients, all only with TCP/IP loaded. We no longer have
any win9x or even NT clients. And we don't have any xp clients
either.
