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

    • Par for the course. I asked a question a few days ago and was threatened to be reported. 😂
    • Ummmm Are you kidding? Do think these books being sold are disclosing they are AI written?
    • i'm just commenting because of this madness. you simply asked "what crowd" which i too am genuinely curious about, only to receive a response in the form of a link that directs to an analysis of the audited financial statements with the accompanying notes. then you say that the guy who wrote it is stupid, which whatever, that's not an argument being discussed atm, only to receive a response from Arceles saying "i don't deal with people whose first response is an ad homenim". jesus. this is like making a claim, and then saying "i don't deal with people who speak in a certain way or swear so i'm not gonna answer you hah!" (said in a nasaly voice, not trying to depict you Arceles). then focus on the argument instead of the explanation begins... "so what don't you like about the guy (lunduke)" followed by "he just likes to insult people" and the explanation for the "crowd" being referred to was never even established. so a request for an explanation about the crowd turned into an argument about "why do you think lunduke is an idiot". wowza.
    • Sony lays off 30% of staff from Days Gone developer Bend Studio by Pulasthi Ariyasinghe Another wave of layoffs has hit the game developer space, and this time, it's a first-party Sony studio that's been affected. Following a report by Bloomberg's Jason Schreier, Bend Studio has confirmed that it is letting go of "incredibly talented teammates" as it begins work on a new game project. "Today, we said goodbye to some incredibly talented teammates as we transition to our next project," said Bend Studio in a social media post today. "We're deeply thankful for their contributions as they've shaped who we are, and their impact will always be part of our story." Bend Studio is most well-known for its 2019-released open-world zombie adventure Days Gone, which even received a remaster just a few months ago. Prior to that, the studio had been responsible for the classic Syphon Filter series while also developing several PlayStation Portable and Vita games like Resistance: Retribution and Uncharted: Golden Abyss, respectively. "This is a difficult moment for our team, but we hold immense respect for everyone who got us here," the company added. "As we move forward, we remain committed to building the future of Bend Studio with creativity, passion, and innovation in the titles we craft." While Sony did not detail just how many staff have been affected by this latest decision, Jason Schreier revealed that 30% of the studio is being laid off. This amounts to around 40 people, according to the reporter. Earlier this year, Sony canceled two live service games that were in development at Bend Studio and Bluepoint Games. It was never revealed what this mystery game was supposed to be. "Bend and Bluepoint are highly accomplished teams who are valued members of the PlayStation Studios family," Sony said at the time. It's unclear if Bluepoint, which had been developing a God of War live service experience, will soon be hit by its own wave of layoffs too.
    • KataLib 4.5.3.0 by Razvan Serea KataLib is more than just a music player — it's a complete audio suite designed for music lovers and creators alike. It combines a powerful audio player, a flexible metadata editor, a capable audio converter, and a music library manager into one streamlined application. Core Features: Audio Player Enjoy seamless playback of virtually any audio format or even streaming video files. DJ Mode lets you mix tracks with manual or automatic crossfades. You can also load and save WinAmp-style playlists for quick access to your favorite sets. Audio Converter Convert between a wide range of audio formats effortlessly. Trim or normalize your output automatically, and even extract audio from streaming video sources. Ideal for preparing files for different devices or platforms. Metadata Editor View and edit ID3v2 tags and other metadata. Batch edit multiple files at once, and fetch missing information directly from the MusicBrainz database. You can also apply or update album art with ease. Music Library Manager Organize your entire audio collection, search across tracks instantly, and download cover images from the internet — or use your own custom artwork. KataLib makes it easy to keep your library tidy and enriched with useful info. Supported Formats: KataLib supports a wide range of both lossy and lossless audio formats: Input: OPUS, AAC, FLAC, M4A, MP3, MP4, MPC, APE, AIF, MKV, AVI, MOV, FLV, WEBM, Ogg Vorbis, WAV, WAVPack, WMA Output: OPUS, FLAC, M4A, MP3, Ogg Vorbis, WAV Under the hood, KataLib uses the trusted FFmpeg engine for audio conversion and media playback, ensuring compatibility with virtually all mainstream media formats. Download: KataLib 4.5.3.0 | 64.5 MB (Open Source) Links: KataLib Home Page | Github | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
  • Recent Achievements

    • First Post
      K Dorman earned a badge
      First Post
    • Reacting Well
      rshit earned a badge
      Reacting Well
    • Reacting Well
      Alan- earned a badge
      Reacting Well
    • Week One Done
      IAMFLUXX earned a badge
      Week One Done
    • One Month Later
      Æhund earned a badge
      One Month Later
  • Popular Contributors

    1. 1
      +primortal
      545
    2. 2
      ATLien_0
      268
    3. 3
      +FloatingFatMan
      207
    4. 4
      +Edouard
      201
    5. 5
      snowy owl
      139
  • Tell a friend

    Love Neowin? Tell a friend!