Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 2 replies
  • Subscribers 3 subscribers
  • Views 2996 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

RD Gateway Problems from IP V6 Internet Connections

Widde

Hello!

We use the WAF Feature of our Sophos UTM for a few months now to make our RD Gateway (Windows Server 2012 R2) accessible from the outside. It is working fine for Users on any Windows Client if they use the "old" RDP Client, but it is not working with the "new" Remotedesktop Windows App. So we just stick to the old RDP Client. No biggie. It was working OK.

Suddenly we have a new Problem at hand: The private Internet Access from some of our Workers was switched to IP V6 by their Internet Providers and now they can't connect anymore from home. Our Companys Internet Connection still has IP V4 only. So somewhere there has to be a Translation between IPV6 and IPV4 and i think maybe that is causing some trouble here? Has someone experienced something like this? Any Idea where to start?



This thread was automatically locked due to age.
  • 0

    Normaly such translation service is provided by the internet provider for outbound traffic. Maybe you could ask the remote worker to test his ipv4 connectivity, for example here

    Could not help with the other questions, but interessting problem.

    Alex

    -

  • 0 in reply to Alexander Busch

    Ja, we tested a little bit more and found out that older Windows 8.1 RDP Clients can succesfully make a RDP Connection from the same Home Network.

    So it must have something to do with the RDP Client under Windows 10 and the WAF on the Sophos. We are looking there right now. Windows 2012 R2 RD Gateway over WAF is a Little bit tricky as it seems.

Unfiltered HTML