NO NAT not working

[Gagandeep]

We are using Public IP range as a Source segment to access Internet and we also using NO NAT option to disable the NATING and Secondly we are able to telnet and trace the Google and other Websites. Post Creating the ACL with NO NAT option, we observed Internet is not working and secondly whenever we do Default NAT with FW outside interface IP, Internet working fine on Problematic Source Segment (Public IP) but without NAT internet not working as above mentioned. Note: - Internet is working fine on another Source Segment (Public IP) from last many months. Please assist

[rwpatterson]

This sounds more like a problem with your ISP not the Fortigate. Since you cannot have that ' public' segment on both router interfaces, your ISP may not be passing the public subnet through back to you.

[Gagandeep]

Thanks for the response. But We aready using the Public IP as an Source and Internet is working fine but we got new Public IP range to configure the same ACL in FW but issue only with new ACL and old one is working fine from last 7-8 months.

[pchechani_FTNT]

For the New Source Segment ISP has to configure same back route as they have configured for the old public subnet segment. To know the ISP router where to route the packet for your subnet.

[Gagandeep]

Thanks for assistance Let me check as suggested and also let me know if any other possiblity which I can check to fix this issue.

[Gagandeep]

I have checked and got confirmation that Routing for New Pulic Segment is same as for OLD Public Segment. Please assist other possiblities to check this issue

[pchechani_FTNT]

It will be better if you post your configuration little bit which helps understand the problem clearly. If we are not using the NAT, then you have to create two policy, one inbound and one outbound. this is called route mode nat in fortigate http://docs.fortinet.com/fos40hlp/43/wwhelp/wwhimpl/js/html/wwhelp.htm just create simple fw policy from inbound to outbound interface and outbund to inbound.