Port forward to RDP

[Nuur]

Hello all,

Basicly I installed Forticlient-VM and Windows Server 2022 on Hyper-V.

Everything seems to work Ok except port forward.

This is how I set up th VIP

Interface = any (also tried WAN)
Type = Static NAT
External IP address/range = WAN 192.168.1.253 (Also tried 0.0.0.0)
Map to IPv4 address/range = Server ip 192.168.5.10 - LAN network
Port Forwarding = ON
Protocol = TCP
Port Mapping Type = One to one
External service port = 3389
Map to IPv4 port = 3389

I have also created firewall policy

Can any help me with any kind of a solut

[carlosaleman]

Hello, have you verified the procedure described in this article?

https://community.fortinet.com/t5/FortiGate/Technical-Tip-Use-RDP-via-VIP/ta-p/210093

[Nuur]

I will try this later today.

I'll let you know.

Thanks

[Hosemacht]

Dear Nuur,

in your policy you have set both the incoming and outgoint Interface to "Wan (Port1)"

usually you have to set the lan facing interface on the outgoing site

maybe this could be the problem here.

[Nuur]

Hi Hosemacht,

I have tried that. Unfortunately not the solution

Thanks though

[msanjaypadma]

Hi @Nuur ,

If you are sure about incoming interface port1 and outgoing interface port2 , then configuration look fine.

You might have to check debug logs to understand the exact issue. 

get router info routing detail 192.168.1.253 
get router info routing detail 192.168.5.10
get router info routing detail <source>

show sys interface port1
show sys interface port2

diag debug reset
diag debug disable
diag debug flow filter clear
diag debug flow filter addr x.x.x.x <--- source ip address
diag debug flow show iprope enable
diag debug flow show function-name enable
diag debug console timestamp enable
diag debug flow trace start 9999
diag debug enable

generate the traffic from source ip address x.x.x.x and once get the error in the connection , then stop the debug using below commands.
diag deb disable
diag deb reset

Hope you will be able to see logs and it will tell you the exact issue.

Thanks,

[pmeet]

Hello @Nuur ,

From what IP does a user tries to RDP into the internal PC, is the IP used from the external user is public IP or it's the IP 192.168.1.253  , if its public IP please use 0.0.0.0 in external IP,

Also please disable the NAT in the firewall policy,

Let us know if that does not helps.

[Nuur]

Hi pmeet,

it's not working with 0.0.0.0 as the external ip 

[mle2802]

Hi @Nuur,

Is 192.168.1.253 your interface of port 1? Are you connecting from inside or outside of your network and from where you connect, is it routable to 192.168.1.253? Also tried to remove the VIP from policy and change interface binding to port1.

Regards,
Minh

[Nuur]

I am connecting from outside to 192.168.1.253.

I removed the NAT but stil not working 

is it routable to 192.168.1.253?

I configured static routes if you mean that