Server 2003 SP2 and Server 2003 R2 SP2

[Guest Juergen Ladrick]

Hi guys,

 

i need some advice: ( and i don not know if this if the right group to

post it, but let´s see...)

 

i have a domain with two dc´s 2003SP2. we added file 2 servers (2003

sp2 and 2003 r2sp2).

now when we browse shares with vista clients, browsing on the 2003

servers is fine, but when

we browse shares on the 2003r2sp2 server, it lasts several minutes

until the directory of the

folder is shown. did anyone of you expierence this behaviour?

 

thanx in advance...

 

juergen ladrick

[Guest Thee Chicago Wolf]

Re: Server 2003 SP2 and Server 2003 R2 SP2

 

>i need some advice: ( and i don not know if this if the right group to

>post it, but let´s see...)

>

>i have a domain with two dc´s 2003SP2. we added file 2 servers (2003

>sp2 and 2003 r2sp2).

>now when we browse shares with vista clients, browsing on the 2003

>servers is fine, but when

>we browse shares on the 2003r2sp2 server, it lasts several minutes

>until the directory of the

>folder is shown. did anyone of you expierence this behaviour?

>

>thanx in advance...

>

>juergen ladrick

 

Hi,

 

Microsoft pulled the KB article pertaining to problems people

experience with SP2 so here's a synopsis of it in case you want to try

or at least be aware of it:

 

Title: Some problems occur after installing Windows Server 2003 SP2

 

Result: After applying Service Pack 2 on your Windows Server 2003

computer, you may experience one of more of the following symptoms:

 

1. If it is an Exchange Server, Exchange queues become clogged in the

MAPI delivery queue. Messages get stuck in this queue and cannot be

delivered.

 

2. ActiveSync may not work on the Exchange Server 2003

 

3. For the IIS server, browsing the public and/or default website in

IIS results in error "Page cannot be displayed"

 

4. Non-Pages Pool (Kernel) memory becomes exhausted

 

5. For a print server, the printing job may be partially missing

 

Cause: The problem may be the result of combining the NIC driver and

the TCP Chimney feature that comes with the Scalable Networking Pack,

which is included in Windows 2003 PS2.

 

With TCP Chimney feature, some NIC driver cause high NonPaged pool

usage.

 

Once there is less than 30MB of available paged pool memory, http.sys

starts rejecting connections.

 

Resolution: Contact the NIC manufacturer and upgrade to the NIC driver

to the latest version. If the driver does not resolve the issue, use

the workaround below.

 

Disable the TCP Chimney feature on the server using the netsh.exe

tool. Click Start, click Run, type cmd, click OK. At the prompt type

netsh.exe int ip set chimney DISABLED and press the Enter key.

 

- Thee Chicago Wolf