Support Forum
The Forums are a place to find answers on a range of Fortinet products from peers and product experts.
Yosef
New Contributor

cannot connect from lan to other lan

hi in my fortigate i have lan ports that are connected like this : internal1 :192.168.0.61/255.255.252.0 internal2 :192.168.7.61/255.255.255.0 internal3 :192.168.4.61/255.255.255.0 and the wan like this : wan1 :215.215.2.165/255.255.255.255

internal1 is the local servers port

in the policy i created policies to connect each lan internal to internal1 and to wan 1 when i am trying to connect from internal 3 to internet and to servers everything work correctly as shown in tracnet command cmd:

C:\Users\student>tracert 192.168.0.1

[size="1"]Tracing route to a-server.ba.local [192.168.0.1][/size] over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.4.61 [size="1"] 2 <1 ms <1 ms <1 ms a-server.ba.local [192.168.0.1][/size]

Trace complete.

C:\Users\student>tracert www.google.co.il

[size="1"]Tracing route to www.google.co.il [213.151.35.143][/size] over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.4.61 [size="1"] 2 17 ms 16 ms 16 ms mx-lns-01.neto.net.il [213.151.32.237][/size] 3 16 ms 16 ms 16 ms 10.17.50.1 4 16 ms 16 ms 36 ms 213.151.32.188 [size="1"] 5 16 ms 16 ms 16 ms cache.google.com [213.151.35.143][/size]

Trace complete.

but when i'm trying to connect to servers on internal1 from internal 2 nothing happens and it seems like it trying to find the server on internet from any reason as shown:

C:\Users\1>tracert 192.168.0.1

Tracing route to 192.168.0.1 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 192.168.7.61 [size="1"] 2 16 ms 15 ms 16 ms mx-lns-01.neto.net.il [213.151.32.237][/size] 3 16 ms 16 ms 16 ms 10.17.50.5 4 * * * Request timed out. 5 * * * Request timed out. 6 * * * Request timed out. 7 * ^C C:\Users\1>tracert www.google.com

[size="1"]Tracing route to www.google.com [74.125.195.147][/size] over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.7.61 [size="1"] 2 16 ms 15 ms 15 ms mx-lns-01.neto.net.il [213.151.32.237][/size] 3 16 ms 16 ms 15 ms 10.17.50.5 4 16 ms 16 ms 17 ms 213.151.32.188 [size="1"] 5 82 ms 70 ms 87 ms xe-10-3-3-249.edge4.London1.Level3.net [212.113.[/size] 14.217] 6 77 ms 77 ms 77 ms 72.14.203.126 7 78 ms 77 ms 77 ms 209.85.255.78 8 74 ms 75 ms 75 ms 216.239.51.3 9 85 ms 84 ms 84 ms 209.85.249.211 10 80 ms 80 ms 80 ms 72.14.239.96 11 * * * Request timed out. [size="1"] 12 83 ms 83 ms 83 ms wj-in-f147.1e100.net [74.125.195.147][/size]

Trace complete.

thanks for any help

 

10 REPLIES 10
ggntt

We had an issue recently where we could ping a device connected to the internal port and could ping the WAN / Internet from the CLI

It just made no sense, no traffic visible...all rules correct.

We suspect the config got corrupt when we upgraded the OS after we took the device out of the box and did not do a factory reset before starting the config.

We suspect that the older version fw default config got corrupt during the upgrade ....when we factory reset on the latest OS and started again the device worked perfectly.  

Announcements

Select Forum Responses to become Knowledge Articles!

Select the “Nominate to Knowledge Base” button to recommend a forum post to become a knowledge article.

Labels
Top Kudoed Authors