06-17-2015 04:30 AM - edited 03-05-2019 01:41 AM
Hi
i work in a company and i have to change a modem router f@st 3304 by cisco c887w
i put this configuration in the cisco router and i can navigate to internet when im directly connected to the C887w
but when i put it with the firwall fortigate i can't navigate from the inside
----dialer0-C887W-(192.168.1.1)-------192.168.1.50 PC ITWORKS
---dialer0-C887W--(192.168.1.1)-----192.168.1.50-Fortigate-10.10.10.2-----10.10.10.4-TMG-172.16.0.1------172.16.1.2-PC Doesn't work
here is my config
Solved! Go to Solution.
06-19-2015 11:57 AM
Hi,
If Fortigate is natting and there is a permit policy then everything should be working.
You should be able to ping 8.8.8.8 from a PC in the inside interface of the Fortigate.
If you can do this but can't ping www.google.com then indeed you have a DNS problem.
Is the Fortigate the DHCP server for inside machines ? If so what are the dns servers they are getting from dhcp ?
Regards,
Alain
06-18-2015 01:28 PM
Hi,
Are you natting on the Fortigate ? if not then the traffic from inside interface of fortigate won't be natted on the Cisco router and won't get routed on the Internet.
You could edit your ACL 101 to permit this ip subnet too.
You'll also have to put a static route towards this subnet on the Cisco router pointing towards the Fortigate.
Also on the Fortigate you have to create a policy for permitting traffic from inside to outside.
Regards,
Alain
06-19-2015 03:29 AM
Yes the fortigate is Natting outgoing trafic
In this case shall i add the static route ? or not ?
Yes in th fortigate there is a policy which allow trafic to go from the inside to outside actually theere is a Sagem modem router which is working fine with the fortigate and i want to replace this sagem router by the cisco c887
Can you explain please how i must configure the policy?
Best regards and thanks again.
06-19-2015 11:57 AM
Hi,
If Fortigate is natting and there is a permit policy then everything should be working.
You should be able to ping 8.8.8.8 from a PC in the inside interface of the Fortigate.
If you can do this but can't ping www.google.com then indeed you have a DNS problem.
Is the Fortigate the DHCP server for inside machines ? If so what are the dns servers they are getting from dhcp ?
Regards,
Alain
06-19-2015 04:00 PM
Hi Alain
C887----Fortigate----TMG----PC
before the fortigate there is a TMG proxy which is the gatway and this TMG is natting also the trafic.
the machines take IP from windows DHCP server behind the TMG and there is a windows DNS server behind the TMG
I will test the ping and navigation to give you the results about DNS.
thank you Alain
06-22-2015 02:46 PM
Hi
I'm finaly connected to the internet from the inside but still have slow connection any suggestions ?
06-24-2015 11:22 AM
Hi,
Are you doing webfiltering or application control on the Fortigate ?
What happens if you take out the Proxy out of the equation ?
Regards,
Alain
06-19-2015 05:13 AM
i think i have a DNS problem when i connect the cisco router with the fortigate
06-19-2015 02:58 AM
Yes the fortigate is Natting outgoing trafic
In this case shall i add the static route ? or not ?
Yes in th fortigate there is a policy which allow trafic to go from the inside to outside actually theere is a Sagem modem router which is working fine with the fortigate and i want to replace this sagem router by the cisco c887
Can you explain please how i must configure the policy?
Best regards and thanks again.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide