JavaClient account launches as @unknown

[stefan_h]

Yes, the replacement of fqdn with the ip-address in the downloaded jnlp-file solved the problem!

Thank you!

[DirkH]

Unfortunately the IP address was already present in our downloaded JNLP file. However, we can't really treat that as a proper solution, can we? Downloading the JNLP file, replacing all instances of the server name with the IP address each time and then launching the client... That doesn't sound very user friendly to me

Our team member with the issues is now using a different pc each time she needs to use FirstSpirit. I know that can't be a proper solution either, but so far we haven't found a proper solution. If anybody here has any other ideas, don't hesitate to mention them.

[Peter_Jodeleit]

She could change the url she uses to open the start page of your FirstSpirit installation (using the IP instead of the FQN in the URL).

Btw: I suspect that this is not a bug in FirstSpirit but a problem in your network infrstructure or in the name resolving of the infected affected pc.

[christian_vogel]

@Dirk Hendriks:

in your case, did it work  with the IP address in the jnlp? I understood your reply to Stefan Heiking, that it didn't work for you?

Stefan Heiking is working at our customer, so him and me are talking about the same problem and "solution".

I agree that changing the Name to IP-address is no solution, but it's a strong hint, that it is probably no Firstspirit problem.