Capturing kerberos traffic but not able to capture TGS-REQ ?
TGS-REP are getting captured but no TGS-REQ, any inputs for such case?
Does the system have multiple interfaces/addresses? If so, it's quite possible that the TGS-REQs are sometimes arriving on different interfaces/addresses.
Asked: 2017-11-03 13:42:46 +0000
Seen: 555 times
Last updated: Jul 30 '18
Providing more information like how and where the capture has been taken, which devices are involved etc. would be helpful.
It’s one app which is configured for Kerberos with delegation, when we capture wire shark we can see TGS-rep but not TGS-REQ on one of the domain on other domains we can see REQ as well