Re: Terminal Services hang and can't be restartet except with Serv

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

Are you connecting to the TS over your LAN or over a WAN
connection?
Check if this helps:

898060 - Installing security update MS05-019 or Windows Server 2003
Service Pack 1 may cause network connectivity between clients and
servers to fail
http://support.microsoft.com/?kbid=898060
_________________________________________________________
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?YWxwaGEtY2VudGF1cmk=?=
<alphacentauri@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote on 15 aug 2006 in
microsoft.public.windows.terminal_services:

We us the remotedesktop just for administration purpose. the
eventlog don't mention anything in conjunction with this error.

the server just does not accept connections.

"Lanwench [MVP - Exchange]" wrote:



In news:0510BB56-2382-480C-83AD-05F6C51D58D1@xxxxxxxxxxxxx,
alpha-centauri <alphacentauri@xxxxxxxxxxxxxxxxxxxxxxxxx> typed:
Hello!

System: Server 2003 SP1

Clients: Windows XP

We just use the built in 2 TS sessions allowed for the
server.

After a few days, we can't connect to the server per
remote-desktop client.

the client starts, we enter the DNS name, it starts the
connections and returns after two seconds havin done nothing.

server is working. it can be pinged. listening on 3389
(netstat). "telnet srvname 3389 " is working.

I have to reboot the server, which is very disappointing.

If I look at the services.msc, the Terminal Services and RPC
can't be manually restarted, because the buttons are grayed
out.

What can I do, except a reboot?

Start by looking at your event logs...

You do know that the built-in Remote Desktop (which isn't TS in
W2003-speak) is for admin use only, right? Not for
users/application mode use.
.

Quantcast