You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've set the default shell of the server the Bash of WSL 2, and I'm able to connet to my server through SSH using the WSL Bash. It works perfect except for the X11 Forwarding.
On the beggining of the section MobaXterm prints..
│ ∙ Direct SSH : ✔ │
│ ∙ SSH compression : ✔ │
│ ∙ SSH-browser : ✔ │
│ ∙ X11-forwarding : ✘ (disabled or not supported by server)
When I try echo $DISPLAY I got:
172.29.0.1:0
But it is not on the list of listening Displays.
Expected Behavior
GUI Applications Running on the client using Xserver as it does when running a local WSL.
Actual Behavior
When I start a GUI application from the client it opens on the server machine if it is a running Xserver, if not it does not open.
Diagnostic Logs
No response
The text was updated successfully, but these errors were encountered:
Windows Build Number
Microsof windows 19041.1052
WSL Version
Kernel Version
5.4.72
Distro Version
Ubuntu 20
Other Software
MobaXterm X11 Server
Repro Steps
I've set the default shell of the server the Bash of WSL 2, and I'm able to connet to my server through SSH using the WSL Bash. It works perfect except for the X11 Forwarding.
On the beggining of the section MobaXterm prints..
│ ∙ Direct SSH : ✔ │
│ ∙ SSH compression : ✔ │
│ ∙ SSH-browser : ✔ │
│ ∙ X11-forwarding : ✘ (disabled or not supported by server)
When I try echo $DISPLAY I got:

172.29.0.1:0
But it is not on the list of listening Displays.
Expected Behavior
GUI Applications Running on the client using Xserver as it does when running a local WSL.
Actual Behavior
When I start a GUI application from the client it opens on the server machine if it is a running Xserver, if not it does not open.
Diagnostic Logs
No response
The text was updated successfully, but these errors were encountered: