Re: [Samba] Mapping drive
Hello, which version of samba? Is there a domain (samba or Windows?)? Did you made a "net use delete" and with xp, did you do execute "control keymgr.dll" and deleted all passwords saved? Then mapped new? --- EDV Daniel Müller Leitung EDV Tropenklinik Paul-Lechler-Krankenhaus Paul-Lechler-Str. 24 72076 Tübingen Tel.: 07071/206-463, Fax: 07071/206-499 eMail: muel...@tropenklinik.de Internet: www.tropenklinik.de --- -Ursprüngliche Nachricht- Von: samba-boun...@lists.samba.org [mailto:samba-boun...@lists.samba.org] Im Auftrag von Brian Gesendet: Donnerstag, 19. Mai 2011 15:40 An: samba@lists.samba.org Betreff: [Samba] Mapping drive We have a server running linux with a samba shared directory. We have sever windows xp machines that map the samba shared directory using the same user name and password. All has gone well for a couple of years. Now, on some of the machines, it won't allow the mapping of the samba share reporting "Access denied" I have made sure that the proper user name and password is used. There has been no recent updates on the server or user's computer...that we know of. One hint of a problem is that the windows machines appears to be trying to send the windows machine's group name as part of the log in which I know it didn't do before. Any ideas? Thanks to all that answer Brian Brian Germann Wayne Enterprises Inc. Linden, CA 209-887-2008 mailto:br...@revolution911.com http://www.revolution911.com -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
[Samba] No Access after enabling SMB2
Hello, i have a Samba Server running on CentOS 5.6 with samba package 3.5.8 from SerNet. Shares can accessed until I enable max protocol = smb2, after that no access is possible. In the samba logfiles such an access is logged with: Failed to parse NTLMSSP packet, could not extract NTLMSSP command Followed by a dump_data. Any ideas? Cheers, Daniel -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] No Access after enabling SMB2
On Fri, May 20, 2011 at 11:00:38AM +0200, Zabel, Daniel wrote: > i have a Samba Server running on CentOS 5.6 with samba package 3.5.8 > from SerNet. > > Shares can accessed until I enable max protocol = smb2, after that no > access is possible. For SMB2, please try 3.6.0rc1. Volker -- SerNet GmbH, Bahnhofsallee 1b, 37081 Göttingen phone: +49-551-37-0, fax: +49-551-37-9 AG Göttingen, HRB 2816, GF: Dr. Johannes Loxen -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Strange problem with my new PDC
Hi Helmut, the logs are 2,6 MB uncompressed, each. So inline would make ~5MB , multiplied by the number of recipients ;) So I thought a ~400 KB great attachment would be the better way ... Am 20.05.2011 07:22, schrieb Helmut Hullen: > Hallo, Marc, > > Du meintest am 19.05.11: > >> You can find two Logfiles in the attached archive. One's named >> Success.log and the other one Failing.log. > > No - this mailing list doesn't support such attachments. Try inline > copies. > > Viele Gruesse! > Helmut -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] No Access after enabling SMB2
On 2011-05-20 at 11:09 +0200 Volker Lendecke sent off: > On Fri, May 20, 2011 at 11:00:38AM +0200, Zabel, Daniel wrote: > > i have a Samba Server running on CentOS 5.6 with samba package 3.5.8 > > from SerNet. > > > > Shares can accessed until I enable max protocol = smb2, after that no > > access is possible. > > For SMB2, please try 3.6.0rc1. we plan to publish RPMs for testing on ftp.sernet.de in a couple of days. Cheers Björn -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Printer settings not saved
Dear Thilo, Did you manage to solve this issue? I'm having the same problem for some time now and I have not any clue yet how to solve this. On Wed, Apr 20, 2011 at 04:40:28PM +0200, Thilo Uttendorfer wrote: > Hi, > > I have problems to save printer settings like changing the > size from letter to A4. This happens for user settings > and default printer settings. The settings are always > resetted to default values like "letter". > > The system uses samba 3.4.11, I also did some tests with > samba 3.5.8, but nothing changed. > > After downgrading to 3.3.2 everything worked as expected. > I didn't change any samba configuration while up- and > downgrading. > > Bug #6727 sounds a little bit like my problem: > "[...] Also if I change the configuration (e. g. configure > 4 cartridges instead of 2), it is not be saved)." > But this bug should be fixed with 3.5.8, see: > https://bugzilla.samba.org/show_bug.cgi?id=6727 > > Can somebody confirm this bug? > > > Thank you, > Thilo Uttendorfer > > > > > -- > Thilo Uttendorfer > Linux Information Systems AG > Putzbrunner Str. 71, 81739 München > > t.uttendor...@linux-ag.com, http://www.linux-ag.com > > -- > To unsubscribe from this list go to the following URL and read the > instructions: https://lists.samba.org/mailman/options/samba -- Met vriendelijke groeten, With kind regards, Mit freundlichen Gruessen, Willy * W.K. Offermans e-mail: wi...@offermans.rompen.nl Powered by (__) \\\'',) \/ \ ^ .\._/_) www.FreeBSD.org -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
[Samba] Problems with group assignments
Dear All, We are trying to transfer a SaMBa installation from an old server to a newer more up-to-date one. The original server was sharing files to Windows XP systems in Active Directory (Windows Server 2003 R2 version), but as we move to Windows 7 and Active Directory (Windows Server 2008 R2 version) we need to upgrade the service. The old server was part of a NIS domain, with the "valid users", "write list", etc entries in its smb.conf referring to the NIS groups using the "@" sign (which the documentation says it means "is interpreted as an NIS netgroup first (if your system supports NIS), and then as a UNIX group if the name was not found in the NIS netgroup database"; see http://samba.org/samba/docs/man/manpages-3/smb.conf.5.html#INVALIDUSERS). It all worked fine as it picked users' group membership from NIS. The new server is a Solaris 10 box running SaMBa 3.5.5, and we are having problems with it picking up the group memberships. The old server's smb.conf was transplanted to the new server (with a few path changes), and the new server was successfully added to our Active Directory domain. As the new server is NOT a member of NIS, we made a copy of all the smb.conf-relevant groups to its local /etc/group and added all the users to the /etc/passwd file. With these changes we can access the shares using the AD usernames and passwords as long as they are not access-limited by "valid users", so the integration of the server into AD is working. But if we add a "valid users = @group" line to the share in smb.conf, it will completely refuse access to all users, even the ones belonging to the group. Leaving the share accessible to all, but adding a "write list = @group" line to smb.conf, will allow access, but no one will be able to write to it, even the members of the group. If we chan ge the "write list" and "valid users" lines to list the usernames directly instead of through a group membership, it works. To avoid even attempting to talk to NIS, we changed the "@" signs for "+", but it still kept refusing to recognize group memberships (NIS or local UNIX ones). So it seems our new SaMBa is having problems recognizing group memberships. What am I doing wrong? Have SUN/Oracle done something to stop SaMBa accessing its local UNIX groups? Thank you for your help. Yours, David del Campo -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Problems with group assignments
Dear Michal, The user authentication must be being handled by AD; the local accounts on the new server have been added to the /etc/passwd and /etc/shadow files, but the passwords in the /etc/shadow file are set to locked (which means that though the account exists and can own files, people cannot actually log in to the system; root can "su" to them though). As a result AD must be providing the authentication. The usernames in AD and the local files are the same. The /etc/nsswitch.conf file is as follows (comments removed): passwd: files group: files hosts: files dns ipnodes: files dns networks: files protocols: files rpc:files ethers: files netmasks: files bootparams: files publickey: files netgroup: files automount: files aliases:files services: files printers: user files auth_attr: files prof_attr: files project:files tnrhtp: files tnrhdb: files As you can see anything should be handled by the local files. The /etc/samba/smb.conf file is as follows (comments and private removed): [global] workgroup = server string = Samba Server on %h netbios name = security = ADS hosts allow = guest account = nobody log file = /var/samba/log/log.%m max log size = 500 password server = , realm = passdb backend= smbpasswd interfaces= local master = no os level = 33 domain master = no preferred master= no dns proxy = no [transit] comment = Temporary Backup for Windows 7 Upgrades path = browseable= no read only = yes valid users = user1, user2, user3, user4 # valid users = @group write list= users1, user2, user3, user4 # write list = +sysman As is, the share works, but as you can see I have to specify the usernames and cannot use +group or @group notation as I did on the old server. The old server was also part of the AD domain, so as far as I can see the only differences between the two setups is the SaMBa version and the fact the new server is not part of NIS; that is why I tried the +group notation, to no avail. I also have a Linux (Fedora 14) machine acting as a temporary SaMBa server (version 3.5.8); it is part of the NIS and AD domains and the @group assignments work fine from NIS. Thank you for your help. Yours, David > -Original Message- > From: Michal Belica [mailto:beli+...@beli.sk] > Sent: 20 May 2011 14:46 > To: F. David del Campo Hill > Subject: Re: [Samba] Problems with group assignments > > Hi, > > - Original Message - > > From: "F. David del Campo Hill" > > Sent: Friday, May 20, 2011 2:43:49 PM > [...snip...] > > path changes), and the new server was successfully added to our > > Active Directory domain. As the new server is NOT a member of > NIS, > > we made a copy of all the smb.conf-relevant groups to its local > > /etc/group and added all the users to the /etc/passwd file. With > > these changes we can access the shares using the AD usernames and > > passwords as long as they are not access-limited by "valid > users", > > so the integration of the server into AD is working. But if we > add > > a "valid users = @group" line to the share in smb.conf, it will > > Are you using local or AD users and groups or are you mixing them? You > say you have joined the server to AD and also added users and groups to > /etc/passwd and /etc/group. But when a user connects to the Samba > server from Win, (probably) his AD account is used, but in /etc/group, > the members are the local users, which need not be the same (depends on > more factors, like your NS switch settings for example). > Try to check that you're using the AD/local users/groups consistently, > or give more info related to this (e.g. from /etc/nsswitch.conf, > /etc/smb.conf ...). > > -- > Michal Belica - IT consultant > beli+...@beli.sk | www.beli.sk -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
[Samba] samba 3.6.0rc1 in Debian experimental
I have the pleasure to announce that the Debian experimental archive now carries packages for samba 3.6.0rc1. This happened 53 hours and 26 minutes after Karolin announced the availability of this new version..:-) Instead of re-explaining how the Debian experimental archive is working, please allow me to point to a quite complete Wiki page about it: http://wiki.debian.org/DebianExperimental 3.6.* packages will remain in Debian experimental until the release of the final version of 3.6.0. Then, packages will be uploaded to Debian unstable, thus targeting the next Debian version (and indirectly flowing to Ubuntu, of course). -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Samba 4 and gpo in win7
Hello Kalle, It looks better but according to what I see I think that you didn't update the code of samba4. Did you pull the latest changes ? and then compile and install it ? Matthieu. Hello! Attached a trace file while running gpupdate. Accessing sysvol works through: \\ip\sysvol and \\dc.domain_name\sysvol Doesn´t work through \\domainname\sysvol - Ursprungligt meddelande - Från: "Matthieu Patou" Till: samba@lists.samba.org, "samba-technical" Skickat: torsdag, 19 maj 2011 15:31:34 Ämne: Re: [Samba] Samba 4 and gpo in win7 On 12/05/2011 11:21, tae...@bredband.net wrote: Hello! Having an issue with getting gpo to apply for my win7 clients. Running samba4. Creating gpo with gpmc and they are created under var/locks/sysvol/"mydomain"/policies They applies just perfect on win xp clients but when trying on win7 clients they just won´t apply. When runnin gpupdate /force we get this(summary): So I pushed a few fixes in the Git tree of samba and made a lot of tests about this. First you need: host msdfs = yes in the [global] part of your configuration. Then reboot XP / windows7. Try to access \\domain.tld\sysvol and also navigate inside it. If it works it means that dfs for sysvol is working in most the case it will solve Windows7 problems with fetching the GPO. If not make trace from the samba server and send us for analysis, trace can be done like this: tcpdump -i any host ip_of_the_client -s 16000 -w /tmp/trace.pcap. Matthieu. -- Matthieu Patou Samba Teamhttp://samba.org Private repo http://git.samba.org/?p=mat/samba.git;a=summary -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] samba 3.6.0rc1 in Debian experimental
Hi Christian, On Fri, May 20, 2011 at 07:30:51PM +0200, Christian PERRIER wrote: > I have the pleasure to announce that the Debian experimental archive > now carries packages for samba 3.6.0rc1. This happened 53 hours and 26 > minutes after Karolin announced the availability of this new > version..:-) > > Instead of re-explaining how the Debian experimental archive is > working, please allow me to point to a quite complete Wiki page about > it: > > http://wiki.debian.org/DebianExperimental > > 3.6.* packages will remain in Debian experimental until the release of > the final version of 3.6.0. Then, packages will be uploaded to Debian > unstable, thus targeting the next Debian version (and indirectly > flowing to Ubuntu, of course). thanks a *lot*! :-) That makes testing pretty easy. Cheers, Karolin -- Samba http://www.samba.org SerNet http://www.sernet.de sambaXP http://www.sambaxp.org -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
