Jump to content

Server 2003 Stardard SP1 to SP2


Recommended Posts

Posted

After installing SP2 on my DC I found that I was unable to login through

terminal services to my terminal services server (not on the domain). I

received the "RPC server unavailable" error when I attempted to login.

However I am able to login directly to the console.

 

Is there a work around of a fix to this issue? Do I need to provide more

information?

  • Replies 3
  • Created
  • Last Reply

Popular Days

Guest Thee Chicago Wolf
Posted

Re: Server 2003 Stardard SP1 to SP2

 

>After installing SP2 on my DC I found that I was unable to login through

>terminal services to my terminal services server (not on the domain). I

>received the "RPC server unavailable" error when I attempted to login.

>However I am able to login directly to the console.

>

>Is there a work around of a fix to this issue? Do I need to provide more

>information?

 

Microsoft had a KB article up (KB944011) that details some problems

when updating to SP2. They removed it a few days ago for whatever

reason but here's the synopsis in case you'd like to try a couple of

the solutions outlined therein:

 

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 SP2.

 

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.

 

Hope this is useful information to you.

 

- Thee Chicago Wolf

Guest Thee Chicago Wolf
Posted

Re: Server 2003 Stardard SP1 to SP2

 

>After installing SP2 on my DC I found that I was unable to login through

>terminal services to my terminal services server (not on the domain). I

>received the "RPC server unavailable" error when I attempted to login.

>However I am able to login directly to the console.

>

>Is there a work around of a fix to this issue? Do I need to provide more

>information?

 

In checking the KB, I found an article referring the exact problem

you're seeing but the fix is an older rdpdr.sys file that is surely

newer in SP2. View it here:

http://support.microsoft.com/kb/883670/en-us

 

There is a KB article that does have a newer rdpdr.sys file in the

following KB article so maybe grab it and give it a try:

http://support.microsoft.com/kb/938645/en-us

 

- Thee Chicago Wolf

Guest chriske911
Posted

Re: Server 2003 Stardard SP1 to SP2

 

Kevin submitted this idea :

> After installing SP2 on my DC I found that I was unable to login through

> terminal services to my terminal services server (not on the domain). I

> received the "RPC server unavailable" error when I attempted to login.

> However I am able to login directly to the console.

> Is there a work around of a fix to this issue? Do I need to provide more

> information?

 

I have exactly the same problem with servers running sp2

I have a case with MS for this and they provided the same info as Wolf

has given

I got an answer that MS does not advice you to use RDP when updating

8-o

something I have been doing for many years now

the case is still open

 

grtz


×
×
  • Create New...