Hello ​@Tina_K - unfortunately not, if you need this type of information, then you would need to collect logging from the Jump Client itself. Or you can log a case with our Support Team who can walk you through some other checks through appliance logging.

Hello ​@PhillC  thank you for your reply!

Is there really not even some kind of .ini file or something on the client somewhere? 

By collecting logging from the jump client you mean with the blog.ini right?

That is a bit overkill… I just want to see a parameter “client name xyz is connected to trafficnode_germany.support.de” for example.

And the best would be to get this parameter on the fly for any client if I need it.

Hello ​@Tina_K - that would be a great idea to put on our Ideas Portal, through the link at the top of this page. If you log this idea, I will happily vote it up.

Can I ask if there is an issue you are trying to solve here or something this information will help you with? We are happy to work through any issues or problems you are having with your Jump Clients.

Hello ​@PhillC  - done ;-)  T2SRM-I-3593

I found another idea that goes slightly into this direction with “unlikely to implement”, but maybe mine is not too unlikely… 

Sure, we have some tickets opened up with your support at this time. And one of them is a strange issue with the web console: Screen sharing only works if the supporter uses the same traffic node as the client. If not, the loading bar never goes away. It is at escalation team right now I think… 

So the information about the traffic node would be great for troubleshooting, workaround and also to see if everything works correctly with the jump clients. (To check if they can connect correctly)

I appreciate every help! ^^