In small remote sites, we want to get rid of our dependence on static
addressing, so DHCP seems like a no-brainer. We have one major criteria
though: the DHCP server must do Dynamic DNS updates to our internal DNS
zone on behalf of the client. Our cl...
Hello, We have been using SSLVPN in tunnel mode with FortiClient for
awhile with good success. Intranet and Internet web browsing was
successful. Recently, we turned on split-tunnelling so all Internet
browsing wouldn' t come through our corporate ne...
Hello, we' re experiencing an issue where the SSL-VPN client stops
working after a 2-4 weeks on a particular laptop. All it takes is an
uninstall/reinstall of the SSL-VPN client and it will immediately start
working again. It doesn' t give any error ...
Hello, I' ve got an odd one for you... Recently switch from MPLS service
to FGT VPNs for a bunch of sites. 200B Cluster at Central site, 60Cs at
remote. Since the change, we have been experiencing the following
problem in most (if not all) of the rem...
Has anyone tried or successfully used OpenVPN SSL client to connect to
FortiGate SSL VPN? I tried, but when connecting I get an error in the
FortiGate debug logs regarding certificates, I think. Not sure how much
effort its worth putting into. I' m l...
You can use ' expect' to script changes to your Fortigate through CLI.
That expect script could be launched from a cron job or something, to
routinely modify your configuration. So, in short, yes it is possible.
In general yes, DHCP clients should and do update their own records. In
this environment I' m dealing with antiquated thin clients mostly where
client-side DNS updates are unheard of.
Paul S, https://support.fortinet.com/EndUser/Bulletin.aspx Also see the
4.3.5 thread:
http://support.fortinet.com/forum/tm.asp?m=80337&p=1&tmode=1&smode=1
Is there still a good reason not to go to MR3? I steered well clear of
it for the first few releases, but is it stablized now? This is going on
a pair of 200Bs.