HORRIBLY slow network

  • Thread starter Thread starter IBC
  • Start date Start date
I

IBC

Am I the only one whose thrown an XP Box on a 2000 Network and had it turn
into a 286? What's the deal?

Windows XP Pro with SP1, Office 2000, all the Windows update Critical Update
stuff and anything available for download without having to call Microsoft.
(more on that later) I have 6 of these boxes to deploy, and If I have to
stand on my head with each one, they may go straight to the dumpster
instead. Why on earth is an XP Pro box not plug -n- go 2 years after XP is
released?

<rant>And why on earth do I have to call Microsoft asking for a patch? If
there is a patch out there for a known issue, why on earth do I have to
waste time on a phone begging for hot fixes?
</rant>

Can somebody please point me to how they fixed this problem on their
network?

Thank you.
 
More Info is needed to pinpoint your problem
1. Do you have a dns server on your network and if so are
zones configured?
Are you using static ips or DHCP
I have found that for an xp box to function on a network
it needs a properly configured DNS server authrotative for
your lan. If you are using internet DNS servers you will
be in slow motion.
 
1. I honestly have no idea. We have been running SBS2000 for 3 years with
W2K clients and never had a hiccup. So if its there or if the zones are
configured is a good question. I'd be happy to look if somebody can tell me
where.

2. DHCP. I prefered using static for such a small LAN (under 30 machines)
but the consultant insisted 3 years ago we go DHCP.

Thanks for taking the time!
 
OK, I did look under Administrative Tools and in DNS. It lists our server
and all the machine names/IPs. What in particular makes it properly
configured?
 
Hello,

I had the same problem, and found this solution today
that fixed it, hope it helps you

This could be due to a known issue with webclient, fixed
in XP Service Pack
1.
Assuming you don't use "Web Distributed Authoring and
Versioning (WebDAV)",
here's a possible workaround:

Type the following command to determine whether webclient
is running:
sc queryex webclient
If the STATE shows RUNNING, then run the following
command to disable it:
sc config webclient start= disabled
The initial slowness in accessing file shares should not
occur on the next
boot. To avoid a
reboot, you could run the following command:
sc stop webclient
 
Back
Top