Hi, I have a device on the DMZ with port 443 open and the site can be
accessed fine, no other ports are in the allow policy for that device.
When I do a scan on the devices external IP however I saw ports 8008 and
8010 listed as open and whn I went t...
Hi, recently turned on the report feature on our 200b to send us a
weekly summary report. The last two weeks I've noticed on the Top Users
by Sessions there is an external IP making the top 10, all other IPs are
(as expected) internal IPs. We don't h...
Hi I'm trying to get my head around setting up QOS/ traffic Shaping for
a particular need we have. My big concern is not to adversely affect
other network traffic if possible.Fortigate 200B Firmware: v5.0
build0318 - GA Patch 12 We have a 150/150 pip...
Hi (edit: 4.0 MR3 on a 200b) I' m setting up a VIP for an internal
server to allow it server http traffic. We already have another server
doing the same and it' s working fine. I cannot get the new server to
work. I' ve created the same rules, placed...
We' ve change ISP so have set up a new interface for the new ISP. I' ve
duplicated the existing policies to point to the new WAN interface,
disabled the existing policies and edited the static route so now all
traffic is going through the new ISP. In...
Found the cause of this, there was a web filter rule enabled on this
particular policy even though it was a WAN --> DMZ rule for https
access. Once I disabled web filtering on the policy the access on port
8008 and 8010 is no more.
After much chasing our ISP have come back to say there is a route config
error in their systems in relation to our IP assignment! They plan to
sort it tomorrow morning so all going well that' s the problem. Thanks
for the help, apologies for any wast...
Fairly sure, a long time ago when I was setting up a VIP I was trying to
use ##.###.###.92 and I could not for the life of me get it working, had
the same issues I' m having now. That time I contacted the ISP and they
ran their tests and told me it w...
Hi I can ping the Newserver' s internal, external and FQDN from a
Fortigate SSH session and it replies. When I enable the logging and
tried pinging the Newserver WAN IP from an external source nothing was
logged. Just for some historic info, we had a...
Hi Ede, thanks for the reply. -The WAN to Webserver never works to the
new server. -For some strange reason when the new WAN to Webserver
Firewall Policy is enabled it breaks the Webserver to WAN traffic, if I
disable that rule the Webserver to WAN t...
