Overview
Regarding the default service object of Managed Firewall / UTM, there are some differences between the display setting and the actual setting. This event occurs in both Version 1 and Version 2.
Regarding the default settings of the following service objects, there is a problem with Protocol Type "TCP/UDP/ICMP".
For an example of DNS service object, the Destination Port is "53", and Protocol Type is "UDP" on the setting screen, but in reality "UDP" and "TCP" are set. Even if the destination port is "53" and the protocol type is "UDP" on the screen, it actually works like the destination port "53" and the protocol type "UDP + TCP".
Target service object (Protocol name: TCP port number / UDP port number)
DNS:53/53
H323:1720 1503/1719
L2TP:1701/1701
NFS:111 2049/111 2049
NTP:123/123
PC-Anywhere:5631/5632
ONC-RPC:111/111
DCE-RPC:135/135
SIP:5060/5060
SNMP:161-162/161-162
SOCKS:1080/1080
WINS:1512/1512
CVSPSERVER:2401/2401
AFS3:7000-7009/7000-7009
RTSP:554 7070 8554/554
MMS:1755/1024-5000
KERBEROS:88/88 * Version1 Service
KERBEROS:88,464/88,464 * Version2 Service
Workaround
When the [Apply configuration] button is pressed after saving on the object edit screen, the protocol settings displayed on the screen on the device will be reflected. Only the UDP displayed on the screen is set. TCP that was not previously displayed on the screen will be removed from the device settings. If you want to use TCP for communication, please add a new rule.