similar to: Debian Stable Samba 3.0.5 to 3.0.6 upgrade - broke my config?

Problem: When I try to open a samba share from a Windows 2003 R2 computer, I get a login challenge. When winbind and smb start up, the logs look clean except for the following: smbd.log -------- [2008/11/11 04:42:16, 3] lib/privileges.c:get_privileges(261) get_privileges: No privileges assigned to SID [S-1-22-1-0] [2008/11/11 04:42:16, 3] lib/privileges.c:get_privileges(261)

Hello all, I have a nice dual Opteron server with a lot of disk space I'd like to let Windows ADS groups use. I am running FreeBSD (AMD64) 5.4-RELEASE-p1 with samba-3.0.20,1 I joined the ADS domain. Smbclient works perfectly. Server shows up in "My Network Places" When I click on it, I get a login box and no credentials will authenticate me. Read some of the samba docs, and found

Hi, We have got problems mapping the homes drives of our users. We don't know how to fix it. Files: burz-nfs:/etc/samba # more /etc/krb5.conf [libdefaults] default_realm = TTDE.TRANSTEC.DE dns_lookup_realm = false dns_lookup_kdc = true default_tkt_enctypes = RC4-HMAC des-cbc-crc des-cbc-md5 default_tgs_enctypes = RC4-HMAC des-cbc-crc des-cbc-md5 clockskew = 600 [realms] TTDE.TRANSTEC.DE

Hi, Thanks to all who responded to my initial post to the list regarding "Ticket not yet valid" messages in my samba logs. I neglected to include this in my initial post - we had already suspected clock synchronisation problems, and all of our servers (AIX Samba server and windows clients) are all synchronised to the AD DC, which is sychronised to an internet atomic clock in Melbourne.

Hi, I'm having a problem with Samba 3 in AD mode. For some reason, the first time (usually first thing in the morning) a user tries to map a drive to my samba 3 server, the log shows a message "Ticket not yet valid". The user is prompted for username/password (they've already logged on to the windows domain, so they shouldn't be prompted. The user then waits for a minute or

Hello everyone, I'm sorry for this long post, but I think there is a real understanding problem for many people on ADS domain membership. I'm not the first to post about this type of problem, however I didn't find an answer to it in the archives and I followed the HOWTO-collection. Well, this is what I'm doing : I am using samba-3.0.1 compiled from source, MIT kerberos 1.3.1

=20 \\128.252.123.123\sharename <file:///\\128.252.123.123\sharename>=20 =20 And it works as expected - my clients are in the same domain, no password is asked for, etc. =20 Using any form of the hostname in the URI, either \\hostname\sharename <file:///\\hostname\sharename> or \\hostname.domain.name\sharename <file:///\\hostname.domain.name\sharename> in the URI will

Hi all, we here have a user that got a new Windows 7 client (before he had Windows XP) and now is no longer able to connect to our Samba shares. Testing his client with another account has proven that the client is not the problem, other user can connect. Also testing the user on another (Windows 7) client gave the result that the user is not allowed to access. Running Samba with different log

I have been fighting with this FreeBSD port for two days off/on Can anyone please suggest something? Even if it's paid support to fix this? Thanks! Eric [2005/11/03 17:03:17, 3] smbd/sesssetup.c:reply_sesssetup_and_X_spnego(619) NativeOS=[Windows 2002 Service Pack 2 2600] NativeLanMan=[Windows 2002 5.1] PrimaryDomain=[] [2005/11/03 17:03:17, 3]

I'm beating my head up against the wall here.. Need some extra eyes!!! Setup -- Samba4 Domain Controller and samba3 print server.. DNS FlatFile,, All dns works.. Issue, When I browse to the print Server vi \\IP-Address I am able to connect just fine.. When I browse using \\netbios-name I connect to the server but it opens up a username/pass dialog box and no name or passwords will work..

Hello all! We are currently testing the implementation of a multi-use server at my work. I am working with a Windows 2003 RC2 domain controller, and a CentOS 5 NIS/NFS/Samba server. I've followed various how-to's and researched several errors during the past sixteen hours working on this but all things I try seem to come back with empty results. I

Hi! I have samba4 domain controller + samba 3.4 member server. On XP login to domain and connection to member server works ok. Vista can login to domain but can't get connected to member server. Member servers log.smbd is following error with Vista client: ------------------- [2009/09/02 14:12:02, 3] smbd/process.c:1259(switch_message) switch message SMBsesssetupX (pid 30541) conn 0x0

I am struggling with a Samba/Server 2003 problem which doesn't make sense. I have compiled Samba 3.0.14a and MIT Kerberos 1.3.6 several times on different machines. I have a set of RPMS which work fine on one of my workstations, but do not work on the server. On the server I get the dreaded: reply_spnego_kerberos(173) Failed to verify incoming ticket! in the logs. I have compiled

Hello, I'm trying to access a samba share using an ADS user credentials. I always get an error, and the debug traces (log level = 5) are giving me the output in the follow. I have searched the samba ML archives, and I have found the thread http://lists.samba.org/archive/samba/2004-April/084545.html but, before asking the system admin to apply the eventual KB fixes, I would like to know if the

Hello, We are experiencing ADS lower performance on Samba-3.0.22 for HPUX. I did Google search, and find out one message posted at http://lists.samba.org/archive/samba/2005-November/114231.html at the earlier time. >From my observation, it seems there was a spin on reply_spnego_negotiate()/ reply_spnego_kerberos() calls that invokes register_vuid() to register uvid with different vuid# for a

Since I haven't gotten any responses from the segfault log I posted earlier, I will try another approach. Below is what happens when a client tries to connect. Again, this all started after I changed a username mapping entry from root = DOMAIN\Administrator to root = @"DOMAIN\Domain Admins". This is in a security = ADS setup. wbinfo -u and -g return the correct information.

I tried to use the samba share that I was able to access this morning, but now I cannot get to it. The error in the client's log is: Doing spnego session setup [2006/02/09 13:14:02, 3] ../smbd/sesssetup.c:reply_sesssetup_and_X_spnego(664) NativeOS=[Windows 2002 Service Pack 1 2600] NativeLanMan=[Windows 2002 5.1] PrimaryDomain=[] [2006/02/09 13:14:02, 10]

Hello everyone, I'm trying to make Samba authenticate clients against an Active Directory Server running on W2k3 R2. Samba is running on a Debian Linux: virtual-101:~# dpkg -l | egrep -i '(samba|kerb)' ii krb5-config 1.17 Configuration files for Kerberos Version 5 ii krb5-user 1.6.dfsg.3~beta1-2 Basic programs to

I recently upgraded a backup fileserver used for testing purposes from samba-3.0.10 to the current samba-3.0.11 using the FreeBSD portupgrade. The fileserver is setup in a W2K AD. The fileserver uses Winbind to get AD accounts and shares are created on the Samba server. Worked fine until the upgrade. Here is a copy of the current smb.conf [global] unix charset = LOCALE

Hi, all! I have the following environment here: - A Windows 2000 domain, with one server running Windows 2003 Server - A kerberos realm, using MIT Kerberos - A samba server, with security=ads The Windows 2003 server have a trust relationship with the MIT kerberos realm. Users logs on that kerberos realm on their Windows workstations, and are supposed to have access to the shares at samba