Limit RDP connections for certain user groups to IP


Recommended Posts

I have a win 2003 standard edition server running as a web server, with Remote Desktop to admin it. I also have a static IP address at this end.

I know I can IPSec ALL Remote Desktop connections to a set IP address, but can I somehow limit administrator groups to my static IP address, but allow a standard user to connect from any IP address?

Thanks in advance.

huh?

You can control who has access to remote desktop by group or user account. The builtin administrators group has permissions by default, but you can add other groups or users that you want to be able to remote desktop.

As to IPSec all remote desktop connections?? :blink:

You can modify your IP security policies with secpol.msc, you can create IP filters there as well -- is this what your asking?

Edited by BudMan
  tiddlie said:
No - I want to limit the access to remote desktop via remote IP address. I want only my static IP to be allowed to login via a user in the administrator group, but a 'standard' user to have access from any IP address.
This makes NO sense.. So your allowing users from any IP access.. Then all IPs have access.

Sorry but that tool controls access to the PORT 3389, it does not say oh your from IP address X you can login as a USER, but not as an Admin User.

Oh your from IP Y, you can login as Admin.

"Logon screen is only displayed if the connection is established from particular IPs or machines. Computers that do not meet the filter restrictions don't see the logon screen & won't get to try a brute force logon!"

Since your allowing any IP to use remote desktop.. Then any IP will get the login screen -- an if they have a valid user account that can remote desktop, then they can log in.

Here are the filters you can use from that tool;

--

This is the main SecureRDP page. It includes several filters that can be combined to create very complex conditions that must be met in order to be able to logon to your Terminal Server. These filters include:

IP Address: restricts the connection by checking the client IP Address.

Computer Name: restricts the connection by checking the client computer name.

MAC address: restricts the connection by checking the client PC MAC address. Note that this filter works only for computers on the same subnet as your Terminal Server.

Client Version: restricts the connection by checking the Terminal Services Client version. To make this filter more effective you should be using a customized Terminal Services Client with your own version number. This service is available in our website at http://www.terminal-services.NET.

Time Restriction: restricts the connection by checking the logon date and time.

--

What he is asking does not even make any sense to do anyway.. Users that are NOT admin should really not even have remote desktop access to a server. But since your going to allow them access -- yes if they knew the admin password, they would be able to login as an admin. Even if you blocked their remote desktop login - they could just login as a user, then run whatever they wanted as the admin account.

Edited by BudMan

Agreed -- an than can be done with a simple IP security filter using secpol, or your firewall, etc.

No need for the tool -- its pretty much just a gui that puts some settings all in the same place for people that do not now how to use their own OS ;)

Well, I have no direct access to the server. Obviously, leaving RDP open to all IP addresses is a real problem - goes without saying. Hence why I want to limit the admin access to my static IP address.

I do however, work away from time to time, and only have access to the internet via a laptop on a public or hotel lan. Should I need to access the server whilst away to do a simple task such as edit the php.ini file, or reboot IIS, it would be handy to have a somewhat locked down account that allows me these limited functions. Obviously, this needs to be accessed from a public IP addess.

If this is a roundabout way to do it - hey - we all learn, and advice is always appreciated.

And surely Windows 2003 fits into your description of that tool Budman....a 'gui that puts some settings all in the same place' - 2003 seems to be entierly made up of wizards.....

They have had wizards since the first version of windows -- does not mean you have to use them ;)

An I agree -- I would never open up RDP to the public NET.

You should access it thru a VPN or SSH/SSL tunnel, etc. This allows you to move around, just setup TLS auth to the server -- just keep your cert with you. Be it auth to the VPN/SSL or Remote Desktop or private key access to the SSH server.

This prevents bruteforce attacks, an allows you access from anywhere on the planet.

http://technet2.microsoft.com/windowsserve...3.mspx?mfr=true

Configuring authentication and encryption

http://support.microsoft.com/kb/895433

How to configure a Windows Server 2003 terminal server to use TLS for server authentication

For example -- you can only access my home network with OPENVPN or SSH, I keep my keys on my thumbdrive -- so I can access all of my machines from anywhere on the planet either with just putty an tunnel anything I need or with the openvpn client -- an again all services are open to me just as if I was on the local lan -- just a bit slower ;)

Putting up any type of service that only requires a password to access is just asking for trouble!

edit: BTW the IP an or fqdn to access my server along with the cert/key passwords are in my head -- so even if I loose the thumb drive -- the finder does not have access to anything.

Edited by BudMan
This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • Meta says that its "Private Processing technology" will be used. Oh, thank God! Now, I will finally sleep a whole lot better at night trusting FB. 🙄🙄🙄
    • The Teams Admin center is still a mess. I use it all the time. They really need to talk with the Intune or Entra ID folks for help.
    • Senua's Saga: Hellblade II to get 60FPS mode, dev commentary, and more alongside PS5 launch by Pulasthi Ariyasinghe Back in May, Microsoft revealed Senua's Saga: Hellblade II as the next first-party Xbox game to reach PlayStation platforms. Now, that release has an official release date attached to it, and alongside it, developer Ninja Theory is releasing an update across all platforms with some major features, including a 60 FPS mode on consoles. The Performance Mode is easily the biggest addition to the story-focused immersive experience. Ninja Theory is delivering it to both Xbox Series X and PlayStation 5 players, but there is some bad news for Series S owners, as it is being left out from the upgrade. "The result is smoother gameplay, especially noticeable during combat and fast-moving moments of the game," says the developer. It's unclear how much of the game's visuals Performance Mode users will be missing out on compared to the default 30FPS "cinematic" mode. PC players are getting an upgrade too. A Very High preset is being added to the settings menu for those wanting even higher fidelity graphics. Optimizations have also been a focus on PC, and Ninja Theory says that the title will be Steam Deck Verified when the Enhanced update lands in August. Next, similar to the original, Dark Rot is incoming as an optional experience that players can enable when starting a campaign. This will have a rot effect being applied to Senua every time she dies, and if it ever reaches her head, the game will come to an end, with all progress from that save being wiped. The Photo Mode in Hellblade II is being upgraded with this update too, with the studio touting a new Motion tab for cinematic video capture, as well as improvements across the board to the feature. Lastly, four hours of developer commentary is being added to give a behind-the-scenes look at how the studio crafted the story and gameplay. "Hear from the ensemble cast, key collaborators in depicting Senua’s experience of psychosis, and members of the development team who poured their heart and soul into Senua’s story," says the studio. The Senua’s Saga: Hellblade II Enhanced comes out on August 12 across PC, Xbox Series X|S, and PlayStation 5 for all owners and Game Pass subscribers as a free upgrade. As for the PlayStation 5 launch of Senua’s Saga: Hellblade II that's happening on the same day, Microsoft will be offering two versions: Standard and Deluxe. As expected, Standard includes the complete base game for $49.99, but Deluxe goes further by adding on a copy of the first game, Hellblade: Senua’s Sacrifice, as well as its original soundtrack. The Deluxe Edition costs $69.99 to purchase.
    • Not sure what you’re talking about. Has been there for quite a while and in the latest versions it’s actually quite good. I use it several times a day as I am a terrible typist.
  • Recent Achievements

    • Rising Star
      Phillip0web went up a rank
      Rising Star
    • One Month Later
      Epaminombas earned a badge
      One Month Later
    • One Year In
      Bert Fershner earned a badge
      One Year In
    • Reacting Well
      ChrisOdinUK earned a badge
      Reacting Well
    • One Year In
      Steviant earned a badge
      One Year In
  • Popular Contributors

    1. 1
      +primortal
      549
    2. 2
      ATLien_0
      207
    3. 3
      +FloatingFatMan
      172
    4. 4
      Michael Scrip
      152
    5. 5
      Som
      139
  • Tell a friend

    Love Neowin? Tell a friend!