Re^4: not able to read remote file from linux machine

What i understand from all the comments is that if my remote file is on Windows client then I need to have samba client running on my machine. But, what if my remote file is on nix box? also let me know do i need to compulsorily have the remote machine username and password. In case it is shared to everyone. Thanks

Comment on Re^4: not able to read remote file from linux machine

Replies are listed 'Best First'.
Re^5: not able to read remote file from linux machine by ikegami (Patriarch) on Nov 11, 2008 at 20:09 UTC
For whatever protocol you pick, you'll need to have a service speaking that protocol on the machine from which you want to fetch a file, and you'll need a client speaking that protocol on the machine doing the fetching. If you wish to use SMB, you'll need a SMB server on the machine with the file and an SMB client on the machine that wants the file. If you wish to use NFS, you'll need a NFS server on the machine with the file and an NFS client on the machine that wants the file. If you wish to use FTP, you'll need a FTP server on the machine with the file and an FTP client on the machine that wants the file. If you wish to use HTTP, you'll need a HTTP server on the machine with the file and an HTTP client on the machine that wants the file. etc. For file sharing protocols, SMB is usually used on Windows machine, Appletalk is usually used on Macs, and NFS is usually used on unix. So far, the discussions has revolved around SMB. The Windows client is called "Client for Microsoft Windows". The Windows server is called "File and Printer sharing for Microsoft Networks". It's my understanding that Samba provides both for unix. This thread has strayed very far from the domain of PerlMonks. System administration is not in PerlMonks purview.	[reply]

Replies are listed 'Best First'.

Re^5: not able to read remote file from linux machine
by ikegami (Patriarch) on Nov 11, 2008 at 20:09 UTC

For whatever protocol you pick, you'll need to have a service speaking that protocol on the machine from which you want to fetch a file, and you'll need a client speaking that protocol on the machine doing the fetching.

If you wish to use SMB, you'll need a SMB server on the machine with the file and an SMB client on the machine that wants the file.
If you wish to use NFS, you'll need a NFS server on the machine with the file and an NFS client on the machine that wants the file.
If you wish to use FTP, you'll need a FTP server on the machine with the file and an FTP client on the machine that wants the file.
If you wish to use HTTP, you'll need a HTTP server on the machine with the file and an HTTP client on the machine that wants the file.
etc.

For file sharing protocols, SMB is usually used on Windows machine, Appletalk is usually used on Macs, and NFS is usually used on unix.

So far, the discussions has revolved around SMB. The Windows client is called "Client for Microsoft Windows". The Windows server is called "File and Printer sharing for Microsoft Networks". It's my understanding that Samba provides both for unix.

This thread has strayed very far from the domain of PerlMonks. System administration is not in PerlMonks purview.

[reply]