no longer able to remote in to server

[Guest duke]

Windows Server 2003. Months ago when we got the server new, I was able to

remote into it from my office. Cannot remember if I had to enable this on

the server. Then I installed terminal server to try it out, and after

playing around with it I took it back out because I was afraid it would cut

me off from remote access after the trial ended. Now I can no longer remote

in "The client could not connect to the remote computer".

 

Is there something I have forgotten to reset?

[Guest Myweb]

Re: no longer able to remote in to server

 

Hello duke,

 

You have installed the Terminal server in Application mode i think and after

the trial period you have to install licenses bought by MS. So 2 options,

buy licenses for every user that has to connect to the server or switch back

to Administration mode via add/remove programs windows components terminal

server.

 

Best regards

 

Myweb

Disclaimer: This posting is provided "AS IS" with no warranties, and confers

no rights.

> Windows Server 2003. Months ago when we got the server new, I was

> able to remote into it from my office. Cannot remember if I had to

> enable this on the server. Then I installed terminal server to try it

> out, and after playing around with it I took it back out because I was

> afraid it would cut me off from remote access after the trial ended.

> Now I can no longer remote in "The client could not connect to the

> remote computer".

>

> Is there something I have forgotten to reset?

>

[Guest Vera Noest [MVP]]

Re: no longer able to remote in to server

 

It's a bit unclear, but I take this statement:

>> .. after playing around with it I took it back out

to mean that the OP already uninstalled Terminal Services.

 

If that is correct, then you have to re-enable Remote Desktop for

Administration, in Control Panel - System - Remote.

_________________________________________________________

Vera Noest

MCSE, CCEA, Microsoft MVP - Terminal Server

TS troubleshooting: http://ts.veranoest.net

___ please respond in newsgroup, NOT by private email ___

 

Myweb <meiweb@gmx.de> wrote on 09 aug 2007 in

microsoft.public.windows.terminal_services:

> Hello duke,

>

> You have installed the Terminal server in Application mode i

> think and after the trial period you have to install licenses

> bought by MS. So 2 options, buy licenses for every user that has

> to connect to the server or switch back to Administration mode

> via add/remove programs windows components terminal server.

>

> Best regards

>

> Myweb

> Disclaimer: This posting is provided "AS IS" with no warranties,

> and confers no rights.

>

>> Windows Server 2003. Months ago when we got the server new, I

>> was able to remote into it from my office. Cannot remember if

>> I had to enable this on the server. Then I installed terminal

>> server to try it out, and after playing around with it I took

>> it back out because I was afraid it would cut me off from

>> remote access after the trial ended. Now I can no longer remote

>> in "The client could not connect to the remote computer".

>>

>> Is there something I have forgotten to reset?

[Guest duke]

Re: no longer able to remote in to server

 

terminal server had been removed already and remote enabled... but same

result.

 

"Vera Noest [MVP]" wrote:

> It's a bit unclear, but I take this statement:

> >> .. after playing around with it I took it back out

> to mean that the OP already uninstalled Terminal Services.

>

> If that is correct, then you have to re-enable Remote Desktop for

> Administration, in Control Panel - System - Remote.

> _________________________________________________________

> Vera Noest

> MCSE, CCEA, Microsoft MVP - Terminal Server

> TS troubleshooting: http://ts.veranoest.net

> ___ please respond in newsgroup, NOT by private email ___

>

> Myweb <meiweb@gmx.de> wrote on 09 aug 2007 in

> microsoft.public.windows.terminal_services:

>

> > Hello duke,

> >

> > You have installed the Terminal server in Application mode i

> > think and after the trial period you have to install licenses

> > bought by MS. So 2 options, buy licenses for every user that has

> > to connect to the server or switch back to Administration mode

> > via add/remove programs windows components terminal server.

> >

> > Best regards

> >

> > Myweb

> > Disclaimer: This posting is provided "AS IS" with no warranties,

> > and confers no rights.

> >

> >> Windows Server 2003. Months ago when we got the server new, I

> >> was able to remote into it from my office. Cannot remember if

> >> I had to enable this on the server. Then I installed terminal

> >> server to try it out, and after playing around with it I took

> >> it back out because I was afraid it would cut me off from

> >> remote access after the trial ended. Now I can no longer remote

> >> in "The client could not connect to the remote computer".

> >>

> >> Is there something I have forgotten to reset?

>

[Guest Vera Noest [MVP]]

Re: no longer able to remote in to server

 

OK, then it's time for some troubleshooting questions:

 

* are there any errors or warning in the EventLog?

* is the Terminal Server service running?

* is the server listening on port 3389? You can check by running

the command "netstat -an" (without the quotes) on the console of

the server

* if the server is listening on port 3389, can you connect to the

server itself from the console of the server, with mstsc to

localhost?

_________________________________________________________

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?ZHVrZQ==?= <duke@discussions.microsoft.com> wrote on 10

aug 2007 in microsoft.public.windows.terminal_services:

> terminal server had been removed already and remote enabled...

> but same result.

>

> "Vera Noest [MVP]" wrote:

>

>> It's a bit unclear, but I take this statement:

>> >> .. after playing around with it I took it back out

>> to mean that the OP already uninstalled Terminal Services.

>>

>> If that is correct, then you have to re-enable Remote Desktop

>> for Administration, in Control Panel - System - Remote.

>> _________________________________________________________

>> Vera Noest

>> MCSE, CCEA, Microsoft MVP - Terminal Server

>> TS troubleshooting: http://ts.veranoest.net

>> ___ please respond in newsgroup, NOT by private email ___

>>

>> Myweb <meiweb@gmx.de> wrote on 09 aug 2007 in

>> microsoft.public.windows.terminal_services:

>>

>> > Hello duke,

>> >

>> > You have installed the Terminal server in Application mode i

>> > think and after the trial period you have to install licenses

>> > bought by MS. So 2 options, buy licenses for every user that

>> > has to connect to the server or switch back to Administration

>> > mode via add/remove programs windows components terminal

>> > server.

>> >

>> > Best regards

>> >

>> > Myweb

>> > Disclaimer: This posting is provided "AS IS" with no

>> > warranties, and confers no rights.

>> >

>> >> Windows Server 2003. Months ago when we got the server new,

>> >> I was able to remote into it from my office. Cannot

>> >> remember if I had to enable this on the server. Then I

>> >> installed terminal server to try it out, and after playing

>> >> around with it I took it back out because I was afraid it

>> >> would cut me off from remote access after the trial ended.

>> >> Now I can no longer remote in "The client could not connect

>> >> to the remote computer".

>> >>

>> >> Is there something I have forgotten to reset?

[Guest duke]

Re: no longer able to remote in to server

 

that was it. Uninstalling the terminal server disabled the terminal services

service. Re-enabled it and now I'm back. Thanks for your help

 

"Vera Noest [MVP]" wrote:

> OK, then it's time for some troubleshooting questions:

>

> * are there any errors or warning in the EventLog?

> * is the Terminal Server service running?

> * is the server listening on port 3389? You can check by running

> the command "netstat -an" (without the quotes) on the console of

> the server

> * if the server is listening on port 3389, can you connect to the

> server itself from the console of the server, with mstsc to

> localhost?

> _________________________________________________________

> 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?ZHVrZQ==?= <duke@discussions.microsoft.com> wrote on 10

> aug 2007 in microsoft.public.windows.terminal_services:

>

> > terminal server had been removed already and remote enabled...

> > but same result.

> >

> > "Vera Noest [MVP]" wrote:

> >

> >> It's a bit unclear, but I take this statement:

> >> >> .. after playing around with it I took it back out

> >> to mean that the OP already uninstalled Terminal Services.

> >>

> >> If that is correct, then you have to re-enable Remote Desktop

> >> for Administration, in Control Panel - System - Remote.

> >> _________________________________________________________

> >> Vera Noest

> >> MCSE, CCEA, Microsoft MVP - Terminal Server

> >> TS troubleshooting: http://ts.veranoest.net

> >> ___ please respond in newsgroup, NOT by private email ___

> >>

> >> Myweb <meiweb@gmx.de> wrote on 09 aug 2007 in

> >> microsoft.public.windows.terminal_services:

> >>

> >> > Hello duke,

> >> >

> >> > You have installed the Terminal server in Application mode i

> >> > think and after the trial period you have to install licenses

> >> > bought by MS. So 2 options, buy licenses for every user that

> >> > has to connect to the server or switch back to Administration

> >> > mode via add/remove programs windows components terminal

> >> > server.

> >> >

> >> > Best regards

> >> >

> >> > Myweb

> >> > Disclaimer: This posting is provided "AS IS" with no

> >> > warranties, and confers no rights.

> >> >

> >> >> Windows Server 2003. Months ago when we got the server new,

> >> >> I was able to remote into it from my office. Cannot

> >> >> remember if I had to enable this on the server. Then I

> >> >> installed terminal server to try it out, and after playing

> >> >> around with it I took it back out because I was afraid it

> >> >> would cut me off from remote access after the trial ended.

> >> >> Now I can no longer remote in "The client could not connect

> >> >> to the remote computer".

> >> >>

> >> >> Is there something I have forgotten to reset?

>

[Guest Vera Noest [MVP]]

Re: no longer able to remote in to server

 

You're welcome, Duke. I'm glad that your problem is solved, and

thanks for reporting back here!

_________________________________________________________

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?ZHVrZQ==?= <duke@discussions.microsoft.com> wrote on 10

aug 2007 in microsoft.public.windows.terminal_services:

> that was it. Uninstalling the terminal server disabled the

> terminal services service. Re-enabled it and now I'm back.

> Thanks for your help

>

> "Vera Noest [MVP]" wrote:

>

>> OK, then it's time for some troubleshooting questions:

>>

>> * are there any errors or warning in the EventLog?

>> * is the Terminal Server service running?

>> * is the server listening on port 3389? You can check by

>> running the command "netstat -an" (without the quotes) on the

>> console of the server

>> * if the server is listening on port 3389, can you connect to

>> the server itself from the console of the server, with mstsc to

>> localhost?

>> _________________________________________________________

>> 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?ZHVrZQ==?= <duke@discussions.microsoft.com> wrote on

>> 10 aug 2007 in microsoft.public.windows.terminal_services:

>>

>> > terminal server had been removed already and remote

>> > enabled... but same result.

>> >

>> > "Vera Noest [MVP]" wrote:

>> >

>> >> It's a bit unclear, but I take this statement:

>> >> >> .. after playing around with it I took it back out

>> >> to mean that the OP already uninstalled Terminal Services.

>> >>

>> >> If that is correct, then you have to re-enable Remote

>> >> Desktop for Administration, in Control Panel - System -

>> >> Remote.

>> >> _________________________________________________________

>> >> Vera Noest

>> >> MCSE, CCEA, Microsoft MVP - Terminal Server

>> >> TS troubleshooting: http://ts.veranoest.net

>> >> ___ please respond in newsgroup, NOT by private email ___

>> >>

>> >> Myweb <meiweb@gmx.de> wrote on 09 aug 2007 in

>> >> microsoft.public.windows.terminal_services:

>> >>

>> >> > Hello duke,

>> >> >

>> >> > You have installed the Terminal server in Application mode

>> >> > i think and after the trial period you have to install

>> >> > licenses bought by MS. So 2 options, buy licenses for

>> >> > every user that has to connect to the server or switch

>> >> > back to Administration mode via add/remove programs

>> >> > windows components terminal server.

>> >> >

>> >> > Best regards

>> >> >

>> >> > Myweb

>> >> > Disclaimer: This posting is provided "AS IS" with no

>> >> > warranties, and confers no rights.

>> >> >

>> >> >> Windows Server 2003. Months ago when we got the server

>> >> >> new, I was able to remote into it from my office. Cannot

>> >> >> remember if I had to enable this on the server. Then I

>> >> >> installed terminal server to try it out, and after

>> >> >> playing around with it I took it back out because I was

>> >> >> afraid it would cut me off from remote access after the

>> >> >> trial ended. Now I can no longer remote in "The client

>> >> >> could not connect to the remote computer".

>> >> >>

>> >> >> Is there something I have forgotten to reset?