[X2Go-User] socket bind error with Windows client
Hanno Foest
hurga-x2go at tigress.com
Wed Mar 15 12:05:55 CET 2023
Hi,
I didn't manage to gather any useful (apparently related) info with
x2goclient.exe --debug, but when running
NETSTAT.EXE -ban | Select-String -patt "57030" -context 2,3
in powershell with admin rights repeatedly during connection gives me
> TCP 127.0.0.1:59450 127.0.0.1:6002 WARTEND
TCP 127.0.0.1:59451 127.0.0.1:57030
SYN_GESENDET
[x2goclient.exe]
briefly before the error appears. (Note: It's been again 57030 and not
something random.) After rebooting Windows, I was able to connect to my
x2go session again. Running the above command again gives me
> TCP 127.0.0.1:52146 127.0.0.1:57030 HERGESTELLT
[nxproxy.exe]
TCP 127.0.0.1:52148 127.0.0.1:6000 HERGESTELLT
[nxproxy.exe]
> TCP 127.0.0.1:57030 0.0.0.0:0 ABHÖREN
[x2goclient.exe]
> TCP 127.0.0.1:57030 127.0.0.1:52146 HERGESTELLT
[x2goclient.exe]
so I would guess indeed something is not listening which should be listening,
when the error appears...
Hanno
On Wed, Mar 08, 2023 at 05:28:49PM +0100, Ulrich Sibiller wrote:
> I am not sure where the tunnel is created (there's ssh communication
> in both directions) so better check the port on the server side, too.
>
> You can run x2goclient.exe --debug --sshlib-debug --session="your
> session name" and you will find logfile in <your user
> directory>/.x2go/sshLogs. Maybe that helps to identify the problem.
>
> Uli
More information about the x2go-user
mailing list