GSA issue access on prem services

Kieran Mckay 0 Reputation points
2025-01-16T09:42:37.8466667+00:00

Had an issue since last night, GSA logs showing traffic to on prem resources e.g RDP SMB but not loading. Not an issue with one user, issue with all

Microsoft Entra Private Access
Microsoft Entra Private Access
Microsoft Entra Private Access provides secure and deep identity-aware, Zero Trust network access to all private apps and resources.
77 questions
{count} votes

1 answer

Sort by: Most helpful
  1. Janaki Kota 230 Reputation points Microsoft Vendor
    2025-01-22T12:51:09.01+00:00

    Hello @Kieran Mckay,

    We understand that you're experiencing an issue where GSA logs show traffic to on-prem resources like RDP and SMB, but the traffic fails to load. 

    To simplify troubleshooting, if you know the target IPs and ports that your app should be connecting to, you can filter the logs by these parameters to remove irrelevant traffic. For instance, if you're troubleshooting RDP connections, you could filter by "Destination Port == 3389." If you're unsure of the destination IPs or ports, you can filter by the process name, such as "mstsc.exe" for RDP traffic. 

    Some applications may require connectivity to multiple services with various destination IPs, ports, or protocols (TCP or UDP). It’s common to encounter scenarios where application traffic is being tunneled via segments (defined under Forwarding Profiles) but some destinations may be missed. If you know the application’s process name, you can filter by it and remove the default Action==Tunnel filter. This will help you identify any traffic the app is attempting to send that is being overlooked by the current rules. 

    For example, by removing the default Action==Tunnel filter, adding a process name filter, and reproducing the issue, you might notice that mstsc.exe tries to connect to the RDP server on port 3389/UDP. However, the GSA client might determine that this traffic should be bypassed because it doesn’t match a forwarding profile rule. In some cases, missing traffic can be harder to detect because the connection is initiated by a process other than the application itself.  

    Sharing relevant documents for more information: https://microsoft.github.io/GlobalSecureAccess/Troubleshooting/WindowsClientTroubleshooting/#packets-not-seen-by-the-gsa-client

    https://learn.microsoft.com/en-us/entra/global-secure-access/troubleshoot-global-secure-access-client-advanced-diagnostics

    Hope this helps. Do let us know if you any further queries.

    Thanks & Regards

    Janaki Kota


    If this answers your query, do click Accept Answer and Yes for was this answer helpful. And, if you have any further query do let us know.

    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.