[X2Go-User] socket bind error with Windows client

[Ulrich Sibiller]

Hi Hanno,

The second to last line shows x2goclient is (still) listening to port
57030 for further connections, so I think this is the ssh master
connection.
The second connection is from nxproxy to your local X server.
The first and the last line show a tcp connection between nxproxy and
x2goclient, using the 57030 port. I guess this is the connection from
the nxproxy to the nxagent on the server, tunneling through the master
connection.

So far, so good. So all this probably means that x2goclient is always
selecting port 57030 for the master connection. I have no idea why it
behaves like that. But this must not necessarily be a problem itself.
I think before you rebooted there was simply a hanging ssh master
connection blocking that port.

In the source code there's no evidence of 57030 being hardcoded so it
is probably tied to your system. Can you confirm that after another
(or multiple) reboot(s) it is still using 57030?

Uli

On Wed, Mar 15, 2023 at 12:06 PM Hanno Foest <hurga-x2go at tigress.com> wrote:
>
> 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
> _______________________________________________
> x2go-user mailing list
> x2go-user at lists.x2go.org
> https://lists.x2go.org/listinfo/x2go-user