- CheckMates
- :
- Products
- :
- General Topics
- :
- MUH2 seems to still be port based
Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
Are you a member of CheckMates?
×
Sign in with your Check Point UserCenter/PartnerMap account to access more great content and get a chance to win some Apple AirPods! If you don't have an account, create one now for free!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
MUH2 seems to still be port based
I installed the MUH2 terminal server agent (R80.219.0000) on a citrix server, and thought that it replaced the port-based approach for identifying users with a different approach (some sort of packet tagging per sk164998). However, when I look at the agent and the PDP, it appears that port ranges are still being assigned to each user. Is this expected? Or do I have to configure the agent differently?
Example:
2 Replies
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Are the gateways in question R80.40?
This is required for MUH2.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello,
MUHv1 is still active on your Citrix server. As I understand the documentation MUHv1 must be uninstalled, server rebooted, MUHv2 installed and rebooted again.
For MUHv2 Client Type should be Terminal Server Identity Agent v2 in pdp mon ip.
