Re: RPC Server Unavailable
Check if this fixes your problem:
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
If it doesn't: is there anything else that you can tell us?
Does this happen completely at random, or is there a pattern? Time
of day, user load on the TS, time since last reboot of the TS,
etc.
Have you considered to install SP2 on the TS?
Check this as well:
905700 - You may receive an "RPC server is too busy to complete
this operation" error message when you try to log on to a computer
that is running Windows Server 2003 with Service Pack 1
http://support.microsoft.com/?kbid=905700
_________________________________________________________
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?U2FtIEdpbGw=?= <SamGill@discussions.microsoft.com> wrote
on 10 jul 2007 in microsoft.public.windows.terminal_services:
> None!
>
> "Vera Noest [MVP]" wrote:
>
>> Any warnings or errors in the EventLog on the TS?
>>
>> _________________________________________________________
>> 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?U2FtIEdpbGw=?= <SamGill@discussions.microsoft.com>
>> wrote on 10 jul 2007 in
>> microsoft.public.windows.terminal_services:
>>
>> > Hi,
>> >
>> > Only recently users when logging onto the Terminal Server
>> > have started to encountered this problem, RPC server
>> > unavailable, it doen's happen to all users and not all the
>> > time but it can take several attempts before they can
>> > sucessfully logon.
>> >
>> > The DC is running Windows 2003 Std SP2 and the Terminal
>> > Server is running Windows 2003 Std SP1
>> >
>> > Has anyone come across this issue recently and on how to
>> > resolve it?
>> >
>> > Thks