Forum Discussion
Deny RDP ACCESS
- Jan 15, 2016
Probably the easiest way to start trying to figure out what's different between different classes of users is:
Make the connection via method A.
Go view the user's session variables in BIG-IP GUI. Screenshot it or copy it someplace.
Make the connection via method B.
Go view the user's session variables again.
Make a note of the difference between how the two set up sessions.
Probably the easiest way to start trying to figure out what's different between different classes of users is:
Make the connection via method A.
Go view the user's session variables in BIG-IP GUI. Screenshot it or copy it someplace.
Make the connection via method B.
Go view the user's session variables again.
Make a note of the difference between how the two set up sessions.
- Carlos_Garibay_Jan 15, 2016Nimbostratusok when I connect to via webtop I see the session, but when I connect via regular mstsc I do not see a sessiong on the big Ip
- Lucas_Thompson_Jan 15, 2016Historic F5 AccountOK, perfect! In that case you'll have to simply block this using Windows Firewall or some other firewall. Only allow the RDP connections from APM's self IPs (you probably would include the floating self IP and both non-floating self IPs).
Recent Discussions
Related Content
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com