UaGateway BadTimeout to localhost

[DWEC92]

Hello dear UA Forum,
I am trying to get the UaGateway working but after installing latest version I cant connect to the localhost as in the installation webinar on the website.
It says "Could not connect to server BadTimeout". The icon says server is running. I dont know how to debug from there. I tried to install it on a Windows 7 Pro machine maybe thats the issue. I also tried it on a windows 11 and a windows 10 machine and it was running without any issues. But my OPC DA Server runs on Windwos 7 so I hope you could help me solve the issue!

Greetings

[Support Team]

Hi,

just for clarification. Where exactly do you get the BadTimeout?
1) You have "installed" the UaGateway
2) You have clicked through the AdministrationDialog (finished with Apply/Close)
3) You have "started" the UaGateway by clicking "Start" in the Taskbar Icon
4) You "opened" the ConfigurationTool (which tries to connect to UaGateway on localhost:48050)
If you get "BadTimeout" here, the UaGateway is not running (check with Taskmanager, look for "uagateway.exe"), or runs on a different TCP-port, or ConfigurationTool tries on different TCP-port.
5) in ConfigTool you "configured" connection to underlying DA Server (browse for DA Server and "Add/Close")
6) Connections state must be shown as "conneced"
If you get "lost connection, trying reconnect" here, your underlying DA Server does not come up. If you get "BadTimeout" here, the DA Server may hung up, or can't be started because of insufficient permissions

[DWEC92]

Hej!
I am on Point 4)

I opened ConfigurationTool and want to connect to localhost:48050.
The task uagateway.exe is running in taskmanager.

In administration the port is set to 48050 and in configurationtool is the endpoint url opc.tcp://pcname:48050

[DWEC92]

I just want to let you know that Í moved to windows 10 and it works just fine!

[Support Team]

Hi,

we never had any issues with Windows version, since WinXPSP3 up to now Win11, the UaGateway can be installed and runs just fine.
The only reason the ConfigTool can not connect (ending in BadTimeout) is that the URL (opc.tcp://pcname:48050) using for connect is not reaching the UaGateways UA Server.

Possible reasons are:
1) uagateway.exe is not running (but you have checked that)
2) configuration was changed to different port, other than 48050 (but you have checked that as well)
3) the host name could not be resolved (would be unusual on localhost, maybe manipulated etc/host file)

Note: make sure your "hostname" confirms to the RFC standard (certain characters are not allowed, but could be configured in Windows OS). You should stick to the standard to allow proper name resolution with all (different) methods available in your network infrastructure.