Lock down Terminal Services

[Guest Larry]

I have a couple questions. Is there anyway to lock down Windows Server 2003

Terminal Services to a particular workstation so you can only RDP to the

server from that particular workstation? Second, is there anyway to add

Terminal Services to Windows NT other then upgrading to Terminal Services

addition? Thanks!

[Guest Vera Noest [MVP]]

Re: Lock down Terminal Services

 

That's not a built-in feature of TS.

Can you explain a bit more when and why you want to do this? What's

the idea with having a Terminal Server for a single client?

 

And no, you can't add TS to NT 4.0 other than by installing NT 4.0

Terminal Server Edition. You can install VNC on it though, which

doesn't make it a Terminal Server, but allows for administrative

access with a VNC client. There are lots of free VNC packages, search

on Google.

 

_________________________________________________________

Vera Noest

MCSE, CCEA, Microsoft MVP - Terminal Server

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

___ please respond in newsgroup, NOT by private email ___

 

"Larry" <lnelson33@hotmail.com> wrote on 14 feb 2008 in

microsoft.public.windows.terminal_services:

> I have a couple questions. Is there anyway to lock down Windows

> Server 2003 Terminal Services to a particular workstation so you

> can only RDP to the server from that particular workstation?

> Second, is there anyway to add Terminal Services to Windows NT

> other then upgrading to Terminal Services addition? Thanks!

[Guest Larry]

Re: Lock down Terminal Services

 

Thanks for the reply. Yea that's what I thought. I have used VNC on other

servers. One of the project managers here is very cautious about security.

Her employees have been begging her to allow RDP so they don't have to make

multiple trips to server room. She said she would do it if it could be

configured to only allow from one of their workstations in their locked up

lab to access it. Thanks again.

 

 

"Vera Noest [MVP]" <vera.noest@remove-this.hem.utfors.se> wrote in message

news:Xns9A44E4B19E98Dveranoesthemutforsse@207.46.248.16...

> That's not a built-in feature of TS.

> Can you explain a bit more when and why you want to do this? What's

> the idea with having a Terminal Server for a single client?

>

> And no, you can't add TS to NT 4.0 other than by installing NT 4.0

> Terminal Server Edition. You can install VNC on it though, which

> doesn't make it a Terminal Server, but allows for administrative

> access with a VNC client. There are lots of free VNC packages, search

> on Google.

>

> _________________________________________________________

> Vera Noest

> MCSE, CCEA, Microsoft MVP - Terminal Server

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

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

>

> "Larry" <lnelson33@hotmail.com> wrote on 14 feb 2008 in

> microsoft.public.windows.terminal_services:

>

>> I have a couple questions. Is there anyway to lock down Windows

>> Server 2003 Terminal Services to a particular workstation so you

>> can only RDP to the server from that particular workstation?

>> Second, is there anyway to add Terminal Services to Windows NT

>> other then upgrading to Terminal Services addition? Thanks!

[Guest Vera Noest [MVP]]

Re: Lock down Terminal Services

 

OK, so it's not a real Terminal Server, it just a normal server

with Remote Desktop for Administration enabled, is that correct?

 

I had almost forgotten it, but I have a FAQ which seems to solve

your problem :-)

 

How can I allow rdp connections from specific clients only?

http://ts.veranoest.net/ts_faq_connectivity.htm#filter_rdp_clients

 

_________________________________________________________

Vera Noest

MCSE, CCEA, Microsoft MVP - Terminal Server

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

___ please respond in newsgroup, NOT by private email ___

 

"Larry" <lnelson33@hotmail.com> wrote on 14 feb 2008 in

microsoft.public.windows.terminal_services:

> Thanks for the reply. Yea that's what I thought. I have used VNC

> on other servers. One of the project managers here is very

> cautious about security. Her employees have been begging her to

> allow RDP so they don't have to make multiple trips to server

> room. She said she would do it if it could be configured to only

> allow from one of their workstations in their locked up lab to

> access it. Thanks again.

>

>

> "Vera Noest [MVP]" <vera.noest@remove-this.hem.utfors.se> wrote

> in message

> news:Xns9A44E4B19E98Dveranoesthemutforsse@207.46.248.16...

>> That's not a built-in feature of TS.

>> Can you explain a bit more when and why you want to do this?

>> What's the idea with having a Terminal Server for a single

>> client?

>>

>> And no, you can't add TS to NT 4.0 other than by installing NT

>> 4.0 Terminal Server Edition. You can install VNC on it though,

>> which doesn't make it a Terminal Server, but allows for

>> administrative access with a VNC client. There are lots of free

>> VNC packages, search on Google.

>>

>> _________________________________________________________

>> Vera Noest

>> MCSE, CCEA, Microsoft MVP - Terminal Server

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

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

>>

>> "Larry" <lnelson33@hotmail.com> wrote on 14 feb 2008 in

>> microsoft.public.windows.terminal_services:

>>

>>> I have a couple questions. Is there anyway to lock down

>>> Windows Server 2003 Terminal Services to a particular

>>> workstation so you can only RDP to the server from that

>>> particular workstation? Second, is there anyway to add

>>> Terminal Services to Windows NT other then upgrading to

>>> Terminal Services addition? Thanks!