Alpha said:
My mistake, sorry, I meant loading IE, also loading Webpages.
The problem could be in DNS. When you web surf, the symbolic address,
like "
www.altavista.com", has to be translated to a numeric address
like "216.155.200.155". DNS is the service that does that.
If I fire up a DOS window (command prompt window), and type
nslookup
www.altavista.com
that manually attempts a translation. The returned response should
be reasonably fast. If there is a significant delay, it means more than
one DNS server might be tested sequentially. In the experiments I've done
here, on Win2K, Windows doesn't seem to be that clever, in the sense
that, if a working DNS server is found, it is not consulted first the
next time. The search order is again used, to resolve the address.
Some other OSes I've worked with, remember which DNS server worked.
I believe there are even cases where the DNS servers are rated
according to how short their response time is. But at least here
on my computer, Win2K doesn't seem to do any of that stuff.
Your networking setup might be done a couple of ways. Many people use
DHCP (automatic setup by talking to router box). The DNS server of choice
may propagate through a couple layers of DHCP, from the ISP. Or, some people
(occasionally me as well), will assign settings manually in the network
setup. For example, when I have a computer, where DNS is extremely slow,
because bad servers are in the list of servers, I override manually and
put my own DNS server address. But that can be bad, because a good choice
on my home ISP, could be a bad choice on a work network. DHCP, in that
regard, can be a better setup option, because in theory, the DNS server
you use, will be more optimized for the current ISP choice.
Paul