Then I installed Windows 2003 SP2 and after a reboot only my Windows
XP SP2 machine can communicate without any delay. When I try to
connect to an administrative share from my Vista Business machine
there is a long delay before I have to authenticate and after
authentication every click causes another delay. When I connect to the
servers console (mstsc /console) there is also a delay in every click
(LAN-LAN). This is not the case when connection from my XP SP2
machine.
All machines are stand alone and not participating in any domain.
Can anyone confirm this and / or tell me how to resolve this?
Arjan
A
<ahs.b...@gmail.com> wrote in message
news:1174381991.7...@e1g2000hsg.googlegroups.com...
Thx for your reply, however I stated that there is no domain (all
machines are stand alone)
Next: I reproduced this scenario twice on my hardware and the problem
resolves when I remove SP2.
It is a clean windows 2003 R2 Standard 64 bit Edition....no upgrades
here!
Arjan
"Arjan" <ahs.b...@gmail.com> wrote in message
news:1174404835....@p15g2000hsd.googlegroups.com...
Thz Jose for this confirmation.
I did not yet find the reason for this delay and tomorrow I am going
to check at another site where we recently installed SP2 on some
servers.
results will be added here!
Arjan
EggHeadCafe.com - .NET Developer Portal of Choice
http://www.eggheadcafe.com
We see the same issues in our lab. I have tracked this down further
yesterday. Only x64 servers seem to be affected.
This seems to be a client issue: It only occurs when using a Vista
workstation. From XPSP2 or W2K3SP1 clients everything works properly.
I think the problems are introduced by the new networking features
included with SP2.
Disabling some of them client-side solves the problem for me:
netsh interface tcp set global rss=disabled
netsh interface tcp set global autotuninglevel=disabled
and reboot
Markus
Today I installed SP2 on a Windows 2003 R2 Enterprise Edition 32-bit
server and did not notice any problems with my Vista machine. This is
the same Vista machine I used when testing communications with a
windows 2003 R2 standard x64 server at another location so I confirm
the conclusion of Markus: This only affects x64 servers.
I also compared the GPO settings on both sites and they are "out of
the box" after installing the server. I did not find any difference
here!
I am going to try the settings client site (see post Markus). Thanks
Markus for the tips.
Arjan
"mmmm" wrote in message news:2007321207...@sbcglobal.net...
"Arjan" <ahs.b...@gmail.com> wrote in message
news:1174432827.0...@d57g2000hsg.googlegroups.com...
Thank you all
"José Antonio Quílez [MS MVP]" <jquilez...@hotmail.com> wrote in message
news:epLu9DEb...@TK2MSFTNGP04.phx.gbl...
started up windows firewall service and then disabled firewall. No reboot and everything works at the expected speed now!
2003 R2 SP1
I did have an origional issue with the inbuilt adapters on my servers using
broadcom chipsets and I had to disable the RSS on the cards. Have since added
intel chipset cards.
Any idea what the underlying cause is and is there a permanent fix for the
server side?
Cheers
Thanks all for the help this was invaluable.
"Denton" wrote:
> That is bizzar!!
>
> Had the same problem, started ICS and Firewall services then turned the fire
> wall off and it is fixed.
I'm sooooo glad I stumbled across this thread. I was experiencing the
same slowness issues with 2 vista laptops on one of our client's
domains.
The domain is a Windows 2003 RC2 SP1 (Std) Server. It all seemed to
happen after I applied the following bundle of patches:
Windows Server 2003 Security Update for Windows Server 2003 (KB935839)
Wednesday, 13 June 2007 Windows Update
Windows Server 2003 Windows Malicious Software Removal Tool - June 2007
(KB890830) Wednesday, 13 June 2007 Windows Update
Windows Server 2003 Security Update for Windows Server 2003 (KB935840)
Wednesday, 13 June 2007 Windows Update
Windows Server 2003 Cumulative Security Update for Outlook Express for
Windows Server 2003 (KB929123) Wednesday, 13 June 2007 Windows Update
Windows Server 2003 Cumulative Security Update for Internet Explorer 7
for Windows Server 2003 (KB933566) Wednesday, 13 June 2007 Windows
Update
Windows Server 2003 Update for Windows Server 2003 (KB927891)
Wednesday, 13 June 2007 Windows Update
Windows Server 2003 Security Update for Windows Server 2003 (KB935966)
Wednesday, 13 June 2007 Windows Update
Windows Server 2003 Security Update for Windows Server 2003 (KB932168)
Wednesday, 13 June 2007 Windows Update
Windows Server 2003 Security Update for Windows Server 2003 (KB931784)
Wednesday, 13 June 2007 Windows Update
Windows Server 2003 Security Update for Windows Server 2003 (KB930178)
Wednesday, 13 June 2007 Windows Update
Windows Server 2003 Security Update for Windows Server 2003 (KB925902)
Wednesday, 13 June 2007 Windows Update
As you can see, the problem is not limited to the x64 version of
Windows, and not limited to SP2 either! Unfortunately, I'm unable to
pinpoint which of the above patches caused the issue.
I can verify that the starting and stopping of the Windows Firewall
service fixes the issue. Although it's a simple fix for most people,
for me it meant that I had to completely disable Routing and Remote
Access which was used for the VPN connections (I tried just stopping
the service, but that didn't work).
Also, in regards to the two lines quoted:
netsh interface tcp set global rss=disabled
netsh interface tcp set global autotuninglevel=disabled
I'm having issues with the parameter being incorrect etc (a user
reported this to me, I have not witnessed it first hand)? Is there
something fundamental he is doing wrong? I thought it was just a copy
and paste into a command prompt and hit enter after each line.
Great post guys!
PC
--
drsplodge
------------------------------------------------------------------------
drsplodge's Profile: http://forums.techarena.in/member.php?userid=26692
View this thread: http://forums.techarena.in/showthread.php?t=709308
I tried the following commands as suggested on my Vista computer:
netsh interface tcp set global rss=disabled
netsh interface tcp set global autotuninglevel=disabled
I got the following error:
"set global command failed on IPv4. The requested operation requires
elevation."
Any help will be appreciated....
thanks
"Denton" wrote:
> That is bizzar!!
>
> Had the same problem, started ICS and Firewall services then turned the fire
> wall off and it is fixed.
>
> "Daniel Damlin" wrote:
>