"unable to open display" in 7/2 build

[Suhaib Siddiqi]

There are several threads about Aventail.  It won't work with Aventail.
This is Aventail problem, they do not let X connect to socket even it is a
local client.  We cannot help you with it.  File a complain with Aventail
tech support.  The actual problem (in my words crap) is in their AUTOSOCK
code which force to direct all the TCP connection to their SOCK even when
Aventail is not running.

All you can do replace Avetail with some better software like CheckPoint
SecuRemote, for example.

Suhaib

-----Original Message-----
From: James E. LaBarre [ mailto:jamesl@bestweb.net ] 
Sent: Friday, July 06, 2001 3:23 PM
To: 'cygwin-xfree@xfree.cygwin.com'
Subject: Re: "unable to open display" in 7/2 build

The .sh script had the DISPLAY command already, and was what one thing I
was trying (mapping explicitly to my actual IP number, trying a
different Screen#, etc.)

However, your hint of the firewall software sounds just right.  I *used*
to have Aventail on this machine, and currently have Hummingbird Socks
(and I'm not confident that Aventail completely uninstalled).  So I will
need to try this on my wife's machine at home (Win98 rather than
Win2K).  Which is fine, as that is where I wanted to install it anyway
(was just trying it out on my company machine first).  Later I'll track
down an unmodified winsock.dll for this machine (my desktop machine
already has Aventail in it's Win2k configuration, although I haven't
booted it to Windows in months).  I'll report back later.

BTW: in the mail list archives, the message I needed to look at is
listed as ""Can't open display"", which is what I think kept
ht//dig from finding it.



Suhaib Siddiqi wrote:
> 
> Edit your startxwin.sh and add as first line
> 
> export DISPLAY=127.0.0.1:0.0
> 
> By the way if you have a VPN or firewall software, then read FAQ and mail
> archive