Re: Can anyone reproduce this Samba problem?
On Sat, Sep 5, 2009 at 6:12 PM, Karl Vogel vogelke+u...@pobox.com wrote: http://www.theopensourcerer.com/2008/04/17/a-shared-drop-box-using-samba/ has some suggestions that might help. It is a good link - In fact it's what I based my setup on. However, it relies on both 'inherit owner' and 'directory mode' / 'force directory mode' working simultaneously. And on my install, for some reason, that does not work. I can only get one or the other to work. Still not sure if it's a general Samba issue or FreeBSD-specific (or me being dumb somehow). -John ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Can anyone reproduce this Samba problem?
On Wed, 26 Aug 2009 21:54:02 -0700,
John W jwde...@gmail.com said:
J I have been trying to set up a 'dropbox' Samba share on FreeBSD, but am
J not having luck. I went back and forth on the Samba ML for a bit, and
J now I'm trying to determine if I am seeing FreeBSD-specific bad
J behavior.
http://www.theopensourcerer.com/2008/04/17/a-shared-drop-box-using-samba/
has some suggestions that might help.
--
Karl Vogel I don't speak for the USAF or my company
:-{8Person who is unhappy with the results of her
breast-enlargement surgery. --Dave Barry's emoticons
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Can anyone reproduce this Samba problem?
Interestingly, if I turn off 'inherit permissions', then 'inherit owner' DOES take effect correctly. However, that means the sticky bit does not get inherited, which will not work for me. I need both to be inherited, and for some reason they are behaving mutually-exclusive (with 'inherit permissions' taking precedence). If I understood your problem correctly, you don't actually want to set sticky bit on the root directory, but suid - so the chmod would be like chmod 4xxx mydir In FreeBSD suid-bitted directory will make all the subdirs to inherit the owner. Sticky bit causes bit different behaviour - see sticky (8) and chmod(1) -Reko ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Can anyone reproduce this Samba problem?
On Thu, Aug 27, 2009 at 2:30 AM, Reko Turjareko.tu...@liukuma.net wrote: Interestingly, if I turn off 'inherit permissions', then 'inherit owner' DOES take effect correctly. However, that means the sticky bit does not get inherited, which will not work for me. I need both to be inherited, and for some reason they are behaving mutually-exclusive (with 'inherit permissions' taking precedence). If I understood your problem correctly, you don't actually want to set sticky bit on the root directory, but suid - so the chmod would be like chmod 4xxx mydir In FreeBSD suid-bitted directory will make all the subdirs to inherit the owner. Sticky bit causes bit different behaviour - see sticky (8) and chmod(1) I want both the owner AND the sticky bit to be inherited. That is my dilemma. The sticky bit is necessary in my case because I do not want anyone but the owner to modify a file once created. And further, I am setting the owner to 'nobody' so this means *no* user can modify a file once created, not even files they themselves created. That is exactly the point of this share I'm trying to create. This directory will be open to many users, via a public share, with no passwords. I want everyone to be able to create new files/dirs in this share, but I do not want anyone to be able to rename/delete/modify/overwrite/etc. *any* files once created. I am trying to avoid using SUIDDIR (see my email), though I realize that is an option. If I cannot make Samba's 'inherit owner' option work on FreeBSD, that may be my only choice. Regardless of that, I would like to determine if this is a Samba bug or not, and which versions are affected, if so. However, even if I were to use SUIDDIR, I would still need the sticky bit to prevent modifications to files. Unless I am missing something, of course (: -John ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Can anyone reproduce this Samba problem?
I have been trying to set up a 'dropbox' Samba share on FreeBSD, but am not having luck. I went back and forth on the Samba ML for a bit, and now I'm trying to determine if I am seeing FreeBSD-specific bad behavior. Could anyone out there see if they can reproduce my issue on FreeBSD? I have a simple reproduction case (repeatable for me, at least), and I'm curious if people see the same behavior on: - Samba 3.2 (broken for me) - Samba 3.3 (broken for me) - Samba 3.4 (It's not in ports, I haven't installed it manually yet, but someone with Ubuntu has confirmed it works for them with this version) Here is tail of the old thread with gory details, if anyone's interested: http://www.mail-archive.com/sa...@lists.samba.org/msg102359.html So here is what I am trying to do, and how to reproduce my issue: I want a dropbox share, with the sticky bit set, and with the file owner to be inherited from the share directory, for new files/dirs. Note: I do not want to use SUIDDIR if possible. I realize it is an option, but am trying to avoid it for now. So I have a directory like this: drwxrwxr-t 20 nobody myuser 512 Aug 19 20:07 myshare And it is shared in smb.conf like this: [myshare] comment = my share path = /path/to/myshare read only = no inherit permissions = yes inherit owner = yes Now I want to create a directory in this share (from a Windows machine, or smbclient). What I would *expect* is this: drwxrwxr-t 2 nobody myuser 512 Aug 19 14:07 some_new_dir Notice that the sticky bit is set, and the user is set to 'nobody' which will ensure that no users, including the original creator, can alter this directory once created. And in fact, this is what happens when Jeremy Allison tried it on Ubuntu 8.10 with Samba 3.4 (see thread mentioned earlier). HOWEVER, on both my FreeBSD boxes with either Samba 3.2 or 3.3, I instead get this: drwxrwxr-t 2 myuser myuser512 Aug 19 14:07 some_new_dir Notice the owner is 'myuser' instead of 'nobody'. Thus, the user 'myuser' can now rename the directory (for instance), which is not acceptable. It seems as though 'inherit owner' is just being ignored. I don't know why. Interestingly, if I turn off 'inherit permissions', then 'inherit owner' DOES take effect correctly. However, that means the sticky bit does not get inherited, which will not work for me. I need both to be inherited, and for some reason they are behaving mutually-exclusive (with 'inherit permissions' taking precedence). I have tried this on Samba3.3 and 3.2, both on FreeBSD-7.2_RELEASE (amd64) machines, and neither works. So to sum up: I'd very much appreciate it if some FreeBSD people could try reproducing this with any/all of Samba 3.2,3.3,3.4. I'd also be curious of the results with Samba3.2 or 3.3 on a non-FreeBSD Unix. I'm just trying to determine if I'm crazy or not (: Thanks -John ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
samba problem; member server can't authenticate
Hey List- I tried the Samba lists...but didn't get any tips there..so possibly a freebsd issue? Dunno, anyways I have a Samba PDC and a Samba Member Server. The Samba PDC works fine, but the problem is that the Member Server can't authenticate users and let me browse file shares and i always get the error: NT_STATUS_NO_LOGON_SERVERS the wierd thing is that sometimes: SMBCLIENT -L ECWTEST will work and list my shares. However, the first time I actually try to authenticate a user to browse a share the whole shebang stops and I get the above error. I'm using Konqueror and smb://ecwtest/sharename to connect. I don't need to make any PAM changes to allow just file / share authentication do I? One thing, the member server is a new rebuild of a machine with the same name and the PDC is a upgrade using the TDBs, etc.. from backup. I did remove the machine account from the PDC and then re-added it using net join and that worked fine. I ran through the test at the back of the offical book and all of them work except the actual sharing and the nmblookup -d 2 '*' on the member server and of course the smbclient specific ones. wbinfo -u and wbinfo -g work on the member server and i can chown files to users only in the PDC in the samba users file. I just can't authenticate. the only error I'm seeing is in log.wb-ECW and its: [2006/09/03 12:54:12, 1] rpc_client/cli_pipe.c:cli_pipe_validate_current_pdu(625) cli_pipe_validate_current_pdu: RPC fault code DCERPC_FAULT_OP_RNG_ERROR received from remote machine ECWSERVER pipe \lsarpc fnum 0x70a8! [2006/09/03 13:17:04, 1] rpc_client/cli_pipe.c:cli_pipe_validate_current_pdu(625) cli_pipe_validate_current_pdu: RPC fault code DCERPC_FAULT_OP_RNG_ERROR received from remote machine ECWSERVER pipe \NETLOGON fnum 0x7549! [2006/09/03 13:38:05, 0] nsswitch/winbindd_dual.c:child_read_request(49) Got invalid request length: 0 [2006/09/03 13:38:12, 1] rpc_client/cli_pipe.c:cli_pipe_validate_current_pdu(625) cli_pipe_validate_current_pdu: RPC fault code DCERPC_FAULT_OP_RNG_ERROR received from remote machine ECWSERVER pipe \lsarpc fnum 0x7104! Here is my setup: PDC: ECWSERVER ; FreeBSD 6-stable and samba-3.0.23b,1 member: ECWTEST ; freeBSD 6-stable and samba-3.0.23b,1 Both servers are on the same network and have static IPs. i am able to ping, etc.. using the netbios names my /etc/nssswitch.conf is the same on both: group: files winbind group_compat: nis hosts: files dns networks: files passwd: files winbind passwd_compat: nis shells: files PDC smb.conf: # Global parameters [global] workgroup = ECW netbios name = ECWSERVER passdb backend = tdbsam:/usr/local/etc/samba/private/passwd.tdb os level = 65 preferred master = yes domain master = yes local master = yes domain logons = yes wins support = yes #server string = Samba %v on %L server string = security = USER encrypt passwords = yes disable spoolss = Yes guest ok = yes follow symlinks = no case sensitive = no idmap uid = 15000-2 idmap gid = 15000-2 username map = /usr/local/etc/samba/smbusers name resolve order = hosts wins bcast time server = Yes #printing options #printing = cups #printcap name = cups #load printers = yes #show add printer wizard = Yes #printer admin = @ecwadmins,@wheel #user scripts add user script = /usr/sbin/pw useradd -n %u -g ecwusers -s /usr/sbin/nologin -c delete user script = /usr/sbin/pw userdel -n %u add group script = /usr/sbin/pw groupadd -n %g delete group script = /usr/sbin/pw groupdel -n %g add user to group script = /usr/sbin/pw usermod -n %u -g %g #add machine script = /usr/sbin/pw useradd -n %u -g 100 -s /usr/sbin/nologin -d /dev/null #user directories logon home = \\%N\%U\ logon drive = H: #roaming profiles logon path = # the member server smb.conf: # Global parameters [global] workgroup = ECW netbios name = ECWTEST #server string = Samba %v on %L server string = security = domain password server = ECWSERVER wins server = 10.0.0.6 encrypt passwords = yes idmap uid = 15000-2 idmap gid = 15000-2 winbind use default domain = yes guest ok = yes follow symlinks = no case sensitive = no os level = 33 preferred master = no domain master = no #bind interfaces only = yes #interfaces = fxp0 lo0 #hosts deny = ALL #hosts allow = 10.0.0.0/24 127. name resolve order = hosts wins bcast Thanks. henrik -- Henrik Hudson [EMAIL PROTECTED] -- There are 10 kinds of people in the world: Those who understand binary and those who don't... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: samba problem; member server can't authenticate
On 9/3/06, Henrik Hudson [EMAIL PROTECTED] wrote: I have a Samba PDC and a Samba Member Server. The Samba PDC works fine, but the problem is that the Member Server can't authenticate users and let me browse file shares and i always get the error: NT_STATUS_NO_LOGON_SERVERS Sounds like your member server can't contact the pdc's logon service. the wierd thing is that sometimes: SMBCLIENT -L ECWTEST will work and list my shares. However, the first time I actually try to authenticate a user to browse a share the whole shebang stops and I get the above error. I'm using Konqueror and smb://ecwtest/sharename to connect. Try to always use FQDN (ecwtest.domain.blah); or be very careful and complete in the way you set up your name resolution (WINS, DNS). Especially if you have hosts on different subnets. I don't need to make any PAM changes to allow just file / share authentication do I? No. Samba doesn't use PAM. One thing, the member server is a new rebuild of a machine with the same name and the PDC is a upgrade using the TDBs, etc.. from backup. I did remove the machine account from the PDC and then re-added it using net join and that worked fine. I ran through the test at the back of the offical book and all of them work except the actual sharing and the nmblookup -d 2 '*' on the member server and of course the smbclient specific ones. nmblookup is a WINS resolution tool. If your WINS server is not configured and functioning and your computers are on different subnets (or have blocking firewalls) you will have problems. If you don't use FQDN samba will, probably, be using WINS to resolve your host names. the member server smb.conf: # Global parameters [global] workgroup = ECW netbios name = ECWTEST #server string = Samba %v on %L server string = security = domain password server = ECWSERVER Make that an FQDN hostname or ip address. wins server = 10.0.0.6 encrypt passwords = yes idmap uid = 15000-2 idmap gid = 15000-2 winbind use default domain = yes guest ok = yes follow symlinks = no case sensitive = no os level = 33 preferred master = no domain master = no #bind interfaces only = yes #interfaces = fxp0 lo0 #hosts deny = ALL #hosts allow = 10.0.0.0/24 127. name resolve order = hosts wins bcast And check your firewall rules. -- -- Perfection is just a word I use occasionally with mustard. --Atom Powers-- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: samba problem; member server can't authenticate
On Sunday 03 September 2006 13:59, Atom Powers [EMAIL PROTECTED] sent a missive stating: On 9/3/06, Henrik Hudson [EMAIL PROTECTED] wrote: I have a Samba PDC and a Samba Member Server. The Samba PDC works fine, but the problem is that the Member Server can't authenticate users and let me browse file shares and i always get the error: NT_STATUS_NO_LOGON_SERVERS Sounds like your member server can't contact the pdc's logon service. Yeap :) the wierd thing is that sometimes: SMBCLIENT -L ECWTEST will work and list my shares. However, the first time I actually try to authenticate a user to browse a share the whole shebang stops and I get the above error. I'm using Konqueror and smb://ecwtest/sharename to connect. Try to always use FQDN (ecwtest.domain.blah); or be very careful and complete in the way you set up your name resolution (WINS, DNS). Especially if you have hosts on different subnets. I've tried it both ways. Some people say to use the FQDN and some the other way around. nmblookup is a WINS resolution tool. If your WINS server is not configured and functioning and your computers are on different subnets (or have blocking firewalls) you will have problems. If you don't use FQDN samba will, probably, be using WINS to resolve your host names. My firewalls are 100% off until I get this working. henrik -- Henrik Hudson [EMAIL PROTECTED] -- There are 10 kinds of people in the world: Those who understand binary and those who don't... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: samba problem; member server can't authenticate
FYI: It seems the winbind use default domain = yes was getting the member server all messed up in the head. I removed that and suddenly it became just a problem of changing my permissions to include the ECW domain in the allowed users. Thanks for the responses. henrik On Sunday 03 September 2006 13:46, Henrik Hudson [EMAIL PROTECTED] sent a missive stating: Hey List- I tried the Samba lists...but didn't get any tips there..so possibly a freebsd issue? Dunno, anyways I have a Samba PDC and a Samba Member Server. The Samba PDC works fine, but the problem is that the Member Server can't authenticate users and let me browse file shares and i always get the error: NT_STATUS_NO_LOGON_SERVERS the wierd thing is that sometimes: SMBCLIENT -L ECWTEST will work and list my shares. However, the first time I actually try to authenticate a user to browse a share the whole shebang stops and I get the above error. I'm using Konqueror and smb://ecwtest/sharename to connect. I don't need to make any PAM changes to allow just file / share authentication do I? One thing, the member server is a new rebuild of a machine with the same name and the PDC is a upgrade using the TDBs, etc.. from backup. I did remove the machine account from the PDC and then re-added it using net join and that worked fine. I ran through the test at the back of the offical book and all of them work except the actual sharing and the nmblookup -d 2 '*' on the member server and of course the smbclient specific ones. wbinfo -u and wbinfo -g work on the member server and i can chown files to users only in the PDC in the samba users file. I just can't authenticate. the only error I'm seeing is in log.wb-ECW and its: [2006/09/03 12:54:12, 1] rpc_client/cli_pipe.c:cli_pipe_validate_current_pdu(625) cli_pipe_validate_current_pdu: RPC fault code DCERPC_FAULT_OP_RNG_ERROR received from remote machine ECWSERVER pipe \lsarpc fnum 0x70a8! [2006/09/03 13:17:04, 1] rpc_client/cli_pipe.c:cli_pipe_validate_current_pdu(625) cli_pipe_validate_current_pdu: RPC fault code DCERPC_FAULT_OP_RNG_ERROR received from remote machine ECWSERVER pipe \NETLOGON fnum 0x7549! [2006/09/03 13:38:05, 0] nsswitch/winbindd_dual.c:child_read_request(49) Got invalid request length: 0 [2006/09/03 13:38:12, 1] rpc_client/cli_pipe.c:cli_pipe_validate_current_pdu(625) cli_pipe_validate_current_pdu: RPC fault code DCERPC_FAULT_OP_RNG_ERROR received from remote machine ECWSERVER pipe \lsarpc fnum 0x7104! Here is my setup: PDC: ECWSERVER ; FreeBSD 6-stable and samba-3.0.23b,1 member: ECWTEST ; freeBSD 6-stable and samba-3.0.23b,1 Both servers are on the same network and have static IPs. i am able to ping, etc.. using the netbios names my /etc/nssswitch.conf is the same on both: group: files winbind group_compat: nis hosts: files dns networks: files passwd: files winbind passwd_compat: nis shells: files PDC smb.conf: # Global parameters [global] workgroup = ECW netbios name = ECWSERVER passdb backend = tdbsam:/usr/local/etc/samba/private/passwd.tdb os level = 65 preferred master = yes domain master = yes local master = yes domain logons = yes wins support = yes #server string = Samba %v on %L server string = security = USER encrypt passwords = yes disable spoolss = Yes guest ok = yes follow symlinks = no case sensitive = no idmap uid = 15000-2 idmap gid = 15000-2 username map = /usr/local/etc/samba/smbusers name resolve order = hosts wins bcast time server = Yes #printing options #printing = cups #printcap name = cups #load printers = yes #show add printer wizard = Yes #printer admin = @ecwadmins,@wheel #user scripts add user script = /usr/sbin/pw useradd -n %u -g ecwusers -s /usr/sbin/nologin -c delete user script = /usr/sbin/pw userdel -n %u add group script = /usr/sbin/pw groupadd -n %g delete group script = /usr/sbin/pw groupdel -n %g add user to group script = /usr/sbin/pw usermod -n %u -g %g #add machine script = /usr/sbin/pw useradd -n %u -g 100 -s /usr/sbin/nologin -d /dev/null #user directories logon home = \\%N\%U\ logon drive = H: #roaming profiles logon path = # the member server smb.conf: # Global parameters [global] workgroup = ECW netbios name = ECWTEST #server string = Samba %v on %L server string = security = domain password server = ECWSERVER wins server = 10.0.0.6 encrypt passwords = yes idmap uid = 15000-2 idmap gid = 15000-2 winbind use default domain = yes guest ok = yes follow symlinks = no case sensitive = no os level = 33 preferred master = no domain master = no #bind interfaces only = yes #interfaces = fxp0 lo0 #hosts deny = ALL #hosts allow = 10.0.0.0/24 127. name resolve order = hosts wins bcast Thanks. henrik -- Henrik Hudson [EMAIL PROTECTED] -- There are 10 kinds of people in the world: Those who understand binary and
Re: Samba problem
Actually, with fBSD6.1-CURRENT, some people have problems mounting SMB shares. I'll try at the kernel-config as Werner-Griessl said. Best Regards, Carlos Silva, CSilva Web: http://www.csilva.org/ Roman Streltsov escreveu: I haven't any mention about SMB in kernel-config. Roman - Original Message - From: Carlos Silva [EMAIL PROTECTED] To: Roman Streltsov [EMAIL PROTECTED] Sent: Tuesday, August 15, 2006 3:27 PM Subject: Re: Samba problem Hi, Yeah, but that continues strange. Now I'll verify kernel-level configuration, maybe the default config has a breach. Thanks Best Regards, Carlos Silva, CSilva Web: http://www.csilva.org/ Roman Streltsov escreveu: Hi cat /usr/local/etc/smb.conf [global] workgroup = SUMA netbios name = S1 hide unreadable = yes [homes] comment = Home Directories valid users = %S read only = No browseable = No [suma] path=/home/suma writable = yes browseable = yes public = no valid users = ilya als warlock #read list = nobody create mask = 0777 directory mask = 0777 nothing unusual Regards Roman - Original Message - From: Carlos Silva [EMAIL PROTECTED] To: Roman Streltsov [EMAIL PROTECTED] Sent: Tuesday, August 15, 2006 3:06 PM Subject: Re: Samba problem hi, can you send me the configuration vars of the smb.conf? maybe that's the problem. Best Regards, Carlos Silva, CSilva Web: http://www.csilva.org/ Roman Streltsov escreveu: Hi all, I am using samba-3.0.21b,1 succefully on 6.1-RELEASE-p3 box without any problem. But portaudit marks the package like problemed. Also the port has IGNORE mark and I can't upgrade samba. Regards Roman Streltsov - Original Message - From: Carlos Silva [EMAIL PROTECTED] To: freebsd-ports@freebsd.org; freebsd-current@freebsd.org Sent: Tuesday, August 15, 2006 2:08 PM Subject: Re: Samba problem that's a big problem.. i've tried to install a NFS server on windowsXP but the filesystem doesnt work very fine with that. so, someone has an idea? Best Regards, Carlos Silva, CSilva Web: [1]http://www.csilva.org/ Divacky Roman escreveu: On Tue, Aug 15, 2006 at 10:10:19AM +0100, Carlos Silva wrote: Hi all, I have installed freebsd 6.1-RELEASE on my machine and now samba dont work, because of a timeout. I've tried the two versions of the samba ports and none of them work properly. Do you have any idea? Ouput: osiris# mount -t smbfs //porta1/tmpdown /tmpdir Password: mount_smbfs: unable to open connection: syserr = Operation timed out Otherwise, this is not an password error. I can confirm this. something happened and now I am not able to mount smb shares on 6.1R.. on 6.0R it works ok. ___ [EMAIL PROTECTED] mailing list [3]http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [4][EMAIL PROTECTED] References 1. http://www.csilva.org/ 2. mailto:freebsd-current@freebsd.org 3. http://lists.freebsd.org/mailman/listinfo/freebsd-current 4. mailto:[EMAIL PROTECTED] ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Samba problem
Hi all, I have installed freebsd 6.1-RELEASE on my machine and now samba dont work, because of a timeout. I've tried the two versions of the samba ports and none of them work properly. Do you have any idea? Ouput: osiris# mount -t smbfs //porta1/tmpdown /tmpdir Password: mount_smbfs: unable to open connection: syserr = Operation timed out Otherwise, this is not an password error. Best Regards, Carlos Silva, CSilva Web: http://www.csilva.org/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Samba Problem
Warren Liddell wrote: When i try logging onto the FreeBSD machine from windows via samba, upon entering the username/pswd windows Automatically adds: fred/shinjii All i want it to have is just shinjii .. what am i missing and where do i go to fix this ? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] If your Windows machine have a name FRED than this is normal behaviour. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Samba Problem
If your Windows machine have a name FRED than this is normal behaviour. yes but there is an optino to turn it off so it dosent add that in and unfortunately, my windows machine isnt called fred. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Samba Problem
On Saturday 11 February 2006 16:14, you wrote: Warren Liddell wrote: On Saturday 11 February 2006 12:33, Duane Whitty wrote: Warren Liddell wrote: When i try logging onto the FreeBSD machine from windows via samba, upon entering the username/pswd windows Automatically adds: fred/shinjii All i want it to have is just shinjii .. what am i missing and where do i go to fix this ? ok, as embaressing as this is, i managed to solve this problem as i had forgotten to add the sama accounts themselves using smbpasswd .. onc ei ran smbpasswd it worked straight up like it should. Thanks to all those who offerd assistance. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Samba Problem
Warren Liddell wrote: When i try logging onto the FreeBSD machine from windows via samba, upon entering the username/pswd windows Automatically adds: fred/shinjii All i want it to have is just shinjii .. what am i missing and where do i go to fix this ? ___ Hi, It might help if you could send a copy of your samba configuration file, usually it is located at /usr/local/etc/smb.conf This is where I would start looking for problems. Also read the smb.conf.default file as it gives good examples as a starting point. --Duane ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Samba Problem
On Saturday 11 February 2006 12:33, Duane Whitty wrote: Warren Liddell wrote: When i try logging onto the FreeBSD machine from windows via samba, upon entering the username/pswd windows Automatically adds: fred/shinjii All i want it to have is just shinjii .. what am i missing and where do i go to fix this ? - Hi, It might help if you could send a copy of your samba configuration file, usually it is located at /usr/local/etc/smb.conf This is where I would start looking for problems. Also read the smb.conf.default file as it gives good examples as a starting point. Attached is conf file #=== Global Settings = [global] # workgroup = NT-Domain-Name or Workgroup-Name, eg: MIDEARTH workgroup = WORKGROUP # server string is the equivalent of the NT Description field server string = Samba Server # Security mode. Defines in which mode Samba will operate. Possible # values are share, user, server, domain and ads. Most people will want # user level security. See the Samba-HOWTO-Collection for details. security = user # This option is important for security. It allows you to restrict # connections to machines which are on your local network. The # following example restricts access to two C class networks and # the loopback interface. For more examples of the syntax see # the smb.conf man page ; hosts allow = 192.168.1. 192.168.2. 127. # If you want to automatically load your printer list rather # than setting them up individually then you'll need this ;load printers = yes # you may wish to override the location of the printcap file ; printcap name = /etc/printcap # on SystemV system setting printcap name to lpstat should allow # you to automatically obtain a printer list from the SystemV spool # system ; printcap name = lpstat # It should not be necessary to specify the print system type unless # it is non-standard. Currently supported print systems include: # bsd, cups, sysv, plp, lprng, aix, hpux, qnx ; printing = cups # Uncomment this if you want a guest account, you must add this to /etc/passwd # otherwise the user nobody is used ; guest account = pcguest # this tells Samba to use a separate log file for each machine # that connects log file = /var/log/samba/log.%m # Put a capping on the size of the log files (in Kb). max log size = 50 # Use password server option only with security = server # The argument list may include: # password server = My_PDC_Name [My_BDC_Name] [My_Next_BDC_Name] # or to auto-locate the domain controller/s # password server = * # password server = NT-Server-Name # Use the realm option only with security = ads # Specifies the Active Directory realm the host is part of ; realm = MY_REALM # Backend to store user information in. New installations should # use either tdbsam or ldapsam. smbpasswd is available for backwards # compatibility. tdbsam requires no further configuration. # passdb backend = tdbsam # Using the following line enables you to customise your configuration # on a per machine basis. The %m gets replaced with the netbios name # of the machine that is connecting. # Note: Consider carefully the location in the configuration file of # this line. The included file is read at that point. ; include = /usr/local/etc/smb.conf.%m # Most people will find that this option gives better performance. # See the chapter 'Samba performance issues' in the Samba HOWTO Collection # and the manual pages for details. # You may want to add the following on a Linux system: # SO_RCVBUF=8192 SO_SNDBUF=8192 socket options = TCP_NODELAY # Configure Samba to use multiple interfaces # If you have multiple network interfaces then you must list them # here. See the man page for details. ; interfaces = 192.168.12.2/24 192.168.13.2/24 # Browser Control Options: # set local master to no if you don't want Samba to become a master # browser on your network. Otherwise the normal election rules apply ; local master = no # OS Level determines the precedence of this server in master browser # elections. The default value should be reasonable ; os level = 33 # Domain Master specifies Samba to be the Domain Master Browser. This # allows Samba to collate browse lists between subnets. Don't use this # if you already have a Windows NT domain controller doing this job ; domain master = yes # Preferred Master causes Samba to force a local browser election on startup # and gives it a slightly higher chance of winning the election ; preferred master = yes # Enable this if you want Samba to be a domain logon server for # Windows95 workstations. ; domain logons = yes # if you enable domain logons then you may want a per-machine or # per user logon script # run a specific logon batch file per workstation (machine) ; logon script = %m.bat # run a specific logon batch file per username ; logon script = %U.bat # Where to store roving
Re: Samba Problem
Warren Liddell wrote: When i try logging onto the FreeBSD machine from windows via samba, upon entering the username/pswd windows Automatically adds: fred/shinjii All i want it to have is just shinjii .. what am i missing and where do i go to fix this ? ___ Hi, Sorry, as well I meant to ask which version of MS-Windows are you running and what version of SAMBA. --Duane ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Samba Problem
Warren Liddell wrote: On Saturday 11 February 2006 12:33, Duane Whitty wrote: Warren Liddell wrote: When i try logging onto the FreeBSD machine from windows via samba, upon entering the username/pswd windows Automatically adds: fred/shinjii All i want it to have is just shinjii .. what am i missing and where do i go to fix this ? - Hi, It might help if you could send a copy of your samba configuration file, usually it is located at /usr/local/etc/smb.conf This is where I would start looking for problems. Also read the smb.conf.default file as it gives good examples as a starting point. Attached is conf file #=== Global Settings = [global] # workgroup = NT-Domain-Name or Workgroup-Name, eg: MIDEARTH workgroup = WORKGROUP # server string is the equivalent of the NT Description field server string = Samba Server # Security mode. Defines in which mode Samba will operate. Possible # values are share, user, server, domain and ads. Most people will want # user level security. See the Samba-HOWTO-Collection for details. security = user # This option is important for security. It allows you to restrict # connections to machines which are on your local network. The # following example restricts access to two C class networks and # the loopback interface. For more examples of the syntax see # the smb.conf man page ; hosts allow = 192.168.1. 192.168.2. 127. # If you want to automatically load your printer list rather # than setting them up individually then you'll need this ;load printers = yes # you may wish to override the location of the printcap file ; printcap name = /etc/printcap # on SystemV system setting printcap name to lpstat should allow # you to automatically obtain a printer list from the SystemV spool # system ; printcap name = lpstat # It should not be necessary to specify the print system type unless # it is non-standard. Currently supported print systems include: # bsd, cups, sysv, plp, lprng, aix, hpux, qnx ; printing = cups # Uncomment this if you want a guest account, you must add this to /etc/passwd # otherwise the user nobody is used ; guest account = pcguest # this tells Samba to use a separate log file for each machine # that connects log file = /var/log/samba/log.%m # Put a capping on the size of the log files (in Kb). max log size = 50 # Use password server option only with security = server # The argument list may include: # password server = My_PDC_Name [My_BDC_Name] [My_Next_BDC_Name] # or to auto-locate the domain controller/s # password server = * # password server = NT-Server-Name # Use the realm option only with security = ads # Specifies the Active Directory realm the host is part of ; realm = MY_REALM # Backend to store user information in. New installations should # use either tdbsam or ldapsam. smbpasswd is available for backwards # compatibility. tdbsam requires no further configuration. # passdb backend = tdbsam # Using the following line enables you to customise your configuration # on a per machine basis. The %m gets replaced with the netbios name # of the machine that is connecting. # Note: Consider carefully the location in the configuration file of # this line. The included file is read at that point. ; include = /usr/local/etc/smb.conf.%m # Most people will find that this option gives better performance. # See the chapter 'Samba performance issues' in the Samba HOWTO Collection # and the manual pages for details. # You may want to add the following on a Linux system: # SO_RCVBUF=8192 SO_SNDBUF=8192 socket options = TCP_NODELAY # Configure Samba to use multiple interfaces # If you have multiple network interfaces then you must list them # here. See the man page for details. ; interfaces = 192.168.12.2/24 192.168.13.2/24 # Browser Control Options: # set local master to no if you don't want Samba to become a master # browser on your network. Otherwise the normal election rules apply ; local master = no # OS Level determines the precedence of this server in master browser # elections. The default value should be reasonable ; os level = 33 # Domain Master specifies Samba to be the Domain Master Browser. This # allows Samba to collate browse lists between subnets. Don't use this # if you already have a Windows NT domain controller doing this job ; domain master = yes # Preferred Master causes Samba to force a local browser election on startup # and gives it a slightly higher chance of winning the election ; preferred master = yes # Enable this if you want Samba to be a domain logon server for # Windows95 workstations. ; domain logons = yes # if you enable domain logons then you may want a per-machine or # per user logon script # run a specific logon batch file per workstation (machine) ; logon script = %m.bat # run a
RE: Samba Problem
[mailto:[EMAIL PROTECTED] On Behalf Of Warren Liddell Sent: Saturday, February 11, 2006 12:41 PM To: freebsd-questions@freebsd.org Subject: Re: Samba Problem On Saturday 11 February 2006 12:33, Duane Whitty wrote: Warren Liddell wrote: When i try logging onto the FreeBSD machine from windows via samba, upon entering the username/pswd windows Automatically adds: fred/shinjii All i want it to have is just shinjii .. what am i missing and where do i go to fix this ? - Hi, It might help if you could send a copy of your samba configuration file, usually it is located at /usr/local/etc/smb.conf This is where I would start looking for problems. Also read the smb.conf.default file as it gives good examples as a starting point. Attached is conf file 1. Check workstation is in the same workgroup 2. When you define your network path in Windows, make sure you use the connect using a different user name dialog box. 3. Make sure the password you use in (2) is the same as your samba password. 4. Note Windows will encrypt passwords by default. If this isn't working for you, you'll have to turn it off in the registry. -gayn Bristol Systems Inc. 714/532-6776 www.bristolsystems.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Samba Problem
When i try logging onto the FreeBSD machine from windows via samba, upon entering the username/pswd windows Automatically adds: fred/shinjii All i want it to have is just shinjii .. what am i missing and where do i go to fix this ? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: NetBSD-FreeBSD move: samba problem
Wojciech Puchar wrote: i had NetBSD with samba: [snip] samba starts smbclient started from host shows like everything is ok. but - from windose i see empty network environment when clicked on Whole network i see message that network can't be browsed etc. etc. [snip] smbclient shows: Sharename Type Comment - --- domowy Disk Katalog domowy uzytkownika public Disk Publiczny faxy Disk FAXY odebrane IPC$ IPC IPC Service (wojtek) ADMIN$ Disk IPC Service (wojtek) Server Comment ---- WOJTEK wojtek WorkgroupMaster ---- DOM WOJTEK i can log in with smbclient to any exported disk with password and all works right. but not from windoze. i really can't believe that it can be FreeBSD problem, but i have same config file and same samba version. any ideas? Hi, You haven't had any replies yet, so... Have you tried Start -- Run \\ipaddress.of.samba.server from the Windows machine? Might help narrow the problem down to netbios/browsing issues if it does find the machine. Peter. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: NetBSD-FreeBSD move: samba problem
Wojciech Puchar wrote: [snip] heve is my smb.conf [global] workgroup = DOM character set = ISO8859-2 client code page = 852 bind interfaces only = yes socket address = 10.255.245.1 server string = wojtek netbios name = wojtek hosts allow = 127.0.0.1 10. load printers = no log file = /var/log/samba.%m max log size = 500 security = user encrypt passwords = no One more thing - I know this came from a working setup on a NetBSD machine, but unless it's a very old version of Windows, encrypt passwords should generally be yes. Peter. domain master = yes local master = yes browseable = yes #socket options = TCP_NODELAY # jak sa jaiies NT to mozan zwiekszyc jak nie am to niepotrzebne os level = 65 [domowy] comment = Katalog domowy uzytkownika browseable = yes writable = yes path = %H [public] comment = Publiczny path = /home/pub read only = no public = yes writable = yes guest ok = no browseable = yes [faxy] comment = FAXY odebrane path = /home/faxy read only = no public = yes writable = yes guest ok = no browseable = yes ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: NetBSD-FreeBSD move: samba problem
thank you for all help. the problem was that windoze got configured by DHCP with netmask 255.255.255.224 (right), while i configured FreeBSD with netmask 255.255.255.0 (wrong). so broadcasts didn't work. today morning i changed it and samba started to work. thank you. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: NetBSD-FreeBSD move: samba problem
Wojciech Puchar wrote: Have you tried Start -- Run \\ipaddress.of.samba.server works. and AFTER THIS network neighborhood works too. any idea? i think that (as unusally) windoze is a problem Yup. All I can say is that I've found this to work with reluctant Windoze clients. I assume they are just *incredibly* slow to discover the network. Give them a week or two switched on, plugged into the network, doing nothing, and they'd probably be fine on their own... cc'ing to the list in case it helps anyone else. Peter. from the Windows machine? Might help narrow the problem down to netbios/browsing issues if it does find the machine. Peter. wait a bit ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
NetBSD-FreeBSD move: samba problem
i had NetBSD with samba: Information for samba-2.2.8anb5: Comment: SMB/CIFS protocol server suite for UNIX and now have FreeBSD with samba: samba-2.2.8aA free SMB and CIFS client and server for UNIX same versions of samba. i moved smb.conf to /usr/local/etc and started samba under FreeBSD. samba starts smbclient started from host shows like everything is ok. but - from windose i see empty network environment when clicked on Whole network i see message that network can't be browsed etc. etc. in log.nmbd i see: [2004/07/18 12:37:15, 0] nmbd/nmbd_responserecordsdb.c:find_response_record(235) find_response_record: response packet id 21742 received with no matching record. [2004/07/18 12:37:15, 0] nmbd/nmbd_responserecordsdb.c:find_response_record(235) find_response_record: response packet id 21743 received with no matching record. [2004/07/18 12:37:19, 0] nmbd/nmbd_become_dmb.c:become_domain_master_stage2(114) * Samba server WOJTEK is now a domain master browser for workgroup DOM on subnet 10.255.245.1 * [2004/07/18 12:37:35, 0] nmbd/nmbd_become_lmb.c:become_local_master_stage2(404) * Samba name server WOJTEK is now a local master browser for workgroup DOM on subnet 10.255.245.1 * smbclient shows: Sharename Type Comment - --- domowy Disk Katalog domowy uzytkownika public Disk Publiczny faxy Disk FAXY odebrane IPC$ IPC IPC Service (wojtek) ADMIN$ Disk IPC Service (wojtek) Server Comment ---- WOJTEK wojtek WorkgroupMaster ---- DOM WOJTEK i can log in with smbclient to any exported disk with password and all works right. but not from windoze. i really can't believe that it can be FreeBSD problem, but i have same config file and same samba version. any ideas? heve is my smb.conf [global] workgroup = DOM character set = ISO8859-2 client code page = 852 bind interfaces only = yes socket address = 10.255.245.1 server string = wojtek netbios name = wojtek hosts allow = 127.0.0.1 10. load printers = no log file = /var/log/samba.%m max log size = 500 security = user encrypt passwords = no domain master = yes local master = yes browseable = yes #socket options = TCP_NODELAY # jak sa jaiies NT to mozan zwiekszyc jak nie am to niepotrzebne os level = 65 [domowy] comment = Katalog domowy uzytkownika browseable = yes writable = yes path = %H [public] comment = Publiczny path = /home/pub read only = no public = yes writable = yes guest ok = no browseable = yes [faxy] comment = FAXY odebrane path = /home/faxy read only = no public = yes writable = yes guest ok = no browseable = yes ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Strange Samba problem(FreeBSD)
Hi, I have two machines one FreeBSD(netbios name= Backup) and one RH9(netbiosname = Redhat) I can see all the shares on both backup and Redhat (Refer to the below) when I am using my FreeBSD machine smbclient -L //redhat added interface ip=192.168.1.195 bcast=192.168.1.255 nmask=255.255.255.0 Got a positive name query response from 192.168.1.191 ( 192.168.1.191 ) Password: Domain=[X] OS=[Unix] Server=[Samba 2.2.7a] Sharename Type Comment - --- IPC$ IPC IPC Service (RH9 Server) ADMIN$ Disk IPC Service (RH9 Server) dannyhoDisk Home Directories Server Comment ---- REDHAT RH9 Server WorkgroupMaster ---- XREDHAT smbclient -L //backup added interface ip=192.168.1.195 bcast=192.168.1.255 nmask=255.255.255.0 Got a positive name query response from 192.168.1.195 ( 192.168.1.195 ) Password: Domain=[X] OS=[Unix] Server=[Samba 2.2.3a] Sharename Type Comment - --- homes Disk Home Directories dannyhoDisk Danny's Home Directory However when I am trying I am trying to view all the shares from my RH9 box I cant view the shares on the backup server (refer to the email below) [EMAIL PROTECTED] dannyho]$ smbclient -L //backup added interface ip=192.168.1.191 bcast=192.168.1.255 nmask=255.255.255.0 Connection to backup failed [EMAIL PROTECTED] dannyho]$ smbclient -L //redhat added interface ip=192.168.1.191 bcast=192.168.1.255 nmask=255.255.255.0 Password: Domain=[X] OS=[Unix] Server=[Samba 2.2.7a] Sharename Type Comment - --- IPC$ IPC IPC Service (RH9 Server) ADMIN$ Disk IPC Service (RH9 Server) dannyhoDisk Home Directories Server Comment ---- REDHAT RH9 Server WorkgroupMaster ---- XREDHAT Any ideas?? Yours faithfully, Danny Ho ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
vsftpd and samba problem
I am having some problems with vsftpd and I was wondering if someone could offer me some insight. I have an ftp server (using vsftpd) that mounts FAT32 shares from another machine via Samba. I can mount the shares with no problem and access the files if I log onto the machine with SSH. However, when I logon to the FTP server using an FTP client I am not able to transfer files with vsftpd. I get an error that states 426: failure writing network stream. I am able to change into the directory that I mount on and get a file listing. Another interesting thing is that when I use another FTP server (such as ProFTPd) everything works fine; I am able to transfer files from the samba shares. I have not been able to find much documentation involving a problem similar to mine. Any ideas/insight would be greatly appreciated. VSFTPD 1.1.3 Samba 2.2.7a FreeBSD 4.7 ProFTPd 1.2.7 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Samba Problem
I am relatively new to FreeBSD. I have been using Linux for about a year and I have decided to make the change to FreeBSD. I currently have one computer running Win98, one running RedHat Linux and one running FreeBSD. I am having trouble connecting to the smb shares on the Linux box from the FreeBSD box. From the BSD box, I can connect to the windows shares, but when I try to mount the Linux shares I got smbfs: unable to open connection: syserr = Authentication error. What really has me puzzled is the fact that the FreeBSD box originally had Linux on it and I had no problem connecting to the other Linux box with samba. Any insight would be appreciated. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
