Post a reply

Before posting, please read how to report bug or request support effectively.

Bug reports without an attached log file are usually useless.

Options
Add an Attachment

If you do not want to add an Attachment to your Post, please leave the Fields blank.

(maximum 10 MB; please compress large files; only common media, archive, text and programming file formats are allowed)

Options

Topic review

martin

Re: X11 not usable while having a winscp session using a tunnel

Thanks. I'll look into it. But actually I have no experience with X11.
rainbumped

Re: X11 not usable while having a winscp session using a tunnel

Anonymous wrote:

martin wrote:

How do you connect "over a tunnel"?
Do you create the tunnel in PuTTY? Or do you use the built-in WinSCP tunneling functionality?


I use the built-in winscp tunnel. I only tunnel X11 via putty. Putty is started independently from winscp.


that was my answer. somehow posted only as guest... :?:
Guest

Re: X11 not usable while having a winscp session using a tunnel

martin wrote:

How do you connect "over a tunnel"?
Do you create the tunnel in PuTTY? Or do you use the built-in WinSCP tunneling functionality?


I use the built-in winscp tunnel. I only tunnel X11 via putty. Putty is started independently from winscp.
martin

Re: X11 not usable while having a winscp session using a tunnel

How do you connect "over a tunnel"?
Do you create the tunnel in PuTTY? Or do you use the built-in WinSCP tunneling functionality?
rainbumped

X11 not usable while having a winscp session using a tunnel

Hi,
first of all, thanks for winscp! Great product!

Now to my question:
When I'm connected to a host via putty and open a winscp session over a tunnel, I cannot use X11 any more
xterm Xt error: Can't open display: localhost:63.0


Once I close the winscp session, I can use X11 again. X11 tools started before the winscp-session are still usable - only the start of new x11-programs is affected.
Sometimes it helps to set the port to a fixed value instead of auto-mode but it's not a guarantee.

Not only that one SSH-Connection is affected by this problem but all (opened different putty sessions to different hosts) connections cannot start x11-progams as long as the winscp session is connected.

It does not matter which X11-Server is running (tried cygwin, vcxsrv, reflection-x).

It also seems to only affect X-Servers started for Display 0 (:0) ...starting an X-Server for :1 and setting up an ssh-session with display-location "localhost:1.0" lets me start x-programs on that server while the other session for :0 shows the problem (which goes away once the winscp-session terminates).

Any ideas?

KR
Thomas