On 12/08/2015 15:23, Kai Hartrampf wrote:
Hello,
I'm located in China, Guangzhou and cannot connect for some reason.
I usually use IPSec, it works very well for me.
Please see the Log below, it says that I should report this problem to
this mail.
I have already downloaded and re-inst
Hello,
I'm located in China, Guangzhou and cannot connect for some reason.
I usually use IPSec, it works very well for me.
Please see the Log below, it says that I should report this problem to
this mail.
I have already downloaded and re-installed the newest version of my VPN,
but it
Please ignore/delete this - I realise this has nothing to do with the
change from 32 to 64 bit.
It has always been a problem, which I have a wrapper script to work
round (I'd forgotten to install the wrapper after the upgrade).
Apologies for a mis-post!
--
Problem reports: http://cygwin.co
On Mar 14 21:21, Peter Binney wrote:
> Please ignore/delete this - I realise this has nothing to do with the
> change from 32 to 64 bit.
>
> It has always been a problem, which I have a wrapper script to work
> round (I'd forgotten to install the wrapper after the upgrade).
In tar, the colon in a
I have just "upgraded" to Cygwin 64 bit (from 32 bit) on Windows 8.
With 32 bit, I could do: tar vtf e:/temp/filename.tar
With 64 bit this fails saying: tar: Cannot connect to e: resolve failed
Using cygwin paths it is OK. ie: tar vtf /cygdrive/e/temp/filename.tar
Here is the
From: Tim Beuman Subject: Re: ssh-add cannot connect to authentication
agent
Date: Fri, 18 May 2007 09:11:00 -0700
Haven't been able to nail it down that specific. I ended up modifying
ssh-agent to run as a service under the SYSTEM account rather than as a
background process under the
Haven't been able to nail it down that specific. I ended up modifying
ssh-agent to run as a service under the SYSTEM account rather than as a
background process under the user-account. It worked fine that way, even
with McAfee but like I said, it required a modification of ssh-agent itself.
Ti
Len Giambrone wrote:
> I'm using XP. I disabled everything I could in McAfee, but still no luck.
> Did you figure out what in McAfee was causing the problem in W2K?
>
It's been noted in the past that disabling is often not enough with these
kinds of intrusive (and buggy) programs. I'd recommend
I'm using XP. I disabled everything I could in McAfee, but still no luck.
Did you figure out what in McAfee was causing the problem in W2K?
-Len
Tim Beuman <[EMAIL PROTECTED]> writes:
> I had the same problem on W2K. Seemed to be caused by McAfee. No
> problems with
I had the same problem on W2K. Seemed to be caused by McAfee. No
problems with McAfee on WXP though.
Tim
Len Giambrone wrote:
The agent starts correctly, but I can't get ssh-add to give me anything other
than:
Could not open a connection to your authentication agent.
I'm running the latest C
The agent starts correctly, but I can't get ssh-add to give me anything other
than:
Could not open a connection to your authentication agent.
I'm running the latest Cygwin/packages. The socket is where it's supposed to
be, the env variables are set. I've tried using ssh-agent -a and putting th
Hunter Peress wrote:
> after installing cygwin, i followed all instructions from:
> http://pigtail.net/LRP/printsrv/cygwin-sshd.html
There are lots of sites that purport to tell you how to install sshd on
Cygwin, but this list does not support any of them.
1. Forget everything you read on any no
after installing cygwin, i followed all instructions from:
http://pigtail.net/LRP/printsrv/cygwin-sshd.html
the important ones being to set
variable name is CYGWIN
variable value is ntsec tty
as an env variable in windows, and
to append ;c:\cygwin\bin to the win2k Path var.
so i do this:
$ ssh -vv
after installing cygwin, i followed all instructions from:
http://pigtail.net/LRP/printsrv/cygwin-sshd.html
the important ones being to set
variable name is *CYGWIN
*variable value is *ntsec tty
as an env variable in windows, and
to append **;c:\cygwin\bin to the win2k Path var.
so i do this:
**$
Dave is right, /dev/comX works fine. And it is indeed not fixed in 6.1.
Hans
-Original Message-
From: Dave Korn [mailto:[EMAIL PROTECTED]
Sent: Friday, November 19, 2004 6:10 PM
To: 'Keith Seitz'; Hans Kester
Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject: RE: Cannot
> -Original Message-
> From: insight-owner On Behalf Of Keith Seitz
> Sent: 19 November 2004 16:48
> To: Hans Kester
> On Fri, 2004-11-19 at 05:08, Hans Kester wrote:
> > When I try to connect to my remote target (sh-elf) with the
> serial port
> > (COM1) I get the following error message
At 10:09 AM 1/23/2004, Christopher Faylor you wrote:
>On Thu, Jan 22, 2004 at 10:22:01PM -0800, Curtis Ebert wrote:
>>Hi Christopher,
>>
>>While Googling for a clue on what may be causing my problem, I came across
>>your post 1/12/02 post to the cygwin group about &q
On Thu, Jan 22, 2004 at 10:22:01PM -0800, Curtis Ebert wrote:
>Hi Christopher,
>
>While Googling for a clue on what may be causing my problem, I came across
>your post 1/12/02 post to the cygwin group about "Cannot connect to
>Interix subsystem" whenever trying to run a
t; First start of cygwin opens a DOS window, and the following
> error appears:
> posix: cannot connect to posix subsystem
Any chance that you've MS's Services For Unix installed on that machine ?
> Any hints ?
>From the FAQ:
Details about your Cygwin setup, accomplished b
On Thu, 19 Dec 2002, a12 wrote:
> Hello cygwin gurus,
>
> First start of cygwin opens a DOS window, and the following
> error appears:
> posix: cannot connect to posix subsystem
Any chance that you've MS's Services For Unix installed on that machine ?
> Any hint
Hello cygwin gurus,
First start of cygwin opens a DOS window, and the following
error appears:
posix: cannot connect to posix subsystem
-bash: cd: /home/a12: No such file or directory
a12@RRBACK /usr/bin
$ pwd
/usr/bin
C:\cygwin\usr contains the following directories:
bin, doc, include, info
21 matches
Mail list logo
