On 09/16/2009 01:46 AM, Michael Semcheski wrote:
I think getting Samba setup is potentially difficult - you don't
describe it in enough depth to say what exactly the problem is (my
guess - you need to access the machine by using its DNS name or IP
address, the "browsing the network neighborhood" doesn't even work all
the time on a properly configured Windows network.)
However, if its a relatively small amount of traffic between Linux
machines, I would be more inclined to use ssh / scp / sftp. It takes
a little effort to setup (generate RSA keys, copy the public key to
the other machine*, etc.) It is very convenient once its setup. You
can also use something like filezilla, winscp, or best of all sshfs.
* something like the following works:
cat .ssh/id_rsa.pub | ssh u...@othermachine "cat - >>
.ssh/authorized_keys"
On Tue, Sep 15, 2009 at 6:36 PM, DB <[email protected]
<mailto:[email protected]>> wrote:
On 09/15/2009 11:56 PM, Steve Searle wrote:
Around 10:34pm on Tuesday, September 15, 2009 (UK time), DB
scrawled:
Thanks Michael,
It turns out I have an installed Firewall I wasn't aware of which had to
be opened for Samba & Client, and that the smb & nmb services were
disabled.... So at least I can see all the attached machines now.
I'll take a look at ssh & co.
Thanks again
Dave
--
fedora-list mailing list
[email protected]
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
