Showing results for 
Show  only  | Search instead for 
Did you mean: 

Who Me Too'd this topic

TS Agent no port mapping when using windows net use

L1 Bithead

Hey Guys

We have noticed a weird behaviour:

When I do a telnet to IP 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:


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

Who Me Too'd this topic