Re: RPC Server Is Unavailable on 2003 TS but not on 2000 TS

Mmm, difficult to solve in a forum like a newsgroup.
Check the troubleshooting tips on EventID.net, one of them might
just trigger something.

You wrote that you replaced the server's netword cards (plural!).
You are not using teaming and LB on those NICs, are you? If so,
check if it helps when you disable teaming.

http://www.eventid.net/display.asp?eventid=5719&eventno=104
&source=NETLOGON&phase=1

http://www.eventid.net/display.asp?eventid=1053&eventno=1584
&source=Userenv&phase=1

http://www.eventid.net/display.asp?eventid=1219&eventno=2848
&source=Winlogon&phase=1
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___

=?Utf-8?B?S2Vsdmlu?= <Kelvin@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote on
15 jan 2007 in microsoft.public.windows.terminal_services:

Hi Vera,

Info as requested :-

When this problem occurs, what is the exact error message that
the users receive, if any?
In a Dialog box
Logon Message
The system cannot log you on due to the following error:
The RPC sever is unavailable

Please try again or consult your system administrator.


Do they get this before or after typing in their username and
passowrd?
This happens immediately after entering the password

Do they get to the logon window in the first place?
yes

And can you logon to the physical console of the server when
the problem occurs?
Yes

We even tried restarting the Netlogon service (suggested in
another post) to see if that will allow users to logon again,
but with no success.

Kelvin

"Vera Noest [MVP]" wrote:

OK, I understand.
No, hotfix 883670 was not included in SP1, but released very
shortly after it. So it's perfectly possible that you already
have a newer version of the file, through another hotfix or
Windows Update.
In that case, there's no need to get the hotfix.

When this problem occurs, what is the exact error message that
the users receive, if any? Do they get this before or after
typing in their username and passowrd? Do they get to the logon
window in the first place?
And can you logon to the physical console of the server when
the problem occurs?

_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___

=?Utf-8?B?S2Vsdmlu?= <Kelvin@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote
on 15 jan 2007 in microsoft.public.windows.terminal_services:

Hi Vera,

Thank you or your reply.

In my haste to post, I forgot to mention that I have already
tried quite a number of things based on previous posts on
Technet as well as posts found doing a Google search,
obviously with no success yet other than to reduce the
frequency of this error occurring (but not erradicate it -
this problem has been ongoing for a few months).

In reponse to your suggestions :-

1) I have rechecked the network settings a number of times -
and have also run a number of diagnostics based on previous
posts (NETDIAG, NETDOM, etc.) and all tests always comes back
as passed when the problem is not occurring. The gigabit
network switch and connecting network cables are new
(replaced when problems first showed up) and have also
changed network cards to be thorough. As the old W2K TS isn't
showing any errors, I still think the probem lies with the
2003 TS.

2) I checked the 883670 per your suggestion - however, I
think that is already included in SP1 as the version
currently on the server is a lot newer and has a much higher
version number than the one mentioned in 883670.

Any further suggestion will be most appreciated.

Kelvin



"Vera Noest [MVP]" wrote:

You seem to have some sort of network problem. Check your
DNS and TCPIP parameters. This might help:

http://www.eventid.net/display.asp?eventid=5719&eventno=104
&source=NETLOGON&phase=1

For the sake of completeness, check also:

883670 - FIX: The Terminal Services service stops responding
in Windows Server 2003 and you receive an "The RPC service
is unavailable" error message when you try to connect to the
terminal server by using the Remote Desktop Connection
program http://support.microsoft.com/?kbid=883670

_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
*----------- Please reply in newsgroup -------------*

=?Utf-8?B?S2Vsdmlu?= <Kelvin@xxxxxxxxxxxxxxxxxxxxxxxxx>
wrote on 15 jan 2007:

Hi,

This is an ongoing problem since putting in the 2003 TS
(problem exists from the very start). This problem does
not occur with the existing 2000 TS.

Environment :
SBS 2003 Premium (Dual Xeon 3.2Ghz, 4 GB RAM, RAID 1 OS,
RAID 5 Data with ample free disk space)
Serving approx. 35 users
Exchange IS is at about 10 - 14GB usually
There are 2 major SQL applications running all the time
TrendMicro CSM for SMB is their AV solution running on the
SBS server

Old W2K TS : Windows 2000 Server SP4 (Dual AMD Athlon MP,
2GB RAM, RAID 1)

New 2003 TS : Server 2003 R2 Std 32bit SP1 with all
current Windows Updates loaded (2 x Dual Core Xeon 3.4Ghz,
4GB RAM, RAID 10)


The existing W2K Terminal Server works fine with all their
applications loaded and they only put in the new 2003 TS
because the W2K TS is getting too slow to run their
applications for the number of users in the office. The
same line of business applications are loaded on the new
2003 TS.

The problem only shows up on the new 2003 TS and only ever
appears during logon. If there are already users logged on
when this problem occurs, the users already logged on
appears to be unaffected and can carry on without knowing
there was a problem. However, the users attempting to log
on when this occurs generally must wait some number of
minutes before attempting to log on again and very often
succeed in logging on after waiting a while. And it can be
any user and not particular to any one or group of users
(including the Administrator).

System & Application logs shows a variety of errors (when
the problem occurs at different times) :-
Eg. Event IDs : 5719, 1053, 1219

They may go days without seeing the problem and they may
suddenly have it occurring every day or every other day or
sometimes several times a day. Rebooting the terminal
server lets users login again immediately (until the
problem reoccurs) or they could just sit and wait several
minutes and the system will then let them login. Note that
whenever this problem occurs, they could still log in to a
session on the old W2K TS.

They have tested logging the entire office in to the 2003
TS (without starting any applications after logging in)
and that did not produce any errors. As it is intermittent
mostly, we cannot "cause" it to happen to try and narrow
down what it is that is causing it.

Please help ! The client is threatening to return the
entire server, OS, Software and all unless this problem is
resolved !
.

Relevant Pages

  • RE: Terminal Services stops responding on our Windows Server 2003
    ... Your terminal server issue appears to have several potential causes. ... first thing to check are the applications running. ... initiate a best practices for deployment of terminal services. ...
    (microsoft.public.windows.terminal_services)
  • Re: RPC Server Is Unavailable on 2003 TS but not on 2000 TS
    ... Windows Server 2003 and you receive an "The RPC service is ... MCSE, CCEA, Microsoft MVP - Terminal Server ... There are 2 major SQL applications running all the time ... They have tested logging the entire office in to the 2003 TS ...
    (microsoft.public.windows.terminal_services)
  • Re: RPC Server Is Unavailable on 2003 TS but not on 2000 TS
    ... number of things based on previous posts on Technet as well as posts found ... Windows Server 2003 and you receive an "The RPC service is ... MCSE, CCEA, Microsoft MVP - Terminal Server ... There are 2 major SQL applications running all the time ...
    (microsoft.public.windows.terminal_services)
  • RE: Windows 2003 Server Terminal Services
    ... I tried the first .bat idea, and though it worked, it left the batch file ... accessing applications which they should run. ... MCSE, CCEA, Microsoft MVP - Terminal Server ... Terminal Server role and the Terminal Services Licensing ...
    (microsoft.public.windows.terminal_services)
  • Re: Logging into TS 2003 Problem
    ... MCSE, CCEA, Microsoft MVP - Terminal Server ... TS troubleshooting: http://ts.veranoest.net ...
    (microsoft.public.windows.terminal_services)