No answer yet. That server's name appears dozens of times in the registry of
one of the standard image XP workstations, and I've installed a lot of
software in that image from a server share. I guess I need to get out a
network analyzer and see exactly what they're trying to talk to.
--
Mike
..
"Corey" wrote:
> Hey Mike,
> We're having the same problem when our main file server went down. XP
> workstations appear to continue to try to connect to the shares causing them
> to hang. We are looking for a solution where people can continue to work
> locally without being logged in to the domain OR we can set the workstations
> where they don't continually look for shares if they aren't available. Your
> problem sounds a little different in that maybe your workstations didn't have
> a mapping to Server1 at all. Did you ever find an answer to your question?
> Corey
>
> "Mike" wrote:
>
> > I support 50 Windows XP Pro SP-3 workstation PCs that are all Active
> > Directory members. My users log into AD accounts, and all their data is on
> > Server1, also an AD member. It’s not a domain controller, but it runs WSUS
> > and is the Windows Update server location for just these 50 workstations.
> > The
> > workstations are set (via group policy) to check for updates every 22 hours
> > and install daily at 8:00 AM. The following took place between 2:00 PM and
> > 3:00 PM:
> >
> > Server1 has several shares. Due to problems with an external RAID array, the
> > server was still running, but some of those shares were unavailable for a
> > while, including the share where the VB Script login script is located. In
> > fact the only shares that were still available were relatively unimportant.
> > This caused no problem other than missing drive mappings that were done in
> > the login script. The server was restarted several times during the period
> > when the shares were unavailable, and the workstations performed normally
> > when it was up and running.
> >
> > When Server1 was shut down, all the workstations started to hang for long
> > periods, even after a restarts. E.g., a 30-60 second delay from clicking on
> > the start menu till the menu was displayed. The same to open IE. They would
> > periodically “break free” and would run at normal speed for a few seconds,
> > then would hang again. During these times, Task Manager showed 99% idle and
> > almost no network activity. Technet’s Procmon.exe also showed very little
> > activity of any sort. There were no unusual entries in event logs.
> >
> > As soon as Server1 was started, the workstations started performing normally
> > again.
> >
> > It seems that the workstations want something from Server1, but I can’t
> > imagine what it is. Only a small portion of the event logs I examined had
> > any Windows Update activity, probably because the “check for update” time is
> > randomized.
> >
> > Can anyone shed any light on this?
> >
> > Thanks.
> >
> > --
> > Mike
> > .
|
Similar Threads
Linear Mode
