Re: Questions from a Total samba Novice.
Hi Martin, I would have had to enabled nfs client if using mount_smbfs, correct? Nopes - stick to using the mount command. Depending on the filesystem you specify (with the -t option), it will call the relevant mount command itself (eg. mount_smbfs, mount_nfs). When I built the system in question, I did not enable nfs capabilities and don't really want to if I can avoid doing so. You don't need it. It sounds like smbclient fits the bill for now, but thanks to all of you for making things more clear. It seems that /usr/ports/net/samba3 gives one a whole boatload of possibilities. Although installing samba will give you smbclient and a load of other things, if you don't need them I wouldn't install it. From what you've previously explained, everything can be done with the (already supplied) mount command. Steve :) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Questions from a Total samba Novice.
Warren Block writes: >Some alternatives have been mentioned, but you might also consider >mount_smbfs(8). I hope I managed to thank each of you who responded as I feel like I know where I need to go next thanks to all the great suggestions. I would have had to enabled nfs client if using mount_smbfs, correct? When I built the system in question, I did not enable nfs capabilities and don't really want to if I can avoid doing so. It sounds like smbclient fits the bill for now, but thanks to all of you for making things more clear. It seems that /usr/ports/net/samba3 gives one a whole boatload of possibilities. Martin McCormick WB5AGZ Stillwater, OK Systems Engineer OSU Information Technology Department Network Operations Group ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Questions from a Total samba Novice.
On Fri, 9 May 2008 16:40:01 +0200 (CEST) Wojciech Puchar <[EMAIL PROTECTED]> wrote: > smbclient connects to any SMB server (be it Windows or unix or > whatever) and perform fetch, upload and other operations from command > line. > > it's good to: > > testing your samba setup (if you need) > fetching/uploading files to windoze from unix, if windoze has folder > sharing enabled. > > > if you need file server for use with windoze - configure smb.conf > properly and run samba with > > smbd_enable="YES" > nmbd_enable="YES" > > > in /etc/rc.conf > > and then by > > /usr/local/etc/rc.d/samba start (or stop/restart) You only need: samba_enable="YES" in the /etc/rc.conf file to make samba start automatically upon reboot, or even if it is started manually for that matter. If you need 'windbindd, that is enabled separately. If you need shares mounted automatically, you can put them in the /etc/fstab file. See the Samba documentation or subscribe to the Samba list. -- Gerard [EMAIL PROTECTED] Did you know that clones never use mirrors? Ambrose Bierce, "The Devil's Dictionary" signature.asc Description: PGP signature
Re: Questions from a Total samba Novice.
On Fri, 9 May 2008, Martin McCormick wrote: I just found out that I will need to copy some files from a FreeBSD system to a Windows shared drive on our network so that Windows users can have access to the files. Some alternatives have been mentioned, but you might also consider mount_smbfs(8). -Warren Block * Rapid City, South Dakota USA ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Questions from a Total samba Novice.
(forgot to send to list the first time) Hi Martin, You don't need samba if all you want to do is copy files from FreeBSD to a Windows system. The easiest way to do it is to mount an existing Windows share, on FreeBSD. This will give you access to the Windows share, but nothing is shared out on your FreeBSD box. Let's assume you have a non-protected share (called MYSHARE) on a Windows server called FRED. Let's also assume you have prepared a mount point on FreeBSD for this share, called /mnt/fred. All you need to do is: $ mount -t smbfs //FRED/MYSHARE /mnt/fred If you need to specify a username/password combo to access the share, try: $ mount -t smbfs //[EMAIL PROTECTED]/MYSHARE /mnt/fred You will need to input a password, but if you want to save the password so it's used automatically, use /etc/nsmb.conf (see the man page), but here's an example. [SNAP-CMS] addr=192.168.0.4 [SNAP-CMS:BACKUP] password=$$14b5d4732371b1c00e5d2f5cd96 The hashed password was created by using 'smbutil crypt' and inputting the real password (see the man page). Obviously you need to make sure the permissions on /etc/nsmb.conf are secure. If you want it to automount at startup, then /etc/fstab could contain: //[EMAIL PROTECTED]/MYSHARE /mnt/fred smbfs rw 0 0 Cheers, Steve :) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Questions from a Total samba Novice.
smbclient(1) The smbclient program implements a simple ftp-like client. This is useful for accessing SMB shares on other compatible servers (such as Windows NT), and can also be used to allow a UNIX box to print to a printer attached to any SMB server (such as a PC running Windows NT). smbclient connects to any SMB server (be it Windows or unix or whatever) and perform fetch, upload and other operations from command line. it's good to: testing your samba setup (if you need) fetching/uploading files to windoze from unix, if windoze has folder sharing enabled. if you need file server for use with windoze - configure smb.conf properly and run samba with smbd_enable="YES" nmbd_enable="YES" in /etc/rc.conf and then by /usr/local/etc/rc.d/samba start (or stop/restart) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Questions from a Total samba Novice.
On Friday 09 May 2008 9:49 am, Ivan Voras wrote: > Martin McCormick wrote: > > I just found out that I will need to copy some files > > from a FreeBSD system to a Windows shared drive on our network so that > > Windows users can have access to the files. > > > > After reading a little documentation and talking to a > > cowworker, I was under the impression that this would allow > > windows clients to access files on the FreeBSD system, kind of > > the reverse of what I wanted. Then I read the man page for the > > samba suite and it says: > > > >smbclient(1) > > The smbclient program implements a simple ftp-like client. This is > > useful for accessing SMB shares on other compatible servers (such as > > Windows NT), and can also be used to allow a UNIX box to print to a > > printer attached to any SMB server (such as a PC running Windows > > NT). > > > > That sounds like I could push a file across when needed and be > > done with it rather than trying to coordinate the remote users > > to get the file at some time after I left it in a given > > directory. > > > > Is that just wishful thinking or will it work that way > > when properly configured? I need to be able to tell others in > > this group what is possible and that one little paragraph seems > > to say one can copy out from the UNIX box to the shared drive. > > Hi, > > After reading all this I'm still not certain about what do you want to > do. If you are trying to just transfer some files from a FreeBSD machine > to a Windows machine (or in the other direction) once, without much > configuration, smbclient will let you do that. Run it on the FreeBSD > machine and connect to a Windows machine. > > If you want to make the FreeBSD machine into a server for Windows > machines (i.e. the files will always be on the FreeBSD machine but > Windows users can access them, i.e. the FreeBSD machine will share > files), then you need to configure Samba properly (edit smb.conf). > > > Any particular gotchas regarding XP which soon will be > > Vista in this neck of the woods? > > No particular problems. Once configured, Samba works without additional > maintenance. If you just want to transfer files to the Win box on an ad hoc, periodic basis, why not just set up ssh on your FreeBSD box and use WinSCP on the Win box? Simpler than setting up Samba (though we use it very successfully here). -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Questions from a Total samba Novice.
Martin McCormick wrote: > I just found out that I will need to copy some files > from a FreeBSD system to a Windows shared drive on our network so that > Windows users can have access to the files. > > After reading a little documentation and talking to a > cowworker, I was under the impression that this would allow > windows clients to access files on the FreeBSD system, kind of > the reverse of what I wanted. Then I read the man page for the > samba suite and it says: > >smbclient(1) > The smbclient program implements a simple ftp-like client. This is > useful for accessing SMB shares on other compatible servers (such as > Windows NT), and can also be used to allow a UNIX box to print to a > printer attached to any SMB server (such as a PC running Windows > NT). > > That sounds like I could push a file across when needed and be > done with it rather than trying to coordinate the remote users > to get the file at some time after I left it in a given > directory. > > Is that just wishful thinking or will it work that way > when properly configured? I need to be able to tell others in > this group what is possible and that one little paragraph seems > to say one can copy out from the UNIX box to the shared drive. Hi, After reading all this I'm still not certain about what do you want to do. If you are trying to just transfer some files from a FreeBSD machine to a Windows machine (or in the other direction) once, without much configuration, smbclient will let you do that. Run it on the FreeBSD machine and connect to a Windows machine. If you want to make the FreeBSD machine into a server for Windows machines (i.e. the files will always be on the FreeBSD machine but Windows users can access them, i.e. the FreeBSD machine will share files), then you need to configure Samba properly (edit smb.conf). > Any particular gotchas regarding XP which soon will be > Vista in this neck of the woods? No particular problems. Once configured, Samba works without additional maintenance. signature.asc Description: OpenPGP digital signature
Questions from a Total samba Novice.
I just found out that I will need to copy some files from a FreeBSD system to a Windows shared drive on our network so that Windows users can have access to the files. After reading a little documentation and talking to a cowworker, I was under the impression that this would allow windows clients to access files on the FreeBSD system, kind of the reverse of what I wanted. Then I read the man page for the samba suite and it says: smbclient(1) The smbclient program implements a simple ftp-like client. This is useful for accessing SMB shares on other compatible servers (such as Windows NT), and can also be used to allow a UNIX box to print to a printer attached to any SMB server (such as a PC running Windows NT). That sounds like I could push a file across when needed and be done with it rather than trying to coordinate the remote users to get the file at some time after I left it in a given directory. Is that just wishful thinking or will it work that way when properly configured? I need to be able to tell others in this group what is possible and that one little paragraph seems to say one can copy out from the UNIX box to the shared drive. Any particular gotchas regarding XP which soon will be Vista in this neck of the woods? I apologize for some of the dumb questions as I do not personally use Windows. I use FreeBSD, Mac and Linux. We have a huge Windows base on our campus, however, so for now, I need to export some log files to the Windows world. Thanks for any useful ideas and for your patience. Martin McCormick WB5AGZ Stillwater, OK Systems Engineer OSU Information Technology Department Network Operations Group ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
