Re: network slows down after SP2 install

Susan:

The reinstall was done for reasons related to the Logitech desktop manager
software that came installed to support the Logitech wireless keyboard &
mouse. Using the bluetooth wireless stuff is OK, but if you get the desktop
manager, it does a little too much and the guys accepted the update from
Logitech. It killed 3 machines. I could not even use the system restore
feature to recover. Logitech support could not correct it and suggested
that we remove the desktop manager on all the other systems.

Jim
"Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]" <sbradcpa@xxxxxxxxxxx>
wrote in message news:%230Byjo$oHHA.2596@xxxxxxxxxxxxxxxxxxxxxxx
Also did the tech really tell you to reinstall the workstations?

jim smith wrote:
Robert:

The only item on your list I cannot address as already being done is item
3. I will check that later this morning.

It still bugs me that SP2 would be this harmful.

My users still use ACT! 6.0 and before SP2, they could open the database
and run just fine. Now, the program will open the database and then
fail, giving a hard error. That's the XP Pro, original installs. These
machines cannot even run the program locally being disconnected from the
server with a local copy of the database. Some policy or something has
been really hosed. However, the machines updated from W2K still open and
read the database just fine! Go figure.

Jim






"Robert Li [MSFT]" <v-robeli@xxxxxxxxxxxxxxxxxxxx> wrote in message
news:rlLjkv2oHHA.1144@xxxxxxxxxxxxxxxxxxxxxxxxx

Hi Paul,

Thanks for posting in our newsgroup and also for Susan's input.

First you have called the MS phone support, but it's not resolved. The
problem is really complex. Thanks for your time and patience.

Please take the following steps:

Step 1: Disable SMB signing.

SMB signing is designed to prevent against Man-in-the-middle attacks but
will reduce network performance because every packet has to be signed,
and
every packet has to be decrypted.

To disable SMB signing in Windows 2003, perform the following steps.

1. Open GPEDIT.MSC
2. Open the "Computer Configuration\Windows Settings\Security
Settings\Local Policies\Security Options" folder.
3. Locate the "Microsoft network server: Digitally sign communications
(always)" policy setting, and then click "Disabled" or "Do Not
Configure".

You can also modify the following key to disable SMB signing.

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\lanmanserver\parameter
s]
"enablesecuritysignature"=dword:00000000
"requiresecuritysignature"=dword:00000000

Step 2: Look at the following KBs:

927695 You cannot host TCP connections when Receive Side Scaling is
enabled
in Windows Server 2003 with Service Pack 2

http://support.microsoft.com/default.aspx?scid=kb;EN-US;927695

Windows 2003 service pack 2 known issues on Small Business Server 2003
http://support.microsoft.com/?id=555912

Step 3: Take the steps in KB 321098
Slow network performance occurs if you copy files to a domain controller
that is running Windows 2000 or Windows Server 2003
http://support.microsoft.com/kb/321098/


Step 4: On the server, change the NIC properties.

Go to Internal NIC properties, On general tab clicked configure button,
click advanced tab,

Turn off following properties
Offload Receive IP checksum,
Offload Receive TCP checksum,
Offload TCP segmentation,
Offload transmit IP checksum
Offload transmit TCP checksum

Step 4: Install SP2 for WIN XP and latest service pack for Office 2003
on
client computer.

I am looking forward to hear from you.

If you need further assistance, please don't hesitate to let me know.

Best regards,

Robert Li(MSFT)

Microsoft CSS Online Newsgroup Support

Get Secure! - www.microsoft.com/security

=====================================================

This newsgroup only focuses on SBS technical issues. If you have issues
regarding other Microsoft products, you'd better post in the
corresponding
newsgroups so that they can be resolved in an efficient and timely
manner.
You can locate the newsgroup here:
http://www.microsoft.com/communities/newsgroups/en-us/default.aspx

When opening a new thread via the web interface, we recommend you check
the
"Notify me of replies" box to receive e-mail notifications when there
are
any updates in your thread. When responding to posts via your
newsreader,
please "Reply to Group" so that others may learn and benefit from your
issue.

Microsoft engineers can only focus on one issue per thread. Although we
provide other information for your reference, we recommend you post
different incidents in different threads to keep the thread clean. In
doing
so, it will ensure your issues are resolved in a timely manner.

For urgent issues, you may want to contact Microsoft CSS directly.
Please
check http://support.microsoft.com for regional support phone numbers.

Any input or comments in this thread are highly appreciated.

=====================================================

This posting is provided "AS IS" with no warranties, and confers no
rights.

--------------------
<Reply-To: "Paul Fitzgerald [MSFT]" <paulfi@xxxxxxxxxxxxxxxxxxxx>
<From: "Paul Fitzgerald [MSFT]" <paulfi@xxxxxxxxxxxxxxxxxxxx>
<References: <A7900F82-BFD9-42CD-90C0-F31782C5C76D@xxxxxxxxxxxxx>
<In-Reply-To: <A7900F82-BFD9-42CD-90C0-F31782C5C76D@xxxxxxxxxxxxx>
<Subject: Re: network slows down after SP2 install
<Date: Wed, 30 May 2007 22:33:04 -0700
<Lines: 47
<Organization: MSFT
<Message-ID: <E7E699F9-B4B2-4E27-B0CA-4BD0D3AF0E6C@xxxxxxxxxxxxx>
<MIME-Version: 1.0
<Content-Type: text/plain;
< format=flowed;
< charset="Utf-8";
< reply-type=original
<Content-Transfer-Encoding: 7bit
<X-Priority: 3
<X-MSMail-Priority: Normal
<X-Newsreader: Microsoft Windows Mail 6.0.6000.16386
<X-MimeOLE: Produced By Microsoft MimeOLE V6.0.6000.16386
<X-MS-CommunityGroup-PostID: {E7E699F9-B4B2-4E27-B0CA-4BD0D3AF0E6C}
<X-MS-CommunityGroup-ThreadID: A7900F82-BFD9-42CD-90C0-F31782C5C76D
<X-MS-CommunityGroup-ParentID: A7900F82-BFD9-42CD-90C0-F31782C5C76D
<Newsgroups: microsoft.public.windows.server.sbs
<Path: TK2MSFTNGHUB02.phx.gbl
<Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.windows.server.sbs:40528
<NNTP-Posting-Host: TK2MSFTNGHUB02.phx.gbl 127.0.0.1
<X-Tomcat-NG: microsoft.public.windows.server.sbs
<
<They all had to be flattened and XP Pro re-installed
<
<are you saying that a support engineer from microsoft asked you to
reinstall
<all of your clients?
<
<
<"jim" <jim@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
<news:A7900F82-BFD9-42CD-90C0-F31782C5C76D@xxxxxxxxxxxxxxxx
<> The blog notes and instructions from the SBS blog have all been
heeded.
<> 32
<> hours of talking with tech support on the phone, changing the nic
card,
<> updating all the drivers, and still, the system is dogging to the
point
of
<> being painful. Here is the unexplainable issue: I have 5 new
machines,
<> all
<> came from Dell with XP Pro installed. They all had to be flattened
and
XP
<> Pro re-installed. They worked great until SP2 was installed. Now
they
<> take
<> 5 minutes to open an 8MB spread*** they used to open in 20 seconds.
My
<> 3
<> old machines were upgraded from W2K to XP Pro and they worked fine
before
<> SP2
<> was installed. Afterward, they are slower, but work better than the
new
<> machines. The old machines can still run ACT 6.0. The new machines
fail
<> with a program error after opening the database. Explain that!
<>
<> All file access to the network is so slow now. Don't suggest
anything
<> previously mentioned in the blog. 4 MS engineers can verify that all
the
<> tricks have been done as outlined in this blog.
<>
<> There must have been some other deep layer of connectivity between
the
<> server and workstations that does some kind of handshaking/security
<> checking
<> that is slowing things down. Excel seems to have been hit the
hardest.
<> It
<> is a terrible thing to see a 2GB 4Ghz Dual Core processor take 60
seconds
<> to
<> copy 10 files of 80K each from the network to the local drive.
<>
<> I have 5 SBS 2003 servers and 3 of them are just fine. This one is
dying
<> and SP2 failed to install on the other one. I am afraid to work the
issue
<> as
<> it might turn out like this one.
<>
<> I really do need ideas and help short of flattening the server, as
that
<> may
<> not help anyway. Ideas, anyone?
<
<







.