As the error message does not include the message like "denied by access-list inside_in", I don't believe that this has something to do with my access-list. However, I'll try to open everything to see if this helps, but normally, the PIX reports the name of the access-list which dines something....
710003 is actually an existing logg message from the 6.x code. You should have been seeing these messages previously.
The way I read the error message is that the PIX is interpreting the the broadcast with destination port 138 as a request to connect to UDP/138 on the inside interface.
The PIX allows only a few protocols on the interfaces. As an example, when you issue the command below, the PIX adds a "virtual permit" to its interface ACL. This ACL is seperate and distinct from an ACL that filters traffic THROUGH the PIX.
ssh 10.10.10.0 255.255.255.255 inside
I recognize this is a tad confusing. The access-group command binds an ACL to an interface for traffic going through the PIX. The ssh command binds a permit statement for access TO the inside interface.
In short, you cannot change the fact that the inside interface disallows UDP/138. You COULD supress the message, but I would not recommend it.
One workaround would be to put a 2-port router between the inside interface and the inside subnet. Since the router will not forward a broadcast, you will not see the message. Unfortunately, this has the same effect as "no logging message 710003".
Login to the FXOS chassis manager.
Direct your browser to https://hostname/, and log-in using the user-name and password.
Go to Help > About and check the current version:
Check the current version availa...
We have configured the outside and inside Interface with official ipv6 adresses, set a default route on outside Interface to our router, we also have definied a rule , which also gets hits, to permit tcp from inside Interface to any6.
In Syslog I also se...