Re: ssh X11 forwarding not working on FreeBSD 6.2
On Wed, Jul 25, 2007 at 08:35:48PM -0700, Michael S. Eubanks wrote: ... Glad to hear you got it working - you are right though. Here's a quick link. http://www.ssh.com/support/documentation/online/ssh/adminguide/32/X11_Forwarding.html Considerring the client uses a special local display setting, would it work to set the environment variables in PuTTY itself, although, that would seem to be manual again. With respect to X, check out the xauth man page. I'm curious as to whether the xauth file needs to exist in the user's home directory. I think the instructions (pictures) showed a key being added to the PuTTY session config. Micahel, Well, actually I did not get anything working at all that I set out to try and get working. I set out to try and get X11 forwarding working but still have not accomplished it. Any setting of the DISPLAY variable either manually or from PuTTY to anything other than what ssh sets it to bypasses encryption provided by ssh and doesn't solve the problem. Anyone else have any ideas? Terry Todd ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ssh X11 forwarding not working on FreeBSD 6.2 (SOLVED)
The cause of this problem, $ xhost Xlib: connection to localhost:10.0 refused by server Xlib: PuTTY X11 proxy: wrong authentication protocol attempted xhost: unable to open display localhost:10.0 was that the hostname on the FreeBSD system was blank. Once I set the hostname it works fine. In fact you don't even need to turn on any of the options in the sshd_config or ssh_config files. Who woulda thunk it. I figured it out by trying it on 2 other FreeBSD systems that did work and comparing how they worked to the one that didn't. Try it on your systems and I'll bet you see the same thing. Terry Todd ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ssh X11 forwarding not working on FreeBSD 6.2
On Tue, 2007-07-24 at 13:29 -0500, Terry Todd wrote: On Tue, Jul 24, 2007 at 10:54:22AM -0700, Michael S. Eubanks wrote: ... Question. How many X servers do you have running? Are you logged into a window manager when you are attempting to connect? Only one instance of Xming is running on the Windows XP system. I am using PuTTY to connect to the FreeBSD system and the other systems. The other systems all work. FreeBSD X11 forwarding does not work. It is an off the shelf standard install of 6.2. Manually setting the DISPLAY variable on the FreeBSD system to [IP address of Widows XP system]:0.0 will allow it to work but that's not what I want to do here. I want it to automatically forward the X11 session through ssh like it does when connecting to the FC6 system. Terry Todd Okay. I was able to get it running. I received a slightly different error when I tried running an application the first time. My error is from Xming and displays as follows (using X forwarding): AUDIT: Tue Jul 24 23:47:34 2007: 608 C:\Program Files\Xming\xming.exe client 4 rejected from IP 192.168.10.101 This error simply means to add the ``-ac'' option to the Xming desktop shortcut. Let me walk you through what I did. Before I begin, I'm using 6-STABLE (now on 6.2) with Xorg 7.2. QUICK INSTRUCTIONS 1. Make sure to install Xming using both the Xming installer program and Xming fonts installer. 2. Modify the Desktop Xming shortcut to include the following arguments: ``:0 -clipboard -multiwindow -ac''. The ac option accepts client requests and quells the error that I had above. 3. Start Xming using the shortcut you just created 4. I'm going to guess that you may leave your sshd_config file the way it is - I did. 5. Install the Xming Portable PuTTY package. Make the changes shown to the PuTTY configuration as shown here before you connect to the FreeBSD machine (NOTE the X11 forwarding to localhost:0 - I think this is how you said your config was): http://www.straightrunning.com/XmingNotes/trouble.php 6. Log into the FreeBSD machine using PuTTY. Set the DISPLAY environment variable equal to the IP address and display of the XP machine. The command I used was: export DISPLAY=192.168.xxx.xxx:0 7. Make sure your Windows Firewall is either turned off or allows incoming requests for Xming. 8. Execute a command like xeyes. It should show on the windows desktop. On Tue, Jul 24, 2007 at 10:54:22AM -0700, Michael S. Eubanks wrote: On Tue, 2007-07-24 at 12:23 -0500, Terry Todd wrote: On Tue, Jul 24, 2007 at 09:48:05AM -0700, Michael S. Eubanks wrote: ... Start by changing the following line from X11DisplayOffset 10 to X11DisplayOffset 1 ... OK, I tried that. No difference. Here's what heppened on the FreeBSD 6.2 system: $ $ echo $DISPLAY localhost:1.0 $ $ xhost Xlib: connection to localhost:1.0 refused by server Xlib: PuTTY X11 proxy: wrong authentication protocol attempted xhost: unable to open display localhost:1.0 $ $ xhost + Xlib: connection to localhost:1.0 refused by server Xlib: PuTTY X11 proxy: wrong authentication protocol attempted xhost: unable to open display localhost:1.0 $ xterm Xlib: connection to localhost:1.0 refused by server Xlib: PuTTY X11 proxy: wrong authentication protocol attempted xterm Xt error: Can't open display: localhost:1.0 $ Question. How many X servers do you have running? Are you logged into a window manager when you are attempting to connect? Here's what happens on the FC6 system: $ echo $DISPLAY localhost:13.0 $ $ xhost access control disabled, clients can connect from any host INET:terry-pc.egizone.com LOCAL: $ Terry Todd On Tue, Jul 24, 2007 at 09:48:05AM -0700, Michael S. Eubanks wrote: On Tue, 2007-07-24 at 10:59 -0500, Terry Todd wrote: I have installed Xming successfully on a Windows XP system. It works OK to a FC6 system and an older UNIXware system. However when trying to connect to a FreeBSD 6.2 system with PuTTY ssh it doesn't work. PuTTY has Enable X11 forwarding checked. Here's what I get: $ $ xhost Xlib: connection to localhost:10.0 refused by server Xlib: PuTTY X11 proxy: wrong authentication protocol attempted xhost: unable to open display localhost:10.0 $ What can be wrong? I have ssh configured as follows: # grep X11 /etc/ssh/* /etc/ssh/ssh_config:ForwardX11 yes /etc/ssh/ssh_config:ForwardX11Trusted yes /etc/ssh/sshd_config:X11Forwarding yes /etc/ssh/sshd_config:X11DisplayOffset 10 /etc/ssh/sshd_config:X11UseLocalhost yes Start by changing the following line from X11DisplayOffset 10 to X11DisplayOffset 1 According to the sshd_conf man page, looks
Re: ssh X11 forwarding not working on FreeBSD 6.2
Michael, Thanks for the directions. Using your method does work. However your method bypasses X11 forwarding. 6. Log into the FreeBSD machine using PuTTY. Set the DISPLAY environment variable equal to the IP address and display of the XP machine. The command I used was: export DISPLAY=192.168.xxx.xxx:0 What I want to get working is X11 forwarding where you don't set the DISPLAY variable explicitly. With X11 forwarding the DISPLAY variable is automatically set to something like, [IP address of Windows box]:0.0. Terry Todd On Wed, Jul 25, 2007 at 12:16:24AM -0700, Michael S. Eubanks wrote: On Tue, 2007-07-24 at 13:29 -0500, Terry Todd wrote: On Tue, Jul 24, 2007 at 10:54:22AM -0700, Michael S. Eubanks wrote: ... Question. How many X servers do you have running? Are you logged into a window manager when you are attempting to connect? Only one instance of Xming is running on the Windows XP system. I am using PuTTY to connect to the FreeBSD system and the other systems. The other systems all work. FreeBSD X11 forwarding does not work. It is an off the shelf standard install of 6.2. Manually setting the DISPLAY variable on the FreeBSD system to [IP address of Widows XP system]:0.0 will allow it to work but that's not what I want to do here. I want it to automatically forward the X11 session through ssh like it does when connecting to the FC6 system. Terry Todd Okay. I was able to get it running. I received a slightly different error when I tried running an application the first time. My error is from Xming and displays as follows (using X forwarding): AUDIT: Tue Jul 24 23:47:34 2007: 608 C:\Program Files\Xming\xming.exe client 4 rejected from IP 192.168.10.101 This error simply means to add the ``-ac'' option to the Xming desktop shortcut. Let me walk you through what I did. Before I begin, I'm using 6-STABLE (now on 6.2) with Xorg 7.2. QUICK INSTRUCTIONS 1. Make sure to install Xming using both the Xming installer program and Xming fonts installer. 2. Modify the Desktop Xming shortcut to include the following arguments: ``:0 -clipboard -multiwindow -ac''. The ac option accepts client requests and quells the error that I had above. 3. Start Xming using the shortcut you just created 4. I'm going to guess that you may leave your sshd_config file the way it is - I did. 5. Install the Xming Portable PuTTY package. Make the changes shown to the PuTTY configuration as shown here before you connect to the FreeBSD machine (NOTE the X11 forwarding to localhost:0 - I think this is how you said your config was): http://www.straightrunning.com/XmingNotes/trouble.php 6. Log into the FreeBSD machine using PuTTY. Set the DISPLAY environment variable equal to the IP address and display of the XP machine. The command I used was: export DISPLAY=192.168.xxx.xxx:0 7. Make sure your Windows Firewall is either turned off or allows incoming requests for Xming. 8. Execute a command like xeyes. It should show on the windows desktop. On Tue, Jul 24, 2007 at 10:54:22AM -0700, Michael S. Eubanks wrote: On Tue, 2007-07-24 at 12:23 -0500, Terry Todd wrote: On Tue, Jul 24, 2007 at 09:48:05AM -0700, Michael S. Eubanks wrote: ... Start by changing the following line from X11DisplayOffset 10 to X11DisplayOffset 1 ... OK, I tried that. No difference. Here's what heppened on the FreeBSD 6.2 system: $ $ echo $DISPLAY localhost:1.0 $ $ xhost Xlib: connection to localhost:1.0 refused by server Xlib: PuTTY X11 proxy: wrong authentication protocol attempted xhost: unable to open display localhost:1.0 $ $ xhost + Xlib: connection to localhost:1.0 refused by server Xlib: PuTTY X11 proxy: wrong authentication protocol attempted xhost: unable to open display localhost:1.0 $ xterm Xlib: connection to localhost:1.0 refused by server Xlib: PuTTY X11 proxy: wrong authentication protocol attempted xterm Xt error: Can't open display: localhost:1.0 $ Question. How many X servers do you have running? Are you logged into a window manager when you are attempting to connect? Here's what happens on the FC6 system: $ echo $DISPLAY localhost:13.0 $ $ xhost access control disabled, clients can connect from any host INET:terry-pc.egizone.com LOCAL: $ Terry Todd On Tue, Jul 24, 2007 at 09:48:05AM -0700, Michael S. Eubanks wrote: On Tue, 2007-07-24 at 10:59 -0500, Terry Todd wrote: I have installed Xming successfully on a Windows XP system. It works OK to a FC6 system and an older UNIXware system. However when trying to connect to a FreeBSD 6.2 system with PuTTY ssh it doesn't work. PuTTY has Enable X11 forwarding checked. Here's
Re: ssh X11 forwarding not working on FreeBSD 6.2
I made a mistake in my last post. SSH X11 forwarding sets the DISPLAY variable to something like: localhost:10.0 It should not be the address of the Windows box because that bypasses X11 forwarding. Terry Todd On Wed, Jul 25, 2007 at 09:01:35AM -0500, Terry Todd wrote: Michael, Thanks for the directions. Using your method does work. However your method bypasses X11 forwarding. 6. Log into the FreeBSD machine using PuTTY. Set the DISPLAY environment variable equal to the IP address and display of the XP machine. The command I used was: export DISPLAY=192.168.xxx.xxx:0 What I want to get working is X11 forwarding where you don't set the DISPLAY variable explicitly. With X11 forwarding the DISPLAY variable is automatically set to something like, [IP address of Windows box]:0.0. Terry Todd On Wed, Jul 25, 2007 at 12:16:24AM -0700, Michael S. Eubanks wrote: On Tue, 2007-07-24 at 13:29 -0500, Terry Todd wrote: On Tue, Jul 24, 2007 at 10:54:22AM -0700, Michael S. Eubanks wrote: ... Question. How many X servers do you have running? Are you logged into a window manager when you are attempting to connect? Only one instance of Xming is running on the Windows XP system. I am using PuTTY to connect to the FreeBSD system and the other systems. The other systems all work. FreeBSD X11 forwarding does not work. It is an off the shelf standard install of 6.2. Manually setting the DISPLAY variable on the FreeBSD system to [IP address of Widows XP system]:0.0 will allow it to work but that's not what I want to do here. I want it to automatically forward the X11 session through ssh like it does when connecting to the FC6 system. Terry Todd Okay. I was able to get it running. I received a slightly different error when I tried running an application the first time. My error is from Xming and displays as follows (using X forwarding): AUDIT: Tue Jul 24 23:47:34 2007: 608 C:\Program Files\Xming\xming.exe client 4 rejected from IP 192.168.10.101 This error simply means to add the ``-ac'' option to the Xming desktop shortcut. Let me walk you through what I did. Before I begin, I'm using 6-STABLE (now on 6.2) with Xorg 7.2. QUICK INSTRUCTIONS 1. Make sure to install Xming using both the Xming installer program and Xming fonts installer. 2. Modify the Desktop Xming shortcut to include the following arguments: ``:0 -clipboard -multiwindow -ac''. The ac option accepts client requests and quells the error that I had above. 3. Start Xming using the shortcut you just created 4. I'm going to guess that you may leave your sshd_config file the way it is - I did. 5. Install the Xming Portable PuTTY package. Make the changes shown to the PuTTY configuration as shown here before you connect to the FreeBSD machine (NOTE the X11 forwarding to localhost:0 - I think this is how you said your config was): http://www.straightrunning.com/XmingNotes/trouble.php 6. Log into the FreeBSD machine using PuTTY. Set the DISPLAY environment variable equal to the IP address and display of the XP machine. The command I used was: export DISPLAY=192.168.xxx.xxx:0 7. Make sure your Windows Firewall is either turned off or allows incoming requests for Xming. 8. Execute a command like xeyes. It should show on the windows desktop. On Tue, Jul 24, 2007 at 10:54:22AM -0700, Michael S. Eubanks wrote: On Tue, 2007-07-24 at 12:23 -0500, Terry Todd wrote: On Tue, Jul 24, 2007 at 09:48:05AM -0700, Michael S. Eubanks wrote: ... Start by changing the following line from X11DisplayOffset 10 to X11DisplayOffset 1 ... OK, I tried that. No difference. Here's what heppened on the FreeBSD 6.2 system: $ $ echo $DISPLAY localhost:1.0 $ $ xhost Xlib: connection to localhost:1.0 refused by server Xlib: PuTTY X11 proxy: wrong authentication protocol attempted xhost: unable to open display localhost:1.0 $ $ xhost + Xlib: connection to localhost:1.0 refused by server Xlib: PuTTY X11 proxy: wrong authentication protocol attempted xhost: unable to open display localhost:1.0 $ xterm Xlib: connection to localhost:1.0 refused by server Xlib: PuTTY X11 proxy: wrong authentication protocol attempted xterm Xt error: Can't open display: localhost:1.0 $ Question. How many X servers do you have running? Are you logged into a window manager when you are attempting to connect? Here's what happens on the FC6 system: $ echo $DISPLAY localhost:13.0 $ $ xhost access control disabled, clients can connect from any host INET:terry-pc.egizone.com LOCAL: $ Terry Todd On Tue,
Re: ssh X11 forwarding not working on FreeBSD 6.2
On Wed, 2007-07-25 at 09:49 -0500, Terry Todd wrote: I made a mistake in my last post. SSH X11 forwarding sets the DISPLAY variable to something like: localhost:10.0 It should not be the address of the Windows box because that bypasses X11 forwarding. Terry Todd On Wed, Jul 25, 2007 at 09:01:35AM -0500, Terry Todd wrote: Michael, Thanks for the directions. Using your method does work. However your method bypasses X11 forwarding. 6. Log into the FreeBSD machine using PuTTY. Set the DISPLAY environment variable equal to the IP address and display of the XP machine. The command I used was: export DISPLAY=192.168.xxx.xxx:0 What I want to get working is X11 forwarding where you don't set the DISPLAY variable explicitly. With X11 forwarding the DISPLAY variable is automatically set to something like, [IP address of Windows box]:0.0. Terry Todd On Wed, Jul 25, 2007 at 12:16:24AM -0700, Michael S. Eubanks wrote: On Tue, 2007-07-24 at 13:29 -0500, Terry Todd wrote: On Tue, Jul 24, 2007 at 10:54:22AM -0700, Michael S. Eubanks wrote: ... Question. How many X servers do you have running? Are you logged into a window manager when you are attempting to connect? Only one instance of Xming is running on the Windows XP system. I am using PuTTY to connect to the FreeBSD system and the other systems. The other systems all work. FreeBSD X11 forwarding does not work. It is an off the shelf standard install of 6.2. Manually setting the DISPLAY variable on the FreeBSD system to [IP address of Widows XP system]:0.0 will allow it to work but that's not what I want to do here. I want it to automatically forward the X11 session through ssh like it does when connecting to the FC6 system. Terry Todd Okay. I was able to get it running. I received a slightly different error when I tried running an application the first time. My error is from Xming and displays as follows (using X forwarding): AUDIT: Tue Jul 24 23:47:34 2007: 608 C:\Program Files\Xming\xming.exe client 4 rejected from IP 192.168.10.101 This error simply means to add the ``-ac'' option to the Xming desktop shortcut. Let me walk you through what I did. Before I begin, I'm using 6-STABLE (now on 6.2) with Xorg 7.2. QUICK INSTRUCTIONS 1. Make sure to install Xming using both the Xming installer program and Xming fonts installer. 2. Modify the Desktop Xming shortcut to include the following arguments: ``:0 -clipboard -multiwindow -ac''. The ac option accepts client requests and quells the error that I had above. 3. Start Xming using the shortcut you just created 4. I'm going to guess that you may leave your sshd_config file the way it is - I did. 5. Install the Xming Portable PuTTY package. Make the changes shown to the PuTTY configuration as shown here before you connect to the FreeBSD machine (NOTE the X11 forwarding to localhost:0 - I think this is how you said your config was): http://www.straightrunning.com/XmingNotes/trouble.php 6. Log into the FreeBSD machine using PuTTY. Set the DISPLAY environment variable equal to the IP address and display of the XP machine. The command I used was: export DISPLAY=192.168.xxx.xxx:0 7. Make sure your Windows Firewall is either turned off or allows incoming requests for Xming. 8. Execute a command like xeyes. It should show on the windows desktop. ...snip... Glad to hear you got it working - you are right though. Here's a quick link. http://www.ssh.com/support/documentation/online/ssh/adminguide/32/X11_Forwarding.html Considerring the client uses a special local display setting, would it work to set the environment variables in PuTTY itself, although, that would seem to be manual again. With respect to X, check out the xauth man page. I'm curious as to whether the xauth file needs to exist in the user's home directory. I think the instructions (pictures) showed a key being added to the PuTTY session config. Cheers, Michael S. Eubanks [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
ssh X11 forwarding not working on FreeBSD 6.2
I have installed Xming successfully on a Windows XP system. It works OK to a FC6 system and an older UNIXware system. However when trying to connect to a FreeBSD 6.2 system with PuTTY ssh it doesn't work. PuTTY has Enable X11 forwarding checked. Here's what I get: $ $ xhost Xlib: connection to localhost:10.0 refused by server Xlib: PuTTY X11 proxy: wrong authentication protocol attempted xhost: unable to open display localhost:10.0 $ What can be wrong? I have ssh configured as follows: # grep X11 /etc/ssh/* /etc/ssh/ssh_config:ForwardX11 yes /etc/ssh/ssh_config:ForwardX11Trusted yes /etc/ssh/sshd_config:X11Forwarding yes /etc/ssh/sshd_config:X11DisplayOffset 10 /etc/ssh/sshd_config:X11UseLocalhost yes Here is the Xming log file: Welcome to the Xming X Server Vendor: Colin Harrison Release: 6.9.0.24 FreeType2: 2.3.0 Contact: http://sourceforge.net/forum/?group_id=156984 C:\Program Files\Xming\Xming.exe :0 -ac -clipboard -multiwindow XdmcpRegisterConnection: newAddress x.x.x.x winPrefsLoadPreferences: C:\Program Files\Xming\Xmingrc LoadPreferences: Done parsing the configuration file... winAdjustVideoModeShadowGDI - Using Windows display depth of 32 bits per pixel winAllocateFBShadowGDI - Creating DIB with width: 1600 height: 1200 depth: 32 winInitVisualsShadowGDI - Masks 00ff ff00 00ff BPRGB 8 d 24 bpp 32 glWinInitVisuals:1511: glWinInitVisuals init_visuals:1055: init_visuals null screen fn ReparentWindow null screen fn RestackWindow InitQueue - Calling pthread_mutex_init InitQueue - pthread_mutex_init returned InitQueue - Calling pthread_cond_init InitQueue - pthread_cond_init returned winInitMultiWindowWM - Hello winInitMultiWindowWM - Calling pthread_mutex_lock () winMultiWindowXMsgProc - Hello winMultiWindowXMsgProc - Calling pthread_mutex_lock () glWinScreenProbe:1390: glWinScreenProbe fixup_visuals:1303: fixup_visuals init_screen_visuals:1336: init_screen_visuals (--) 5 mouse buttons found (--) Setting autorepeat to delay=500, rate=31 (--) winConfigKeyboard - Layout: 0409 (0409) (--) Using preset keyboard for English (USA) (409), type 4 Could not init font path element C:\Program Files\Xming/fonts/misc/, removing from list! Could not init font path element C:\Program Files\Xming/fonts/TTF/, removing from list! Could not init font path element C:\Program Files\Xming/fonts/Type1/, removing from list! Could not init font path element C:\Program Files\Xming/fonts/75dpi/, removing from list! Could not init font path element C:\Program Files\Xming/fonts/100dpi/, removing from list! Could not init font path element C:\Program Files\Xming\fonts\dejavu, removing from list! Could not init font path element C:\Program Files\Xming\fonts\cyrillic, removing from list! Could not init font path element C:\WINDOWS\Fonts, removing from list! winInitMultiWindowWM - pthread_mutex_lock () returned. winInitMultiWindowWM - pthread_mutex_unlock () returned. winMultiWindowXMsgProc - pthread_mutex_lock () returned. winInitMultiWindowWM - DISPLAY=127.0.0.1:0.0 winMultiWindowXMsgProc - pthread_mutex_unlock () returned. winMultiWindowXMsgProc - DISPLAY=127.0.0.1:0.0 winProcEstablishConnection - Hello winInitClipboard () winProcEstablishConnection - winInitClipboard returned. winInitMultiWindowWM - XOpenDisplay () returned and successfully opened the display. winClipboardProc - Hello DetectUnicodeSupport - Windows XP winClipboardProc - DISPLAY=127.0.0.1:0.0 winMultiWindowXMsgProc - XOpenDisplay () returned and successfully opened the display. winClipboardProc - XOpenDisplay () returned and successfully opened the display. Here is the PuTTY event log: 2007-07-24 09:53:57 Looking up host x.x.x.x 2007-07-24 09:53:57 Connecting to x.x.x.x port 22 2007-07-24 09:53:57 Server version: SSH-2.0-OpenSSH_4.5p1 FreeBSD-20061110 2007-07-24 09:53:57 We claim version: SSH-2.0-PuTTY_Snapshot_2005_05_03:r5737 2007-07-24 09:53:57 Using SSH protocol version 2 2007-07-24 09:53:57 Doing Diffie-Hellman group exchange 2007-07-24 09:53:57 Doing Diffie-Hellman key exchange 2007-07-24 09:53:57 Host key fingerprint is: 2007-07-24 09:53:57 ssh-dss 1024 06:2a:c4:9c:e7:6a:f8:0d:5a:17:e9:b0:e3:79:1c:a5 2007-07-24 09:53:57 Initialised AES-256 SDCTR client-server encryption 2007-07-24 09:53:57 Initialised HMAC-SHA1 client-server MAC algorithm 2007-07-24 09:53:57 Initialised AES-256 SDCTR server-client encryption 2007-07-24 09:53:57 Initialised HMAC-SHA1 server-client MAC algorithm 2007-07-24 09:54:06 Access granted 2007-07-24 09:54:06 Opened channel for session 2007-07-24 09:54:06 Requesting X11 forwarding 2007-07-24 09:54:06 X11 forwarding enabled 2007-07-24 09:54:06 Allocated pty (ospeed 38400bps, ispeed 38400bps) 2007-07-24 09:54:06 Started a shell/command 2007-07-24 09:54:17 Received X11 connect request from 127.0.0.1:53737 2007-07-24 09:54:17 Opening X11 forward connection succeeded 2007-07-24 09:54:17 Forwarded
Re: ssh X11 forwarding not working on FreeBSD 6.2
On Tue, 2007-07-24 at 10:59 -0500, Terry Todd wrote: I have installed Xming successfully on a Windows XP system. It works OK to a FC6 system and an older UNIXware system. However when trying to connect to a FreeBSD 6.2 system with PuTTY ssh it doesn't work. PuTTY has Enable X11 forwarding checked. Here's what I get: $ $ xhost Xlib: connection to localhost:10.0 refused by server Xlib: PuTTY X11 proxy: wrong authentication protocol attempted xhost: unable to open display localhost:10.0 $ What can be wrong? I have ssh configured as follows: # grep X11 /etc/ssh/* /etc/ssh/ssh_config:ForwardX11 yes /etc/ssh/ssh_config:ForwardX11Trusted yes /etc/ssh/sshd_config:X11Forwarding yes /etc/ssh/sshd_config:X11DisplayOffset 10 /etc/ssh/sshd_config:X11UseLocalhost yes Start by changing the following line from X11DisplayOffset 10 to X11DisplayOffset 1 According to the sshd_conf man page, looks like the number should be set to the display that you want to forward (the first available display). Here is the Xming log file: Welcome to the Xming X Server Vendor: Colin Harrison Release: 6.9.0.24 FreeType2: 2.3.0 Contact: http://sourceforge.net/forum/?group_id=156984 C:\Program Files\Xming\Xming.exe :0 -ac -clipboard -multiwindow XdmcpRegisterConnection: newAddress x.x.x.x winPrefsLoadPreferences: C:\Program Files\Xming\Xmingrc LoadPreferences: Done parsing the configuration file... winAdjustVideoModeShadowGDI - Using Windows display depth of 32 bits per pixel winAllocateFBShadowGDI - Creating DIB with width: 1600 height: 1200 depth: 32 winInitVisualsShadowGDI - Masks 00ff ff00 00ff BPRGB 8 d 24 bpp 32 glWinInitVisuals:1511: glWinInitVisuals init_visuals:1055: init_visuals null screen fn ReparentWindow null screen fn RestackWindow InitQueue - Calling pthread_mutex_init InitQueue - pthread_mutex_init returned InitQueue - Calling pthread_cond_init InitQueue - pthread_cond_init returned winInitMultiWindowWM - Hello winInitMultiWindowWM - Calling pthread_mutex_lock () winMultiWindowXMsgProc - Hello winMultiWindowXMsgProc - Calling pthread_mutex_lock () glWinScreenProbe:1390: glWinScreenProbe fixup_visuals:1303: fixup_visuals init_screen_visuals:1336: init_screen_visuals (--) 5 mouse buttons found (--) Setting autorepeat to delay=500, rate=31 (--) winConfigKeyboard - Layout: 0409 (0409) (--) Using preset keyboard for English (USA) (409), type 4 Could not init font path element C:\Program Files\Xming/fonts/misc/, removing from list! Could not init font path element C:\Program Files\Xming/fonts/TTF/, removing from list! Could not init font path element C:\Program Files\Xming/fonts/Type1/, removing from list! Could not init font path element C:\Program Files\Xming/fonts/75dpi/, removing from list! Could not init font path element C:\Program Files\Xming/fonts/100dpi/, removing from list! Could not init font path element C:\Program Files\Xming\fonts\dejavu, removing from list! Could not init font path element C:\Program Files\Xming\fonts\cyrillic, removing from list! Could not init font path element C:\WINDOWS\Fonts, removing from list! winInitMultiWindowWM - pthread_mutex_lock () returned. winInitMultiWindowWM - pthread_mutex_unlock () returned. winMultiWindowXMsgProc - pthread_mutex_lock () returned. winInitMultiWindowWM - DISPLAY=127.0.0.1:0.0 winMultiWindowXMsgProc - pthread_mutex_unlock () returned. winMultiWindowXMsgProc - DISPLAY=127.0.0.1:0.0 winProcEstablishConnection - Hello winInitClipboard () winProcEstablishConnection - winInitClipboard returned. winInitMultiWindowWM - XOpenDisplay () returned and successfully opened the display. winClipboardProc - Hello DetectUnicodeSupport - Windows XP winClipboardProc - DISPLAY=127.0.0.1:0.0 winMultiWindowXMsgProc - XOpenDisplay () returned and successfully opened the display. winClipboardProc - XOpenDisplay () returned and successfully opened the display. Here is the PuTTY event log: 2007-07-24 09:53:57 Looking up host x.x.x.x 2007-07-24 09:53:57 Connecting to x.x.x.x port 22 2007-07-24 09:53:57 Server version: SSH-2.0-OpenSSH_4.5p1 FreeBSD-20061110 2007-07-24 09:53:57 We claim version: SSH-2.0-PuTTY_Snapshot_2005_05_03:r5737 2007-07-24 09:53:57 Using SSH protocol version 2 2007-07-24 09:53:57 Doing Diffie-Hellman group exchange 2007-07-24 09:53:57 Doing Diffie-Hellman key exchange 2007-07-24 09:53:57 Host key fingerprint is: 2007-07-24 09:53:57 ssh-dss 1024 06:2a:c4:9c:e7:6a:f8:0d:5a:17:e9:b0:e3:79:1c:a5 2007-07-24 09:53:57 Initialised AES-256 SDCTR client-server encryption 2007-07-24 09:53:57 Initialised HMAC-SHA1 client-server MAC algorithm 2007-07-24 09:53:57 Initialised AES-256 SDCTR server-client encryption 2007-07-24 09:53:57 Initialised HMAC-SHA1 server-client MAC algorithm 2007-07-24 09:54:06 Access granted 2007-07-24
Re: ssh X11 forwarding not working on FreeBSD 6.2
On Tue, Jul 24, 2007 at 09:48:05AM -0700, Michael S. Eubanks wrote: ... Start by changing the following line from X11DisplayOffset 10 to X11DisplayOffset 1 ... OK, I tried that. No difference. Here's what heppened on the FreeBSD 6.2 system: $ $ echo $DISPLAY localhost:1.0 $ $ xhost Xlib: connection to localhost:1.0 refused by server Xlib: PuTTY X11 proxy: wrong authentication protocol attempted xhost: unable to open display localhost:1.0 $ $ xhost + Xlib: connection to localhost:1.0 refused by server Xlib: PuTTY X11 proxy: wrong authentication protocol attempted xhost: unable to open display localhost:1.0 $ xterm Xlib: connection to localhost:1.0 refused by server Xlib: PuTTY X11 proxy: wrong authentication protocol attempted xterm Xt error: Can't open display: localhost:1.0 $ Here's what happens on the FC6 system: $ echo $DISPLAY localhost:13.0 $ $ xhost access control disabled, clients can connect from any host INET:terry-pc.egizone.com LOCAL: $ Terry Todd On Tue, Jul 24, 2007 at 09:48:05AM -0700, Michael S. Eubanks wrote: On Tue, 2007-07-24 at 10:59 -0500, Terry Todd wrote: I have installed Xming successfully on a Windows XP system. It works OK to a FC6 system and an older UNIXware system. However when trying to connect to a FreeBSD 6.2 system with PuTTY ssh it doesn't work. PuTTY has Enable X11 forwarding checked. Here's what I get: $ $ xhost Xlib: connection to localhost:10.0 refused by server Xlib: PuTTY X11 proxy: wrong authentication protocol attempted xhost: unable to open display localhost:10.0 $ What can be wrong? I have ssh configured as follows: # grep X11 /etc/ssh/* /etc/ssh/ssh_config:ForwardX11 yes /etc/ssh/ssh_config:ForwardX11Trusted yes /etc/ssh/sshd_config:X11Forwarding yes /etc/ssh/sshd_config:X11DisplayOffset 10 /etc/ssh/sshd_config:X11UseLocalhost yes Start by changing the following line from X11DisplayOffset 10 to X11DisplayOffset 1 According to the sshd_conf man page, looks like the number should be set to the display that you want to forward (the first available display). Here is the Xming log file: Welcome to the Xming X Server Vendor: Colin Harrison Release: 6.9.0.24 FreeType2: 2.3.0 Contact: http://sourceforge.net/forum/?group_id=156984 C:\Program Files\Xming\Xming.exe :0 -ac -clipboard -multiwindow XdmcpRegisterConnection: newAddress x.x.x.x winPrefsLoadPreferences: C:\Program Files\Xming\Xmingrc LoadPreferences: Done parsing the configuration file... winAdjustVideoModeShadowGDI - Using Windows display depth of 32 bits per pixel winAllocateFBShadowGDI - Creating DIB with width: 1600 height: 1200 depth: 32 winInitVisualsShadowGDI - Masks 00ff ff00 00ff BPRGB 8 d 24 bpp 32 glWinInitVisuals:1511: glWinInitVisuals init_visuals:1055: init_visuals null screen fn ReparentWindow null screen fn RestackWindow InitQueue - Calling pthread_mutex_init InitQueue - pthread_mutex_init returned InitQueue - Calling pthread_cond_init InitQueue - pthread_cond_init returned winInitMultiWindowWM - Hello winInitMultiWindowWM - Calling pthread_mutex_lock () winMultiWindowXMsgProc - Hello winMultiWindowXMsgProc - Calling pthread_mutex_lock () glWinScreenProbe:1390: glWinScreenProbe fixup_visuals:1303: fixup_visuals init_screen_visuals:1336: init_screen_visuals (--) 5 mouse buttons found (--) Setting autorepeat to delay=500, rate=31 (--) winConfigKeyboard - Layout: 0409 (0409) (--) Using preset keyboard for English (USA) (409), type 4 Could not init font path element C:\Program Files\Xming/fonts/misc/, removing from list! Could not init font path element C:\Program Files\Xming/fonts/TTF/, removing from list! Could not init font path element C:\Program Files\Xming/fonts/Type1/, removing from list! Could not init font path element C:\Program Files\Xming/fonts/75dpi/, removing from list! Could not init font path element C:\Program Files\Xming/fonts/100dpi/, removing from list! Could not init font path element C:\Program Files\Xming\fonts\dejavu, removing from list! Could not init font path element C:\Program Files\Xming\fonts\cyrillic, removing from list! Could not init font path element C:\WINDOWS\Fonts, removing from list! winInitMultiWindowWM - pthread_mutex_lock () returned. winInitMultiWindowWM - pthread_mutex_unlock () returned. winMultiWindowXMsgProc - pthread_mutex_lock () returned. winInitMultiWindowWM - DISPLAY=127.0.0.1:0.0 winMultiWindowXMsgProc - pthread_mutex_unlock () returned. winMultiWindowXMsgProc - DISPLAY=127.0.0.1:0.0 winProcEstablishConnection - Hello winInitClipboard () winProcEstablishConnection - winInitClipboard returned. winInitMultiWindowWM - XOpenDisplay () returned and successfully opened the display. winClipboardProc - Hello
Re: ssh X11 forwarding not working on FreeBSD 6.2
On Tue, 2007-07-24 at 12:23 -0500, Terry Todd wrote: On Tue, Jul 24, 2007 at 09:48:05AM -0700, Michael S. Eubanks wrote: ... Start by changing the following line from X11DisplayOffset 10 to X11DisplayOffset 1 ... OK, I tried that. No difference. Here's what heppened on the FreeBSD 6.2 system: $ $ echo $DISPLAY localhost:1.0 $ $ xhost Xlib: connection to localhost:1.0 refused by server Xlib: PuTTY X11 proxy: wrong authentication protocol attempted xhost: unable to open display localhost:1.0 $ $ xhost + Xlib: connection to localhost:1.0 refused by server Xlib: PuTTY X11 proxy: wrong authentication protocol attempted xhost: unable to open display localhost:1.0 $ xterm Xlib: connection to localhost:1.0 refused by server Xlib: PuTTY X11 proxy: wrong authentication protocol attempted xterm Xt error: Can't open display: localhost:1.0 $ Question. How many X servers do you have running? Are you logged into a window manager when you are attempting to connect? Here's what happens on the FC6 system: $ echo $DISPLAY localhost:13.0 $ $ xhost access control disabled, clients can connect from any host INET:terry-pc.egizone.com LOCAL: $ Terry Todd On Tue, Jul 24, 2007 at 09:48:05AM -0700, Michael S. Eubanks wrote: On Tue, 2007-07-24 at 10:59 -0500, Terry Todd wrote: I have installed Xming successfully on a Windows XP system. It works OK to a FC6 system and an older UNIXware system. However when trying to connect to a FreeBSD 6.2 system with PuTTY ssh it doesn't work. PuTTY has Enable X11 forwarding checked. Here's what I get: $ $ xhost Xlib: connection to localhost:10.0 refused by server Xlib: PuTTY X11 proxy: wrong authentication protocol attempted xhost: unable to open display localhost:10.0 $ What can be wrong? I have ssh configured as follows: # grep X11 /etc/ssh/* /etc/ssh/ssh_config:ForwardX11 yes /etc/ssh/ssh_config:ForwardX11Trusted yes /etc/ssh/sshd_config:X11Forwarding yes /etc/ssh/sshd_config:X11DisplayOffset 10 /etc/ssh/sshd_config:X11UseLocalhost yes Start by changing the following line from X11DisplayOffset 10 to X11DisplayOffset 1 According to the sshd_conf man page, looks like the number should be set to the display that you want to forward (the first available display). Here is the Xming log file: Welcome to the Xming X Server Vendor: Colin Harrison Release: 6.9.0.24 FreeType2: 2.3.0 Contact: http://sourceforge.net/forum/?group_id=156984 C:\Program Files\Xming\Xming.exe :0 -ac -clipboard -multiwindow XdmcpRegisterConnection: newAddress x.x.x.x winPrefsLoadPreferences: C:\Program Files\Xming\Xmingrc LoadPreferences: Done parsing the configuration file... winAdjustVideoModeShadowGDI - Using Windows display depth of 32 bits per pixel winAllocateFBShadowGDI - Creating DIB with width: 1600 height: 1200 depth: 32 winInitVisualsShadowGDI - Masks 00ff ff00 00ff BPRGB 8 d 24 bpp 32 glWinInitVisuals:1511: glWinInitVisuals init_visuals:1055: init_visuals null screen fn ReparentWindow null screen fn RestackWindow InitQueue - Calling pthread_mutex_init InitQueue - pthread_mutex_init returned InitQueue - Calling pthread_cond_init InitQueue - pthread_cond_init returned winInitMultiWindowWM - Hello winInitMultiWindowWM - Calling pthread_mutex_lock () winMultiWindowXMsgProc - Hello winMultiWindowXMsgProc - Calling pthread_mutex_lock () glWinScreenProbe:1390: glWinScreenProbe fixup_visuals:1303: fixup_visuals init_screen_visuals:1336: init_screen_visuals (--) 5 mouse buttons found (--) Setting autorepeat to delay=500, rate=31 (--) winConfigKeyboard - Layout: 0409 (0409) (--) Using preset keyboard for English (USA) (409), type 4 Could not init font path element C:\Program Files\Xming/fonts/misc/, removing from list! Could not init font path element C:\Program Files\Xming/fonts/TTF/, removing from list! Could not init font path element C:\Program Files\Xming/fonts/Type1/, removing from list! Could not init font path element C:\Program Files\Xming/fonts/75dpi/, removing from list! Could not init font path element C:\Program Files\Xming/fonts/100dpi/, removing from list! Could not init font path element C:\Program Files\Xming\fonts\dejavu, removing from list! Could not init font path element C:\Program Files\Xming\fonts\cyrillic, removing from list! Could not init font path element C:\WINDOWS\Fonts, removing from list! winInitMultiWindowWM - pthread_mutex_lock () returned. winInitMultiWindowWM - pthread_mutex_unlock () returned. winMultiWindowXMsgProc - pthread_mutex_lock () returned. winInitMultiWindowWM - DISPLAY=127.0.0.1:0.0 winMultiWindowXMsgProc -
Re: ssh X11 forwarding not working on FreeBSD 6.2
On Tue, Jul 24, 2007 at 10:54:22AM -0700, Michael S. Eubanks wrote: ... Question. How many X servers do you have running? Are you logged into a window manager when you are attempting to connect? Only one instance of Xming is running on the Windows XP system. I am using PuTTY to connect to the FreeBSD system and the other systems. The other systems all work. FreeBSD X11 forwarding does not work. It is an off the shelf standard install of 6.2. Manually setting the DISPLAY variable on the FreeBSD system to [IP address of Widows XP system]:0.0 will allow it to work but that's not what I want to do here. I want it to automatically forward the X11 session through ssh like it does when connecting to the FC6 system. Terry Todd On Tue, Jul 24, 2007 at 10:54:22AM -0700, Michael S. Eubanks wrote: On Tue, 2007-07-24 at 12:23 -0500, Terry Todd wrote: On Tue, Jul 24, 2007 at 09:48:05AM -0700, Michael S. Eubanks wrote: ... Start by changing the following line from X11DisplayOffset 10 to X11DisplayOffset 1 ... OK, I tried that. No difference. Here's what heppened on the FreeBSD 6.2 system: $ $ echo $DISPLAY localhost:1.0 $ $ xhost Xlib: connection to localhost:1.0 refused by server Xlib: PuTTY X11 proxy: wrong authentication protocol attempted xhost: unable to open display localhost:1.0 $ $ xhost + Xlib: connection to localhost:1.0 refused by server Xlib: PuTTY X11 proxy: wrong authentication protocol attempted xhost: unable to open display localhost:1.0 $ xterm Xlib: connection to localhost:1.0 refused by server Xlib: PuTTY X11 proxy: wrong authentication protocol attempted xterm Xt error: Can't open display: localhost:1.0 $ Question. How many X servers do you have running? Are you logged into a window manager when you are attempting to connect? Here's what happens on the FC6 system: $ echo $DISPLAY localhost:13.0 $ $ xhost access control disabled, clients can connect from any host INET:terry-pc.egizone.com LOCAL: $ Terry Todd On Tue, Jul 24, 2007 at 09:48:05AM -0700, Michael S. Eubanks wrote: On Tue, 2007-07-24 at 10:59 -0500, Terry Todd wrote: I have installed Xming successfully on a Windows XP system. It works OK to a FC6 system and an older UNIXware system. However when trying to connect to a FreeBSD 6.2 system with PuTTY ssh it doesn't work. PuTTY has Enable X11 forwarding checked. Here's what I get: $ $ xhost Xlib: connection to localhost:10.0 refused by server Xlib: PuTTY X11 proxy: wrong authentication protocol attempted xhost: unable to open display localhost:10.0 $ What can be wrong? I have ssh configured as follows: # grep X11 /etc/ssh/* /etc/ssh/ssh_config:ForwardX11 yes /etc/ssh/ssh_config:ForwardX11Trusted yes /etc/ssh/sshd_config:X11Forwarding yes /etc/ssh/sshd_config:X11DisplayOffset 10 /etc/ssh/sshd_config:X11UseLocalhost yes Start by changing the following line from X11DisplayOffset 10 to X11DisplayOffset 1 According to the sshd_conf man page, looks like the number should be set to the display that you want to forward (the first available display). Here is the Xming log file: Welcome to the Xming X Server Vendor: Colin Harrison Release: 6.9.0.24 FreeType2: 2.3.0 Contact: http://sourceforge.net/forum/?group_id=156984 C:\Program Files\Xming\Xming.exe :0 -ac -clipboard -multiwindow XdmcpRegisterConnection: newAddress x.x.x.x winPrefsLoadPreferences: C:\Program Files\Xming\Xmingrc LoadPreferences: Done parsing the configuration file... winAdjustVideoModeShadowGDI - Using Windows display depth of 32 bits per pixel winAllocateFBShadowGDI - Creating DIB with width: 1600 height: 1200 depth: 32 winInitVisualsShadowGDI - Masks 00ff ff00 00ff BPRGB 8 d 24 bpp 32 glWinInitVisuals:1511: glWinInitVisuals init_visuals:1055: init_visuals null screen fn ReparentWindow null screen fn RestackWindow InitQueue - Calling pthread_mutex_init InitQueue - pthread_mutex_init returned InitQueue - Calling pthread_cond_init InitQueue - pthread_cond_init returned winInitMultiWindowWM - Hello winInitMultiWindowWM - Calling pthread_mutex_lock () winMultiWindowXMsgProc - Hello winMultiWindowXMsgProc - Calling pthread_mutex_lock () glWinScreenProbe:1390: glWinScreenProbe fixup_visuals:1303: fixup_visuals init_screen_visuals:1336: init_screen_visuals (--) 5 mouse buttons found (--) Setting autorepeat to delay=500, rate=31 (--) winConfigKeyboard - Layout: 0409 (0409) (--) Using preset keyboard for English (USA) (409), type 4 Could not init font path element C:\Program Files\Xming/fonts/misc/, removing from
Re: ssh X11 forwarding not working on FreeBSD 6.2
I would guess that it's an xauth(1) problem. Make sure that XAuthLocation is set ,in sshd_config(5), to the right path for the xauth executable (probably /usr/local/bin/xauth, if you've done the update to X.Org 7.2. That's just a shot in the dark, though; the most certain way of finding the problem is to increase the verbosity of sshd's logging, and see what it thinks is wrong. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ssh X11 forwarding not working on FreeBSD 6.2
Lowell, The default sshd_config file does not have XAuthLocation defined. I have not done any updates to X.org so the default location for xauth is /usr/X11R6/bin/xauth. So, I added the line: XAuthLocation /usr/X11R6/bin/xauth to /etc/ssh/sshd_config restarted sshd Tested it out and same problem. BTW - the sshd_config file on FC6 does not have this line either and it works. I increased sshd logging to -d3. No more messages came up in the log file than before. Terry Todd On Tue, Jul 24, 2007 at 02:30:59PM -0400, Lowell Gilbert wrote: I would guess that it's an xauth(1) problem. Make sure that XAuthLocation is set ,in sshd_config(5), to the right path for the xauth executable (probably /usr/local/bin/xauth, if you've done the update to X.Org 7.2. That's just a shot in the dark, though; the most certain way of finding the problem is to increase the verbosity of sshd's logging, and see what it thinks is wrong. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ssh X11 forwarding not working on FreeBSD 6.2
On Tuesday 24 July 2007 15:59:22 Terry Todd wrote: I have installed Xming successfully on a Windows XP system. It works OK to a FC6 system and an older UNIXware system. However when trying to connect to a FreeBSD 6.2 system with PuTTY ssh it doesn't work. PuTTY has Enable X11 forwarding checked. When I saw this post, I thought it was mine, because I am having the same problem, but only in FreeBSD and not Linux and my configurations on both are very much the same (for sshd). I am also unable to use port forwarding in vnc (fbsd 6.2) but I am not certain whether this is related to the X11 Forwarding issue or if it is something unrelated. SSH complains that it cannot use the designated port (I have tried different ports. BTW I can do SSH port forwarding from my fbsd computer (client) to Linux (server) but cannot do this from Linux to fbsd. I changed X11DisplayOffset 10 to X11DisplayOffset 1 as mentioned in another post in this thread but that did not help. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ssh X11 forwarding not working on FreeBSD 6.2
On Tuesday 24 July 2007 18:30:59 Lowell Gilbert wrote: I would guess that it's an xauth(1) problem. Make sure that XAuthLocation is set ,in sshd_config(5), to the right path for the xauth executable (probably /usr/local/bin/xauth, if you've done the update to X.Org 7.2. That's just a shot in the dark, though; the most certain way of finding the problem is to increase the verbosity of sshd's logging, and see what it thinks is wrong. Indeed, setting XAuthLocation is what allowed me to connect FROM fbsd to Linux but I still can't connect from Linux to my FreeBSD computer. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ssh X11 forwarding not working on FreeBSD 6.2
On Tuesday 24 July 2007, Pollywog wrote: On Tuesday 24 July 2007 15:59:22 Terry Todd wrote: I have installed Xming successfully on a Windows XP system. It works OK to a FC6 system and an older UNIXware system. However when trying to connect to a FreeBSD 6.2 system with PuTTY ssh it doesn't work. PuTTY has Enable X11 forwarding checked. When I saw this post, I thought it was mine, because I am having the same problem, but only in FreeBSD and not Linux and my configurations on both are very much the same (for sshd). I am also unable to use port forwarding in vnc (fbsd 6.2) but I am not certain whether this is related to the X11 Forwarding issue or if it is something unrelated. SSH complains that it cannot use the designated port (I have tried different ports. BTW I can do SSH port forwarding from my fbsd computer (client) to Linux (server) but cannot do this from Linux to fbsd. I changed X11DisplayOffset 10 to X11DisplayOffset 1 as mentioned in another post in this thread but that did not help. Is tcp listening still off by default on FreeBSD? Last time I tried to do anything with remote X (which was ages ago) I had to find the goo that was disabling it, I think it was tcp nolisten or something in the startx script. Mind you we are talking FBSD 4.x here, but the errors seem very familiar. -- Thanks, Josh Paetzel pgpisQvtvRXq2.pgp Description: PGP signature
