Can not access Terminal Server via Remote Desktop

  • Thread starter Thread starter Adam V.
  • Start date Start date
A

Adam V.

Guest
Hello:

I have a Windows Server 2003 R2 running Terminal Services. We have a second
location that accesses this server via RDP over a VPN. Everything has worked
fine for a couple of years. This morning, no one could connect to the server
through RDP (either from the remote location or locally). When it fails to
connect, it says "your Remote Desktop Session has ended possibly for one of
the following reasons : network problem, admin ended the session, an error
occurred . . ."

I noticed under Terminal Server licensing that the activation status was
"NOT ACTIVATED". I went ahead and reinstalled the terminal server CALs.
Then, I noticed the C: drive on the server was almost out of disk space. I
cleaned up the C: drive and made about 1.5 GB available, then rebooted the
server. Unfortunately, the Terminal Server is still inaccessible through
RDP. I can access files on the server over the LAN, I can ping it, etc. The
only thing I can't do is access it with RDP. We have an application that the
remote people need to access through Remote Desktop. I don't see any errors
in the event viewer, and all the correct services appear to be running. I
don't know if the low disk space situation disabled something but I don't see
anything wrong.

Any advice would be much appreciated. Thanks, Adam V.
 
Re: Can not access Terminal Server via Remote Desktop

On the console of the server, can you check if the server is
listening on port 3389, by typing "netstat -an"?
Can you connect to the server itself from the console?
Is the TS Licensing Server now activated?
Are sessions enabled? check with "change logon /query"
_________________________________________________________
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?QWRhbSBWLg==?= <AdamV@discussions.microsoft.com> wrote
on 28 aug 2008 in microsoft.public.windows.terminal_services:

> Hello:
>
> I have a Windows Server 2003 R2 running Terminal Services. We
> have a second location that accesses this server via RDP over a
> VPN. Everything has worked fine for a couple of years. This
> morning, no one could connect to the server through RDP (either
> from the remote location or locally). When it fails to connect,
> it says "your Remote Desktop Session has ended possibly for one
> of the following reasons : network problem, admin ended the
> session, an error occurred . . ."
>
> I noticed under Terminal Server licensing that the activation
> status was "NOT ACTIVATED". I went ahead and reinstalled the
> terminal server CALs. Then, I noticed the C: drive on the
> server was almost out of disk space. I cleaned up the C: drive
> and made about 1.5 GB available, then rebooted the server.
> Unfortunately, the Terminal Server is still inaccessible through
> RDP. I can access files on the server over the LAN, I can ping
> it, etc. The only thing I can't do is access it with RDP. We
> have an application that the remote people need to access
> through Remote Desktop. I don't see any errors in the event
> viewer, and all the correct services appear to be running. I
> don't know if the low disk space situation disabled something
> but I don't see anything wrong.
>
> Any advice would be much appreciated. Thanks, Adam V.
 
Re: Can not access Terminal Server via Remote Desktop

The "netstat -an" command indicates the following (as it relates to port 3389):
TCP port
Local Address: 0.0.0.0:3389
Foreign Address: 0.0.0.0
State = Listening

As for connecting to the server itself from the console, I'm not exactly
sure what you mean. From a command prompt, I can ping the server's own IP
address. I can NOT connect to the server's own IP address using RDP on the
server itself. It gives me the same error message.

The licensing server IS activated. It is also the same server as the
Terminal Server.

The "change logon /query" command indicates sessions ARE enabled.

I'm stumped. Any ideas?

Thanks.

"Vera Noest [MVP]" wrote:

> On the console of the server, can you check if the server is
> listening on port 3389, by typing "netstat -an"?
> Can you connect to the server itself from the console?
> Is the TS Licensing Server now activated?
> Are sessions enabled? check with "change logon /query"
> _________________________________________________________
> 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?QWRhbSBWLg==?= <AdamV@discussions.microsoft.com> wrote
> on 28 aug 2008 in microsoft.public.windows.terminal_services:
>
> > Hello:
> >
> > I have a Windows Server 2003 R2 running Terminal Services. We
> > have a second location that accesses this server via RDP over a
> > VPN. Everything has worked fine for a couple of years. This
> > morning, no one could connect to the server through RDP (either
> > from the remote location or locally). When it fails to connect,
> > it says "your Remote Desktop Session has ended possibly for one
> > of the following reasons : network problem, admin ended the
> > session, an error occurred . . ."
> >
> > I noticed under Terminal Server licensing that the activation
> > status was "NOT ACTIVATED". I went ahead and reinstalled the
> > terminal server CALs. Then, I noticed the C: drive on the
> > server was almost out of disk space. I cleaned up the C: drive
> > and made about 1.5 GB available, then rebooted the server.
> > Unfortunately, the Terminal Server is still inaccessible through
> > RDP. I can access files on the server over the LAN, I can ping
> > it, etc. The only thing I can't do is access it with RDP. We
> > have an application that the remote people need to access
> > through Remote Desktop. I don't see any errors in the event
> > viewer, and all the correct services appear to be running. I
> > don't know if the low disk space situation disabled something
> > but I don't see anything wrong.
> >
> > Any advice would be much appreciated. Thanks, Adam V.
>
 
Re: Can not access Terminal Server via Remote Desktop

Long shot, but check if this helps:

My Terminal Server does not respond after a reboot. How do I solve
this?
http://ts.veranoest.net/ts_faq_connectivity.htm#no_access_after_reb
oot

If not, then I think that I would delete the existing rdp-tcp
connection and create a new one, then reboot the server once more.

_________________________________________________________
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?QWRhbSBWLg==?= <AdamV@discussions.microsoft.com> wrote
on 29 aug 2008 in microsoft.public.windows.terminal_services:

> The "netstat -an" command indicates the following (as it relates
> to port 3389): TCP port
> Local Address: 0.0.0.0:3389
> Foreign Address: 0.0.0.0
> State = Listening
>
> As for connecting to the server itself from the console, I'm not
> exactly sure what you mean. From a command prompt, I can ping
> the server's own IP address. I can NOT connect to the server's
> own IP address using RDP on the server itself. It gives me the
> same error message.
>
> The licensing server IS activated. It is also the same server
> as the Terminal Server.
>
> The "change logon /query" command indicates sessions ARE
> enabled.
>
> I'm stumped. Any ideas?
>
> Thanks.
>
> "Vera Noest [MVP]" wrote:
>
>> On the console of the server, can you check if the server is
>> listening on port 3389, by typing "netstat -an"?
>> Can you connect to the server itself from the console?
>> Is the TS Licensing Server now activated?
>> Are sessions enabled? check with "change logon /query"
>> _________________________________________________________
>> 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?QWRhbSBWLg==?= <AdamV@discussions.microsoft.com>
>> wrote on 28 aug 2008 in
>> microsoft.public.windows.terminal_services:
>>
>> > Hello:
>> >
>> > I have a Windows Server 2003 R2 running Terminal Services.
>> > We have a second location that accesses this server via RDP
>> > over a VPN. Everything has worked fine for a couple of
>> > years. This morning, no one could connect to the server
>> > through RDP (either from the remote location or locally).
>> > When it fails to connect, it says "your Remote Desktop
>> > Session has ended possibly for one of the following reasons :
>> > network problem, admin ended the session, an error occurred .
>> > . ."
>> >
>> > I noticed under Terminal Server licensing that the activation
>> > status was "NOT ACTIVATED". I went ahead and reinstalled the
>> > terminal server CALs. Then, I noticed the C: drive on the
>> > server was almost out of disk space. I cleaned up the C:
>> > drive and made about 1.5 GB available, then rebooted the
>> > server. Unfortunately, the Terminal Server is still
>> > inaccessible through RDP. I can access files on the server
>> > over the LAN, I can ping it, etc. The only thing I can't do
>> > is access it with RDP. We have an application that the
>> > remote people need to access through Remote Desktop. I don't
>> > see any errors in the event viewer, and all the correct
>> > services appear to be running. I don't know if the low disk
>> > space situation disabled something but I don't see anything
>> > wrong.
>> >
>> > Any advice would be much appreciated. Thanks, Adam V.
 
Re: Can not access Terminal Server via Remote Desktop

Good News. The long shot paid off this time. Following the instructions in
the link below solved the problem. Thanks a million.

Adam V.

"Vera Noest [MVP]" wrote:

> Long shot, but check if this helps:
>
> My Terminal Server does not respond after a reboot. How do I solve
> this?
> http://ts.veranoest.net/ts_faq_connectivity.htm#no_access_after_reb
> oot
>
> If not, then I think that I would delete the existing rdp-tcp
> connection and create a new one, then reboot the server once more.
>
> _________________________________________________________
> 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?QWRhbSBWLg==?= <AdamV@discussions.microsoft.com> wrote
> on 29 aug 2008 in microsoft.public.windows.terminal_services:
>
> > The "netstat -an" command indicates the following (as it relates
> > to port 3389): TCP port
> > Local Address: 0.0.0.0:3389
> > Foreign Address: 0.0.0.0
> > State = Listening
> >
> > As for connecting to the server itself from the console, I'm not
> > exactly sure what you mean. From a command prompt, I can ping
> > the server's own IP address. I can NOT connect to the server's
> > own IP address using RDP on the server itself. It gives me the
> > same error message.
> >
> > The licensing server IS activated. It is also the same server
> > as the Terminal Server.
> >
> > The "change logon /query" command indicates sessions ARE
> > enabled.
> >
> > I'm stumped. Any ideas?
> >
> > Thanks.
> >
> > "Vera Noest [MVP]" wrote:
> >
> >> On the console of the server, can you check if the server is
> >> listening on port 3389, by typing "netstat -an"?
> >> Can you connect to the server itself from the console?
> >> Is the TS Licensing Server now activated?
> >> Are sessions enabled? check with "change logon /query"
> >> _________________________________________________________
> >> 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?QWRhbSBWLg==?= <AdamV@discussions.microsoft.com>
> >> wrote on 28 aug 2008 in
> >> microsoft.public.windows.terminal_services:
> >>
> >> > Hello:
> >> >
> >> > I have a Windows Server 2003 R2 running Terminal Services.
> >> > We have a second location that accesses this server via RDP
> >> > over a VPN. Everything has worked fine for a couple of
> >> > years. This morning, no one could connect to the server
> >> > through RDP (either from the remote location or locally).
> >> > When it fails to connect, it says "your Remote Desktop
> >> > Session has ended possibly for one of the following reasons :
> >> > network problem, admin ended the session, an error occurred .
> >> > . ."
> >> >
> >> > I noticed under Terminal Server licensing that the activation
> >> > status was "NOT ACTIVATED". I went ahead and reinstalled the
> >> > terminal server CALs. Then, I noticed the C: drive on the
> >> > server was almost out of disk space. I cleaned up the C:
> >> > drive and made about 1.5 GB available, then rebooted the
> >> > server. Unfortunately, the Terminal Server is still
> >> > inaccessible through RDP. I can access files on the server
> >> > over the LAN, I can ping it, etc. The only thing I can't do
> >> > is access it with RDP. We have an application that the
> >> > remote people need to access through Remote Desktop. I don't
> >> > see any errors in the event viewer, and all the correct
> >> > services appear to be running. I don't know if the low disk
> >> > space situation disabled something but I don't see anything
> >> > wrong.
> >> >
> >> > Any advice would be much appreciated. Thanks, Adam V.
>
 
Re: Can not access Terminal Server via Remote Desktop

Great! Glad that your problem is solved, Adam, and thanks for the
feedback!
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
*----------- Please reply in newsgroup -------------*

=?Utf-8?B?QWRhbSBWLg==?= <AdamV@discussions.microsoft.com> wrote
on 31 aug 2008:

> Good News. The long shot paid off this time. Following the
> instructions in the link below solved the problem. Thanks a
> million.
>
> Adam V.
>
> "Vera Noest [MVP]" wrote:
>
>> Long shot, but check if this helps:
>>
>> My Terminal Server does not respond after a reboot. How do I
>> solve this?
>> http://ts.veranoest.net/ts_faq_connectivity.htm#no_access_after_
>> reb oot
>>
>> If not, then I think that I would delete the existing rdp-tcp
>> connection and create a new one, then reboot the server once
>> more.
>>
>> _________________________________________________________
>> 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?QWRhbSBWLg==?= <AdamV@discussions.microsoft.com>
>> wrote on 29 aug 2008 in
>> microsoft.public.windows.terminal_services:
>>
>> > The "netstat -an" command indicates the following (as it
>> > relates to port 3389): TCP port
>> > Local Address: 0.0.0.0:3389
>> > Foreign Address: 0.0.0.0
>> > State = Listening
>> >
>> > As for connecting to the server itself from the console, I'm
>> > not exactly sure what you mean. From a command prompt, I can
>> > ping the server's own IP address. I can NOT connect to the
>> > server's own IP address using RDP on the server itself. It
>> > gives me the same error message.
>> >
>> > The licensing server IS activated. It is also the same
>> > server as the Terminal Server.
>> >
>> > The "change logon /query" command indicates sessions ARE
>> > enabled.
>> >
>> > I'm stumped. Any ideas?
>> >
>> > Thanks.
>> >
>> > "Vera Noest [MVP]" wrote:
>> >
>> >> On the console of the server, can you check if the server is
>> >> listening on port 3389, by typing "netstat -an"?
>> >> Can you connect to the server itself from the console?
>> >> Is the TS Licensing Server now activated?
>> >> Are sessions enabled? check with "change logon /query"
>> >> _________________________________________________________
>> >> 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?QWRhbSBWLg==?= <AdamV@discussions.microsoft.com>
>> >> wrote on 28 aug 2008 in
>> >> microsoft.public.windows.terminal_services:
>> >>
>> >> > Hello:
>> >> >
>> >> > I have a Windows Server 2003 R2 running Terminal Services.
>> >> > We have a second location that accesses this server via
>> >> > RDP over a VPN. Everything has worked fine for a couple
>> >> > of years. This morning, no one could connect to the
>> >> > server through RDP (either from the remote location or
>> >> > locally). When it fails to connect, it says "your Remote
>> >> > Desktop Session has ended possibly for one of the
>> >> > following reasons : network problem, admin ended the
>> >> > session, an error occurred . . ."
>> >> >
>> >> > I noticed under Terminal Server licensing that the
>> >> > activation status was "NOT ACTIVATED". I went ahead and
>> >> > reinstalled the terminal server CALs. Then, I noticed the
>> >> > C: drive on the server was almost out of disk space. I
>> >> > cleaned up the C: drive and made about 1.5 GB available,
>> >> > then rebooted the server. Unfortunately, the Terminal
>> >> > Server is still inaccessible through RDP. I can access
>> >> > files on the server over the LAN, I can ping it, etc. The
>> >> > only thing I can't do is access it with RDP. We have an
>> >> > application that the remote people need to access through
>> >> > Remote Desktop. I don't see any errors in the event
>> >> > viewer, and all the correct services appear to be running.
>> >> > I don't know if the low disk space situation disabled
>> >> > something but I don't see anything wrong.
>> >> >
>> >> > Any advice would be much appreciated. Thanks, Adam V.
 
Back
Top