After ALOT of horsing around with this issue and trying to understand how all of
this works, I finally zeroed in on my own problem which was, after all,
documented somewhere.
The issue is that the DISPLAY parameter CANNOT be set in any login shells on the
remote X-client, EVEN IF IT IS THE SAME
BZAG bzag0 at yahoo.com writes:
The other related factoid is that all of this still comes over on port 6000.
The fact that localhost:10 is used is neither here nor there as far as the
port
is concerned because the tunnel is already established before you logon.
Anyone who plays
I believe Windows Firewall has a setting for applications. Some PC firewalls do
(the one I have does), meaning if the executable changes you have to tell the
firewall it's ok for it to go again.
Even though your post indicates it is failing at startup, the error is reporting
socket access
BZAG bzag0 at yahoo.com writes:
Addendum: The X Server works locally using a local X Client xterm session. I
only have issues when it has to go out to the network.
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
I am trying to use a W2K laptop to run Cygwin/X but I keep getting a connection
refused, xlib no protocol error when I try to run remote windows by SSH into
BSD/Linux boxes. So I tried to setup Cygwin/X on my W2K PC, another box, which
had a MI/X server. I have no problem with MI/X - I always get
5 matches
Mail list logo
