Re: SSH problem after upgrade - SOLVED

2005-12-23 Thread J. David Boyd
Ed Brady <[EMAIL PROTECTED]> writes: > Ed Brady wrote: > >> Igor Pechtchanski wrote: > >>> IIRC, the Windows dynamic loader will first look for DLLs in the >>> application directory, and only then in the PATH. Here's a WAG: do you >>> have a copy of winsock.dll or ws2_32.dll in /usr/bin? >>> >>>

Re: SSH problem after upgrade - SOLVED

2005-12-23 Thread Igor Peshansky
On Fri, 23 Dec 2005, Ed Brady wrote: > Ed Brady wrote: > > > Igor Pechtchanski wrote: > > > > IIRC, the Windows dynamic loader will first look for DLLs in the > > > application directory, and only then in the PATH. Here's a WAG: do you > > > have a copy of winsock.dll or ws2_32.dll in /usr/bin? >

Re: SSH problem after upgrade - SOLVED

2005-12-22 Thread Ed Brady
Ed Brady wrote: Igor Pechtchanski wrote: IIRC, the Windows dynamic loader will first look for DLLs in the application directory, and only then in the PATH. Here's a WAG: do you have a copy of winsock.dll or ws2_32.dll in /usr/bin? The problem is now solved. The culprit is due to the

Re: SSH problem after upgrade

2005-12-21 Thread Ed Brady
[ The following attachment was DELETED when this message was saved:] [ A Text/HTML segment of about 2,921 bytes.]

Re: SSH problem after upgrade

2005-12-21 Thread Ed Brady
Igor Pechtchanski wrote: That's not what I asked (though I can see how it can be misread). Let me try again: if you copy telnet.exe into your home directory, *leave* /usr/bin/telnet.exe in place, and then invoke the telnet in your home directory as /home/Ed/telnet.exe, does it still work for yo

Re: SSH problem after upgrade

2005-12-21 Thread Igor Pechtchanski
Ed, there was no need to Cc: me -- I read the list. Please make sure your mailer respects the Reply-To: header, which I set appropriately. On Wed, 21 Dec 2005, Ed Brady wrote: > Igor Pechtchanski wrote: > > > Does it help if you leave the files in /usr/bin, but explicitly > > specify the path to

Re: SSH problem after upgrade

2005-12-21 Thread Igor Pechtchanski
On Wed, 21 Dec 2005, Ed Brady wrote: > > Ed Brady wrote: > > > > > After upgrading to the latest release of cygwin, I am continually > > > receiving the error message. > > > > > > socket: Operation not permitted > > > ssh: connect to host port 22: Operation not permitted > > > > > > I have had C

Re: SSH problem after upgrade

2005-12-21 Thread Ed Brady
Steve Holden wrote: Ed Brady wrote: After upgrading to the latest release of cygwin, I am continually receiving the error message. socket: Operation not permitted ssh: connect to host port 22: Operation not permitted I have had Cygwin installed on this computer for over three years and h

Re: SSH problem after upgrade

2005-12-21 Thread Steve Holden
Ed Brady wrote: After upgrading to the latest release of cygwin, I am continually receiving the error message. socket: Operation not permitted ssh: connect to host port 22: Operation not permitted I have had Cygwin installed on this computer for over three years and have used ssh reguarly w

Re: SSH problem after upgrade

2005-12-20 Thread Larry Hall (Cygwin)
Ed Brady wrote: After upgrading to the latest release of cygwin, I am continually receiving the error message. socket: Operation not permitted ssh: connect to host port 22: Operation not permitted I have had Cygwin installed on this computer for over three years and have used ssh reguarly w