Dual WAN LINK interface administration

[#1]

Hi all, I already set up 2 WAN link and its working (able to browse internet ), I am only able to access WAN1 administrative webaccess but WAN2, I' m unable to do so. I have set equal distance (5) in the static route for both of the WAN Link and also enable administrative access to both of the WAN link either http and https. What other steps that I miss out? Thank you all.

[g3rman]

dbsanders, do you have 8.7.25.181 in your trusted hosts in the admin configuration? Or are they all 0.0.0.0/0.0.0.0?

[dbsanders]

They are all 0.0.0.0/0.0.0.0. I believe it' s a routing issue - I can set up a static route for my client IP on WAN2 and it does work. I think there' s something I' m not understanding here.

[#4]

Sorry guys, to make load balancing and fail over, what ping server should we point to? It is alright if we put dns server as ping server address ? I m a newbie in firewall and mind I' ll be asking what step that I miss out somemore to allow administrative access to WAN2.

[#5]

Hello dbsanders , In order for wan2 to accept traffic from the Internet you' ll effectively need a second default route associated to this interface, or at least a specific route back the the source IP. The routing table should look like (partially) : S* 0.0.0.0/0 [1/0] via a.b.c.d, wan1 ................. [1/0] via e.f.g.h, wan2 Jabo.

[#6]

august_twenty8, The following article will give some details about fail-over and ping-server : http://kb.fortinet.com/kb/microsites/search.do?cmd=displayKC&docType=kc&externalId=FD30626 I think it' s ok to put a DNS server as ping server, as long as the ping-server is a reliable device. Jabo.