Can't start StellwerkSim on my new laptop

[sandervh1998]

Hi,

I am trying to start stellwerksim on my laptop because I want to play when I am travelling with public transport. With my old laptop wasn't this any problem but since I have a new laptop I get a red light by the "Zeitsystemenverbindungstest". I've Java version 8 update 321 and stellwerksim build 5832. My laptop is a windows 10 device. I tried to re-install the game and Java but it isn't succesful.

The console give me the following error:

Code: Alles auswählen

18., 22:22:31
mrt 18, 2022 10:22:31 PM js.java.schaltungen.stsmain start
WARNING: Ohne einen Fehler ist eine Warnung nur eine Warnung und unkritisch.
mrt 18, 2022 10:22:31 PM js.java.schaltungen.stsmain start
INFO: Ohne einen Fehler ist eine Information nur eine Information und unkritisch.

Build: 5832
mrt 18, 2022 10:22:31 PM com.sun.xml.internal.ws.wsdl.PayloadQNameBasedOperationFinder <init>
WARNING: Non unique body parts! In a port, as per BP 1.1 R2710 operations must have unique operation signature on the wire for successful dispatch. Methods [getName, userData, getUid, getTip, isLoginAllowed, eventOccured, storeLatency, getFriendFoe, userConsole] have the same request body block {http://www.w3.org/2001/XMLSchema}string. Method dispatching may fail, runtime will try to dispatch using SOAPAction. Another option is to enable AddressingFeature to enabled runtime to uniquely identify WSDL operation using wsa:Action header.
mrt 18, 2022 10:22:31 PM com.sun.xml.internal.ws.wsdl.PayloadQNameBasedOperationFinder <init>
WARNING: Non unique body parts! In a port, as per BP 1.1 R2710 operations must have unique operation signature on the wire for successful dispatch. Methods [getName, userData, getUid, getTip, isLoginAllowed, eventOccured, storeLatency, getFriendFoe, userConsole] have the same request body block {http://www.w3.org/2001/XMLSchema}string. Method dispatching may fail, runtime will try to dispatch using SOAPAction. Another option is to enable AddressingFeature to enabled runtime to uniquely identify WSDL operation using wsa:Action header.
mrt 18, 2022 10:22:44 PM de.deltaga.eb.BasicEventBus publish
INFO: No subscriber for js.java.schaltungen.chatcomng.ChatUser
mrt 18, 2022 10:22:44 PM de.deltaga.eb.BasicEventBus publish
INFO: No subscriber for js.java.schaltungen.chatcomng.ChatUser

Does someone know how I can fix this? Thnx in advance!

[DLichti]

Hm, I can't really identify any problem in your console log. But your description seems to hint at a firewall issue between your device and the STS server. According to the manual, STS needs to send packets on port 3288 and 6676 and receive UDP packets.

If you use a software firewall on your device or a hardware firewall in your uplink, you should check their configuration.

If you connect via a Hot Spot or mobile data, your provider may be blocking connections on these ports.

David

[sandervh1998]

Hi david,

Thank you for your response. I tried to use a VPN and with a VPN Connection I can join, also with another mobile hotspot. It seems to be a problem with my hotspot. The weird thing is that when I am using the hotspot of a friend at the same provider the game will start. Is there a possibility that my hotspot is blocked for the game (for example for very short plays or something)?

[DLichti]

A mobile hotspot is acting like a router, usually with some kind of integrated firewall software. The forwarding rules may very well depend on the manufacturer and the installed operating system.

I don't have access to internal information of the simulator, but I am not aware of any measures to block specific client devices, even less intermediate network devices (which would be rather hard to realize, anyways). Blocks for short plays or hopping are user based and would show up as explicit error message on the signal box session selection page.

There is a mechanism to block multiple sessions over the same public IP. But to my knowledge, this would also be reported by a clear error message on the signal box session selection page.

So, from what you write, it seems to be a problem with your restrictive mobile hotspot.

David