Duke-UNC Brain Imaging and Analysis Center
BIAC Forums | Profile | Register | Active Topics | Members | Search | FAQ
 All Forums
 Support Forums
 Unix Support
 ADW openssh and samba installations

Note: You must be registered in order to post a reply.
To register, click here. Registration is FREE!

Screensize:
UserName:
Password:
Format Mode:
Format: BoldItalicizedUnderlineStrikethrough Align LeftCenteredAlign Right Horizontal Rule Insert HyperlinkInsert EmailInsert Image Insert CodeInsert QuoteInsert List
   
Message:

* HTML is OFF
* Forum Code is ON
Smilies
Smile [:)] Big Smile [:D] Cool [8D] Blush [:I]
Tongue [:P] Evil [):] Wink [;)] Clown [:o)]
Black Eye [B)] Eight Ball [8] Frown [:(] Shy [8)]
Shocked [:0] Angry [:(!] Dead [xx(] Sleepy [|)]
Kisses [:X] Approve [^] Disapprove [V] Question [?]

 
Check here to subscribe to this topic.
   

T O P I C    R E V I E W
jimmy.dias Posted - Mar 13 2003 : 4:12:08 PM
Hey all,

I installed openssh 3.5p1 on both the ADWs (mrws-mr5 and mrws-mr6). This package includes sftp, ssh and scp.

I had also installed smbclient on both machines some time ago. You can use either smbclient or sftp to transfer files from the ADW to Bristol. (note: scp will not work with Bristol!).

Enjoy!
Jimmy
1   L A T E S T    R E P L I E S    (Newest First)
jimmy.dias Posted - Mar 17 2003 : 4:26:14 PM
A little clarification with the 'scp will not work with bristol'...

All of the F-Secure versions of SSH 2.x and greater use the sftp subsystem for scp requests, while those from the 1.x versions use two copies of scp talking to each other. This is how rcp does it and its how OpenSSH still does it.

For those of you using Linux or Windows distributions, F-Secure (http://www.f-secure.com) may have the client binaries freely available. Francis verified that these binaries do work with Bristol (at least for Windows)

Oh, and just for completeness sake, I tried using scp with the -1 option but SSH1 is not supported on the server side.

debug1: Remote protocol version 2.0, remote software version 3.2.0 F-Secure SSH Windows NT Server
debug1: no match: 3.2.0 F-Secure SSH Windows NT Server
Protocol major versions differ: 1 vs. 2
debug1: Calling cleanup 0x80674b0(0x0)

Hope that helps!
Jimmy

BIAC Forums © 2000-2010 Brain Imaging and Analysis Center Go To Top Of Page
This page was generated in 0.36 seconds. Snitz Forums 2000