Hello,

I have a small network with an SBS2000 server on a Proliant ML350G3 (Fully loaded), and 4 XP Pro Workstations (HP D220's w/512MB Ram). The network performs well until we initiate more than one connection to the server. For example, if we browse to a share on the server from a workstation and begin a copy of files from one directory to another the performance is poor until we close the window (leaving only the transfer or xcopy still running), then the performance increases dramatically. A network sniff reveals a large amount of SMB traffic and SMB request errors. An old Q article references this exact issue pre-SP1, however the server is W2kSP4.

We have configured the Oplock registry settings, but still do not have any success. Our primary business application resides on the server, and the db is accessed by the workstations. This network performance has brought our business to a grinding halt. Previously we ran another version of our primary business app on a very old Novell server with 32MB Ram and Win98 workstations and had great performance. We were forced to upgrade the HW and operating system to meet the requirements of the newer version of our primary business app.

If anyone has any suggestions, please let me know

Thank you
Roger

Re: SBS2000 w/XP Pro clients, experiencing slow network performance when opening more than one connection to server by Marina

Marina
Thu Nov 20 13:42:31 CST 2003

Have you checked www.smallbizserver.net for the XP-issues?
Put the XP-nics on anything but autosense. Does the ipconfig/all show that
everything is pointing to your server-IP?

Marina

"Roger" <anonymous@discussions.microsoft.com> schreef in bericht
news:DB4968A6-8538-4E50-B28E-73DA780E8679@microsoft.com...
> Hello,
>
> I have a small network with an SBS2000 server on a Proliant ML350G3
(Fully loaded), and 4 XP Pro Workstations (HP D220's w/512MB Ram). The
network performs well until we initiate more than one connection to the
server. For example, if we browse to a share on the server from a
workstation and begin a copy of files from one directory to another the
performance is poor until we close the window (leaving only the transfer or
xcopy still running), then the performance increases dramatically. A
network sniff reveals a large amount of SMB traffic and SMB request errors.
An old Q article references this exact issue pre-SP1, however the server is
W2kSP4.
>
> We have configured the Oplock registry settings, but still do not
have any success. Our primary business application resides on the server,
and the db is accessed by the workstations. This network performance has
brought our business to a grinding halt. Previously we ran another version
of our primary business app on a very old Novell server with 32MB Ram and
Win98 workstations and had great performance. We were forced to upgrade the
HW and operating system to meet the requirements of the newer version of our
primary business app.
>
> If anyone has any suggestions, please let me know.
>
> Thank you,
> Roger