Thread Info
  • State Verified Answer
  • +1 person also asked this people also asked this
  • Locked Locked
  • Replies 6 replies
  • Subscribers 6 subscribers
  • Views 5042 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

Cannot RDP from non-domain to domain computer through RED 15

TomMorgan

 SG230 UTM 9.510-5

I have currently have 3 RED 15s deployed with standard-split tunnels that are all functioning properly. They are used for server file access and RDP.

I recently deployed a 4th RED 15 with absolutely identical configs to the other three. The only one difference is that the remote computer (behind RED) is not a domain computer. The user can access the server files and map a drive but cannot connect to their domain desktop via RDP.

Using nslookup from the remote (non-domain) computer, the domain computer is identified with it's name/IP, but pinging the domain computer name and IP fail. RDP fails with "cannot find computer on this network...". Sophos software VPN client works perfectly (but dreadfully slow).

I tried both the DNS name and IP address in RDP but get the same result.

Is this related to non-domain->domain authentication or could there be an underlying DNS issue I am missing?

Thanks!



This thread was automatically locked due to age.
Parents Reply Children
  • 0 in reply to Badrobot

    Yes thank you. The user/employee is connecting FROM his non-domain box at home, through a RED, TO his domain box at work. So he already had permissions logging in as himself in RDP. In fact, he could RDP successfully using the UTM provided software VPN, but not through the RED. Sophos confirmed that something in the RED was disallowing (or not finding) the network device.

  • +1 in reply to TomMorgan

    This issue was not resolved with my last post since, unknown to me, the employee was still using the Sophos software VPN after I deployed the new RED. Upon discovery of that, I found that the new RED was still unable to make the RDP connection.

    With the help of Sophos support, it was found that the remote computer was not able to respond back to the RED network. The solution?? Add a route to the remote computer:

    route -p ADD [RED subnet] MASK [RED netmask] [remote network gateway]

    route -p ADD 192.168.10.0 MASK 255.255.255.0 192.168.50.1

    BOOM! Instant connection to RDP.