I have 2 MS servers that I am trying to pull WMI statistics from. When I access the server with its real address of 10.0.1.224 it is successful. When I try to access it with the NAT'd address of 10.5.20.224 it fails. I have inspect dcerpc enabled with a class-map. Pings, traceroutes, RDP's work with no issues to the NAT'd address of 10.5.20.224
I did a packet trace and it works. In the DCERPC debug the packet that it says the original length is 1032 and the new length is 1048 shows up as a malformed packet in the wireshark trace.When I attempt WMI to the real address this doesnt happen. Thanks.
To be honest I can't tell what the problem is since I am not familiar on the actual connection you are trying to form and debug.
I would imagine it might have something to do with the "inspect" itself?
As you said, the "packet-tracer" goes through but I assume that the "inspect" does something to this traffic in between that makes it fail. Is the "inspect" supposed to be essential for this connection to work or can it even be removed?
Dont know if I can be much help with this as I dont know anything about the actual connection and how its supposed to behave.
BenefitsDocumentationPrerequisiteImage Download LinksLimitationsSupported PlatformsLicense RequirementsTopologyStep-By-Step ConfigurationConfigure Virtual ServiceActivate the virtual service and configure guest IPsConfiguring UTD (Service Plane)Configurin...
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...