So, by doing this, it will allow users to login to the cluster, but keep them from accessing individual servers?
Main Topics
Browse All TopicsWe run a Terminal Server farm with several servers clustered together. I have a problem of users logging into specific servers, rather than the cluster. Is there a way to prevent this, but still allowing them to login to the cluster?
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
No, it's all on a LAN. Maybe I could set up an internal firewall just for the LAN and point the workstations to it. I am mostly concerned with student computer labs. I could probably set up iptables to do this, if I were to change the IP scheme so the new rules only affected them. It surprises me there is not a a way to do this through windows 2003 server, through group policies, etc....
Once the user has a piece of information like a specific IP address and port/protocol, there's not much that can be done within windows. Unless you were to do something like create a "connection.rdp" with the specific settings you want them to use, and save it to a share on the server (then you'd only have to change it once if you want to change it). Then create a shortcut to that rdp file and push it out to the desktops (via login script or other method). Then forbid the users via GPO from launching the MSTSC.EXE directly... make them use your shortcut. (you could copy MSTSC.EXE and put it in the same share as the *.rdp file, apply the hidden attribute, then use a GPO software restriction policy to forbid access to %windir%\system32\MSTSC.ex
Remember to only allow the "apply group policy" permisison to the group of users you want to enforce this for, or the same policy will apply to you, and then you won't be able to use the RDPCLIENT normally either...
Hope this points you more in the direction you want to take.
(IP rules are probly easier to understand Lol..)
Business Accounts
Answer for Membership
by: nitadminPosted on 2006-10-13 at 22:01:02ID: 17729497
Yes you can do this by creating security group and then adding users to the group. Once you do this use the security group to deny them access to the specific servers you don't want them to have access.
NITADMIN