This discussion has been locked.

You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Update to 7.300 NAT issue

I just had a "gotcha" that may get others:

After applying 7.300 update, all of my NATS were disabled. Enabling them caused an error. This was due to my use of the service type "ANY".

A quick work around is to make a group called "Everything" or "ALL"....etc
and add the existing "ANY" service to it.

Change your NATS to use this new group and all will be fine.

Hope this helps someone.

Matt

This thread was automatically locked due to age.

Parents

0 BrucekConvergent over 17 years ago

Interesting... according to the bugfix list, there was a NAT issue when ANY was used as a service that was corrected in 7.300 (I was one of the ones that reported it, it started showing up in 7.200)... sounds almost like the fix was to prevent folks from selecting ANY... interesting!

CTO, Convergent Information Security Solutions, LLC

https://www.convergesecurity.com

Advice given as posted on this forum does not construe a support relationship or other relationship with Convergent Information Security Solutions, LLC or its subsidiaries. Use the advice given at your own risk.
Cancel
Vote Up 0 Vote Down

Cancel

Reply

0 BrucekConvergent over 17 years ago

Interesting... according to the bugfix list, there was a NAT issue when ANY was used as a service that was corrected in 7.300 (I was one of the ones that reported it, it started showing up in 7.200)... sounds almost like the fix was to prevent folks from selecting ANY... interesting!

CTO, Convergent Information Security Solutions, LLC

https://www.convergesecurity.com

Advice given as posted on this forum does not construe a support relationship or other relationship with Convergent Information Security Solutions, LLC or its subsidiaries. Use the advice given at your own risk.
Cancel
Vote Up 0 Vote Down

Cancel

Children

No Data