XP clients terrible performance when old server is disconnected ne

[Danny F]

I have an issue that has been driving me insane. I have 4 Windows XP Pro SP3
workstations. All the Accounting Dept PC’s. I also have an old Windows 2000
SP4 Server that I want to take offline and decommission. The problem is as
soon as I disconnect this server or shut it down. The 4 workstations slow to
a crawl. Not just on the network but performance as well. Here is the
scenario:
Workstation 1 connected to network and Server Old connected to network.
Everything works great, PC’s screaming fast.
Unplug network cable of ServerOld, workstation1 slows to a crawl.
Open command prompt and type notepad to open notepad 60 seconds before
notepad opens. (I use notepad as a test but all other commands take forever
just to initiate as well including running IE or doing anything on the
network, but apps run slow as hell to)
Plug Serverold network cable back in. Type notepad in command prompt,
instantly opens.
If I unplug ServerOld network cable again, type notepad, 60 seconds before
it opens. But if I then unplug Worksation1 network cable so it is no longer
on network, notepad comes up instantly.
These workstations have some connection to ServerOld that cannot be broken.
I run netstat –a on workstation1 and it shows a connection to Server Old :
TCP Workstation1:1725 192.168.1.11:netbios-ssn ESTABLISHED
I run TCPView and get:
[System Process]:0 TCP workstation1:1758 ServerOld:netbios-ssn TIME_WAIT

ServerOld used to be have shares on it that these workstations mapped drives
to but I deleted the drive mappings. I even disjoined the workstation1 from
domain and it still had slow although not as slow when ServerOld was
disconnected. Then when it was reconnected it ran fine. Rejoined it to the
domain and same issue as before.
Is there some hidden mapping or connection that could be causing this? What
is the System Process 0 connection on netbios-ssn and Microsoft-ds
connections for?

Any help as I would like to take this old server offline but I can’t because
it kills the entire accounting departments workstations.
Thanks,
D

 

[John7]

Re: XP clients terrible performance when old server is disconnected ne

Hi Danny,


I had similar problems. It proved that the major source are links and
references to the old server.
When ServerOld is off/disconneted, any access through these references waits
until timeout,
hence the delays.

1. Give the new server a different name then the old server.
This allows you to diffentiate references to the servers.

2. Give the new server a different IP-address then the old server.

Take the following steps on a pilot system and write down EXACTLY what you
do.

3. In Nethood SHIFT-DELETE all references to the old server.
No fear, these are just links although there is no arrow in the icon.
Also confirm to delete Desktop.ini

4. Disconnect all Network Drives to the old server / check server scripts
that do so.

5. On Desktop / in My Documents / etc. SHIFT-DELETE links to folders
and files on the old server.

6. Disable Offline Files.

7. In Control Panel / Printers and Faxes, delete printers that were attached
to the old server.

8. Get CCleaner (www.ccleaner.com), uncheck Cookies, Analyze and Cleanup
files (no registry cleanup).
MRU-lists like in Start - Recently Opened and Office Word-File maintain
links to Most Recently Used files.

9. Reboot and test the issue.

10. Repeat steps 3 - 8 for all accounts.


Did this resolve your issue ?

John7


"Danny F" <DannyF@discussions.microsoft.com> schreef in bericht
news:9FB1894C-53AF-4623-8C70-148197734F29@microsoft.com...
>I have an issue that has been driving me insane. I have 4 Windows XP Pro
>SP3
> workstations. All the Accounting Dept PC's. I also have an old Windows
> 2000
> SP4 Server that I want to take offline and decommission. The problem is
> as
> soon as I disconnect this server or shut it down. The 4 workstations slow
> to
> a crawl. Not just on the network but performance as well. Here is the
> scenario:
> Workstation 1 connected to network and Server Old connected to network.
> Everything works great, PC's screaming fast.
> Unplug network cable of ServerOld, workstation1 slows to a crawl.
> Open command prompt and type notepad to open notepad 60 seconds before
> notepad opens. (I use notepad as a test but all other commands take
> forever
> just to initiate as well including running IE or doing anything on the
> network, but apps run slow as hell to)
> Plug Serverold network cable back in. Type notepad in command prompt,
> instantly opens.
> If I unplug ServerOld network cable again, type notepad, 60 seconds before
> it opens. But if I then unplug Worksation1 network cable so it is no
> longer
> on network, notepad comes up instantly.
> These workstations have some connection to ServerOld that cannot be
> broken.
> I run netstat -a on workstation1 and it shows a connection to Server Old :
> TCP Workstation1:1725 192.168.1.11:netbios-ssn ESTABLISHED
> I run TCPView and get:
> [System Process]:0 TCP workstation1:1758 ServerOld:netbios-ssn TIME_WAIT
>
> ServerOld used to be have shares on it that these workstations mapped
> drives
> to but I deleted the drive mappings. I even disjoined the workstation1
> from
> domain and it still had slow although not as slow when ServerOld was
> disconnected. Then when it was reconnected it ran fine. Rejoined it to the
> domain and same issue as before.
> Is there some hidden mapping or connection that could be causing this?
> What
> is the System Process 0 connection on netbios-ssn and Microsoft-ds
> connections for?
>
> Any help as I would like to take this old server offline but I can't
> because
> it kills the entire accounting departments workstations.
> Thanks,
> D
>