Skip to main content
Contributor III
March 31, 2006
Question

Help? Remote Desktop over forticlient

  • March 31, 2006
  • 9 replies
  • 5070 views
Hi, I have setup a connection to a PC in the network ... Home--> over forticlient --> Internet --> fortigate60 --> 10.0.0.x Now I want to establish a remote desktop connection to that pc.. How do I do that?

    9 replies

    Contributor III
    March 31, 2006
    If everything is set up properly, all you need to do is open the remote desktop client and point it to the IP address.
    Contributor III
    March 31, 2006
    You are probably having a similiar issue that I am having. Look to see if you have a gateway on your vpn connection. I dont have one when I do IPCONFIG. I am trying to use VNC over a VPN tunnel.
    isptools
    New Member
    March 31, 2006
    first of all: can you ping the server (the internal server-ip) ? If yes you should also be open it via RDP if no look at the default-gw on booth sides. Michael
    Contributor III
    March 31, 2006
    Unfortunatly I cant ping anything. how come? when I have a connection over the forticlient? what could I be doing wrong. My other thread with the vpn config is here: http://support.fortinet.com/forum/tm.asp?m=16644&p=1&tmode=1&smode=1
    Contributor III
    April 1, 2006
    Bear in mind there are two ways to succesfully connect a forticlient to the fortigate. One is with an IP adress of the internal subnet on the client and inbound NAT. The second (more preferred) is to define a VPN subnet, and define a IP in the client in that VPN subnet range. (no NAT in the firewall rule!!!) In the first case you can' t rdesktop to the FC, the second case you can. (if ofcourse the FW rule allows you to) Cheers, Eric
    Contributor III
    April 1, 2006
    thank you for this advice, but can you or someone else also tell me how to do this? somehow i just can' t ping anything in the network, even thou I am connected (according to forticlient and the monitor in the fortigate60) so if I can' t ping, than I am connected, but not in the network...
    Contributor III
    April 2, 2006
    Just made a comment on the other thread you' ve opened, let' s close this and go further in the other.
    Contributor III
    April 7, 2006
    Apparently, the SA has been defined but no FW rules match the tunnel and allow traffic on it.
    Contributor III
    April 13, 2006
    Yes i agree about that, apply the firewall rule enable TCP 3389 services and allow to internal network. Regards Albert Hui
    Thought Leadership Security Summit. Outpace New Threats with AI - enhanced defense. Tuesday, Septmeber 15, 8:30 AM - 2:30 PM PT. The Golf Club at Newcastle, WA.
    Virtual event | September 2026. SASE summit. The age of autonomous trust. Register here!