TS Agent no port mapping when using windows net use

Reply
Highlighted
L1 Bithead

TS Agent no port mapping when using windows net use

Hey Guys

We have noticed a weird behaviour:

When I do a telnet to IP 1.1.1.1 Port 445 on our Terminal Server with the TS Agent installed, the associated Port Range will be used as expected and the source user-id will be mapped.

But when we do a net use in the same CMD window, it won't associate it with the expected port range but with a higher, not related to the users one and won't map the user-id. Both connections are Port 445 (checked in the logs).

 

I found this article online regarding that system context actions can't be mapped:

https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA10g000000ClkCCAS

 

Anyone has/had the same issue? Can it be  that net use is running in system context and can't be tracked?

Thanks and best regards


Accepted Solutions
Highlighted
Cyber Elite


@ErrantOsi wrote:

Can it be  that net use is running in system context and can't be tracked?


That's already the reason why the TS Agent is not able to determine the source user for SMB traffic

View solution in original post


All Replies
Highlighted
Cyber Elite


@ErrantOsi wrote:

Can it be  that net use is running in system context and can't be tracked?


That's already the reason why the TS Agent is not able to determine the source user for SMB traffic

View solution in original post

Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

Click Accept as Solution to acknowledge that the answer to your question has been provided.

The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!

These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the Live Community as a whole!

The Live Community thanks you for your participation!