Skip to main content
ATOON
New Member
June 14, 2024
Solved

Assistance to allow external access to your IIS server

Hi,

 

Assistance with a network configuration. We have an application on a local server (IIS) and need access to it from the external network:

I try the below steps with no luck, can't access it from an external network

 

* DDNS:

  • Created account and host on no-ip
  • Configure no-ip client on the server and connected

* On Firewall:

1- Configure Virtual IPs (External IP address/range: 0.0.0.0, Mapped IP address/range: LAN IP)

     Port Forwarding Protocol (TCP), External service port & Map to port (80)

2- Create Policy

  • Incoming Interface (WAN)
  • Outgoing Interface (LAN)
  • Source (all)
  • Destination (VIP) created earlier
  • Schedule (Always)
  • Service (HTTP)
  • Action (Accepted)
  • NAT (Disable) and try (Enable)

Additionally, configure Windows firewall inbound and outbound for port 80

 

Modem: FortiWiFi 30E

Firmware: v6.2.15 build1378 (GA)

Hong_FTNT
Hong_FTNTAnswer
Staff & Editor
June 14, 2024

Hi @ATOON.,

 

Please run the following debugs and test connection: 

 

di deb disable
di deb res
diagnose debug flow filter clear
di deb flow filter addr <source IP>
di deb flow filter port 80
diagnose debug flow show function-name enable
di deb flow show iprope en
diagnose debug console timestamp enable
diagnose debug flow trace start 9999
diagnose debug enable

 

Regards, 

10 replies

Hong_FTNT
Staff & Editor
Hong_FTNTAnswer
Staff & Editor
June 14, 2024

Hi @ATOON.,

 

Please run the following debugs and test connection: 

 

di deb disable
di deb res
diagnose debug flow filter clear
di deb flow filter addr <source IP>
di deb flow filter port 80
diagnose debug flow show function-name enable
di deb flow show iprope en
diagnose debug console timestamp enable
diagnose debug flow trace start 9999
diagnose debug enable

 

Regards, 

ATOON
ATOONAuthor
New Member
June 14, 2024

Please check the debug attached. Di debug 

Hong_FTNT
Staff & Editor
Staff & Editor
June 15, 2024

@ATOON,

 

From the debug output, the source IP 10.10.210.250 is not a public IP. Are you making an outbound connection from behind the FortiGate to the public IP of the Huawei router? Do you have port forwarding configured on the router to forward port 80 traffic to 192.168.8.2?

 

Regards,

sw2090
SuperUser
SuperUser
June 14, 2024

What WAN connection do you have on the FGT? If there is a router in front of the FGT this router also has to forward the traffic!

ATOON
ATOONAuthor
New Member
June 14, 2024

Have a Huawei router HG8245W5 in front of FGT, internal IP 192.168.8.1.

Make an interface in FGT for wan 192.168.8.2, and make the LAN interface as Vlans 10.10.xx.xx.

So, in the Huawei router, if try to add the internal host, the LAN IP of the local server 10.10.xx.xx is not accepted.

 

HW router.png

ede_pfau
SuperUser
SuperUser
June 14, 2024

How did you test? Using HTTP or by pinging? Ping won't work here.

ATOON
ATOONAuthor
New Member
June 14, 2024

Tested by HTTP browsing, and ping working fine

fdsantos
Staff
Staff
June 15, 2024

You may try to run a packet capture so that we may determine if the packets are reaching the FortiGate from your WAN interface.

 

I would recommend to do the packet capture using your client public IP address that is reaching the VIP.

 

You may follow the command below.


If you are accessing port 80:
diag sniff packet "host <client-public-ip-address> and port 80" 4 0 l

 

You may also check the documentation below in regards for packet capture.

 

https://docs.fortinet.com/document/fortigate/6.4.5/administration-guide/680228/performing-a-sniffer-trace-cli-and-packet-capture

Thought Leadership. Security Summit. Thursday, November 12th, PGA National Resort, Palm Beach Gardens, FL.
Thought Leadership. Security Summit. Thursday, October 8th. Disney's Grand Californian Hotel & SPA, Anaheim, CA.
Security Operations Summit: Modernize SecOps. Operate AI-Native.AMER: November 4 | 9:00 AM PST. India and SAARC: November 5 | 10:00 AM IST. EMEA: November 5 | 10:30 AM CET. APAC: November 5 | 11:00 AM SGT