NAT: Receiving "Error: Unknown Service Class"
08/25/2022 11 People found this article helpful 401,067 Views
Description
NAT: Receiving "Error: Unknown Service Class"
Resolution
Resolution for SonicOS 7.X
This release includes significant user interface changes and many new features that are different from the SonicOS 6.5 and earlier firmware. The below resolution is for customers using SonicOS 7.X firmware.
Problem Definition:
Receiving the following “Error: Unknown Service Class” when creating NAT policy.
Resolution or Workaround:
This error indicates that the Original Service and Translated Service are not of the same type (TCP/UDP). In the instance above, the Original Service is just TCP 3392, but the Translated Service contains TCP and UDP 3389.
To correct/avoid this error, be sure to pick a Translated Service with the correct protocol. As seen in this example:
Resolution for SonicOS 6.5
This release includes significant user interface changes and many new features that are different from the SonicOS 6.2 and earlier firmware. The below resolution is for customers using SonicOS 6.5 firmware.
Problem Definition:
Receiving the following “Error: Unknown Service Class” when creating NAT policy.
Resolution or Workaround:
This error indicates that the Original Service and Translated Service are not of the same type (TCP/UDP). In the instance above, the Original Service is just TCP 3392, but the Translated Service contains TCP and UDP 3389.
To correct/avoid this error, be sure to pick a Translated Service with the correct protocol. As seen in this example:
Resolution for SonicOS 6.2 and Below
The below resolution is for customers using SonicOS 6.2 and earlier firmware. For firewalls that are generation 6 and newer we suggest to upgrade to the latest general release of SonicOS 6.5 firmware.
Problem Definition:
Receiving the following “Error: Unknown Service Class” when creating NAT policy.
Resolution or Workaround:
This error indicates that the Original Service and Translated Service are not of the same type (TCP/UDP). In the instance above, the Original Service is just TCP 3391, but the Translated Service contains TCP and UDP 3389.
To correct/avoid this error, be sure to pick a Translated Service with the correct protocol. As seen in this example:
Related Articles
Categories