Hello, we are testing VPN-IPsec connection through Fortigate 80CM. It
seems that the traffic stops in Fortigate and 137/udp port and the log
entry is enclosed below. How could port 137 traffic be enabled in
Fortigate? 2012-05-25 23:58:46 log_id=00380...
Hello, we would need to make two ports stealth in FG-80CM which
www.grc.com display now not stealth - Port 113 auth / ident - is now
closed but wanted to be stealth --> www.grc.com diagnostics were: " ...
trick is to use the router' s own port forwar...
Yes, different procedure is needed and that command is not available in
4.3. The following article will explain how to go about blocking port
541
http://kb.fortinet.com/kb/microsites/search.do?cmd=displayKC&docType=kc&externalId=FD33502&sliceId=1&doc...
Thanks for the help! Here is the debug log, does it give any further
hints what to try next: FG80CM3909605232 # id=36871 trace_id=1 msg="
vd-root received a packet(proto=17,
192.168.1.111:137->192.168.1.255:137) from internal." id=36871
trace_id=1 ms...
Thanks for the information! Custom service was added Name: UDP/137,138
Protocol Type: TCP/UDP/SCTP Protocol: UDP Source port: Low 1024 High
65535 Destination Port: Low 137 High 138 New Policy was added before the
generic policies Source Interface/Zon...
Thanks for the advice! CLI scripts resolved the problem: config system
interface edit wan1 set ident-accept enable end config sys
management-tunnel set status disable end
