RE: Slow initial access to shares on a Win2kS domain controller from W

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance



Hi,

I have aexactly the same problem on few network configurations win win2000
server and winxp machines. I have been trying for months to get an answer but
with no luck; I was forced to scrap the xp machines and reisntall win2k pro
and everything is now fine. I long for the day that Microsoft admit this as
theri design fault and release a fix for it...For the time being I am foced
not to upgrade to WinXP and advise the same to many of my clients...

regards,

"thatcher" wrote:

> Hello all,
>
> Due to a hard disk failure and a long-running series of poor decision
> catching up to us, I had to re-install Win2k Server (standard) on our
> one and only domain controller two weeks ago. Recreation of the domain
> and rejoining of the existing client machines went pretty well and the
> first thing I did afterward was bring up another DC so I'm not in the
> same boat if it happens again.
>
> Since then, clients have been complaining about slowness when they
> first access network shares. They are not making it up, rebooting the
> affected machines and then trying to access a mapped drive will result
> in a 20 - 40 second wait for the initial directory listing to come up.
> After that, they can browse through folders with no wait. From time to
> time though, when trying to save files to those shares, they get a
> "delayed write" error.
>
> Okay, the details. The server has been completely updated per
> Windows Update. I have updated all of my NIC drivers to the newest I
> could find from the respective manufacturers' websites (HP and D-Link).
> It has three NICs in it, though one of the D-Links is disabled
> (through the network control panel, not the device control panel). It
> seems that the only client machines having difficulty are Windows XP
> machines. They few Win2k Pro and Win98 machines left seem to not have
> the same problem.
>
> The problem seems to affect some client machines more than others,
> and seems to be worse at some times of the day than others. I have
> recently updated the firmware on the switch (HP DL4000 chassis with a
> full rack of 10/100 cards) and have checked to see if the problem is
> merely over-utilization of the network - it is not.
>
> I have also searched through the microsoft newsgroups looking for
> similar problems. A number of the posts reference KB articles which I
> have gone through and not found to apply to my situation.
>
> I'd be very appreciative if anyone with a similar experience or some
> knowledge of the problem would help me out. Thanks.
>
>
.



Relevant Pages

  • Re: Vista, SBS 2003 and RAS not working
    ... We have a windows SBS 2003 server – straight out of the box, ... The VPN connection between your computer and the VPN server could not ... You mention that the clients are Vista machines, which means that their built-in firewall works on outgoing messages as well as incoming ones, and the firewall needs to be told that outgoing PPTP VPN connections should be allowed. ... Computers don't need to be joined to the domain to connect by VPN, by the way, so you can use other remote computers for testing, it's just that only domain machines get access to all network resources easily. ...
    (microsoft.public.windows.server.sbs)
  • Re: Problem getting a new XP computer to join an NT 4.0/Win 98 domain
    ... > the computers and the file server with the goal of getting ... > If you scan Network Neighborhood for the Entire Network after ... > booting, there are 3 workgroups: ... > machines to see and map to shares on the NT file server. ...
    (microsoft.public.windowsxp.network_web)
  • Re: Problem getting a new XP computer to join an NT 4.0/Win 98 domain
    ... > the computers and the file server with the goal of getting ... > If you scan Network Neighborhood for the Entire Network after ... > booting, there are 3 workgroups: ... > machines to see and map to shares on the NT file server. ...
    (microsoft.public.win2000.networking)
  • Re: Connecting from Suse to windows workgroup on
    ... > pool of IPs) and I have just installed a Suse 9.3 Enterprise Server ... > From Suse pinging 127.0.0.1 works but no other machines on the Lan. ... problem with the network card or cabling... ...
    (alt.os.linux.suse)
  • Re: XP Problem
    ... to load the exe on their machines. ... have the data point to the server. ... > Could be Dave. ... >>It may be your client machines can't find them or know where to look ...
    (microsoft.public.fox.programmer.exchange)