From: Jason A. P. <pat...@pc...> - 2004-02-20 19:44:42
|
Jason A. Pattie wrote: > SSH from cygwin works fine. I haven't had any problems with it > whatsoever. However, I don't seem to be able to get scp'd files to > work. Whether it be inside the coLinux environment scp'ing to an > outside server, or from the outside server to the coLinux > environment. It's also just as bad (with only a few bytes > transferred) scp'ing from the Windows/cygwin environment to the > coLinux machine. Don't know what's going on. It seems that most > other networking types work fine (i.e., http, ftp, etc.). I'm attempting to transfer the kernel into the Debian 1GB filesystem. I've tried 'dd if=linux-2.4.24.tar.bz2 | ssh root@colinux tar -C /usr/src -jxf -' as a last ditch effort to maybe uncover whether it's a difference between scp and ssh or not. Apparently, it happens with ssh as well. I noticed an interesting effect, though. It appears that only the first or a few packets are transmitted between the coLinux environment and the Windows environment. Further traffic just ceases. I have no idea what's causing this, either, since existing ssh sessions continue to work. I exited one of my ssh sessions while attempting to do the above tar command, and my ssh session would not completely exit. I had to type '~.' to terminate it and get back to my cygwin prompt. I find it strange that apt-get install's work fine which use HTTP transfers, but scp and/or ssh don't. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. MailScanner thanks transtec Computers for their support. |