HI, I have a cluster of 2 X 100D running 5.4.4. DHCP stop giving IP to
PC last week, it did not look like pool was exausted. Did not find
anything in the system log. I ended up rebooting the master and it did
solve the problem. Today exactly 7 days a...
I'm trying to create a VIP on fortios 5.4 from wan to internal on port
80 and it doesn't work. I changed the fortigate management port for http
to 8181. If I use port 85 it does work but nothing on port 80. Also for
strange reason I don't see anythin...
I have a virtual server setup from a public ip to an internal server (
owa ) with ssloffload. The server has the necessary fortigate
certificate and the fortigate is presenting the original server
certificate to the clients coming from the web. It us...
Looking at the know bugs in 5.4.4 I found: 377192: DHCP request after
lease expires is sent with former unicast IP instead of 0.0.0.0 as
source. Not sure of the implication... My lease is 172800 ( 48 hours )
so I would be expecting to have the issue ...
What happens if you telnet to the port locally ? # execute telnet
127.0.0.1 80Trying 127.0.0.1...Failed to connect to specified unit. We
are assuming your local access on port 8181 is working ? Yes access to
http via 8181 is working fine from interne...
Hi, I have the same issue with a cluster of 310B under 5.2.5 ( was the
same on 5.2.4 ). There is no hdd on the 310B so it only log to memory. I
looked at my 60D that log to memory and to forticloud and this one shows
SSLVPN logs. So I tested removing...
