Re: Can't connect to Terminal Services following upgrade of Win 2003 to service pack 1
- From: "Vera Noest [MVP]" <vera.noest@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Thu, 19 Oct 2006 13:45:59 -0700
Anything in the EventLog on the server?
Is the server listening on port 3389? Check by typing "netstat -
an" at a command prompt.
If "no" to both questions, try with a second reboot.
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___
"Bobby" <bobby2@xxxxxxxxxxxxxxxx> wrote on 19 okt 2006 in
microsoft.public.windows.terminal_services:
Hi all,.
We are using Terminal Services on Windows Server 2003 Standard
Edition version 5.2. I recently upgraded to Service Pack 1 as
requested, and now nobody can connect to Terminal Services.
Can anybody suggest a solution? My knowledge of Terminal
Services is very limited, so it may be that I'm overlooking
something daft, such as a service has not restarted on re-boot.
On the otherhand, I've read about Secure Sockets Layer
(SSL)/Transport Layer Security (TLS) 1.0 for server
authentication, which doesn't mean a lot to me and I'm hoping
that it's a bit more basic than that.
Any help or advice would be greatly appreciated,
Thanks
B
- Follow-Ups:
- References:
- Prev by Date: Re: windows explorer in kiosk mode
- Next by Date: Re: Smart Card > XP > RDP > Win2000 Server ?
- Previous by thread: Can't connect to Terminal Services following upgrade of Win 2003 to service pack 1
- Next by thread: Re: Can't connect to Terminal Services following upgrade of Win 2003 to service pack 1
- Index(es):
Relevant Pages
|