search for: 2k3sp1

Displaying 11 results from an estimated 11 matches for "2k3sp1".

2005 Aug 29
2
Username Case Sensitivity vs. Lower Casing
...Service Pack 1 and we started experiencing incompatibilities with winbind. Looking at the latest Release Notes for Samba 3.0.20 from Aug 19, 2005 told me the following: Common bugs fixed in 3.0.14a include: o Compatibility issues between Winbind and Windows 2003 SP1 domain controllers (*2k3sp1*). So I upgraded to latest Samba 3.0.20 and indeed the compatibility issues with 2k3sp1 went away, but another thing I noticed is that winbind seems to have reverted back to pre 3.0.8 case sensitive username behavior. I had to rename all the directories and stuff again. Unfortunately now if som...
2005 Apr 18
0
Announcement Samba 3.0.14a
...e SuSE und Redhat-Versionen sowie f?r Debian GNU/Linux k?nnen von ftp://ftp.sernet.de/pub/samba/ heruntergeladen werden. Pakete f?r S390 folgen in K?rze. Dieses Samba-Release behebt einige Fehler, darunter: * Kompatibilit?tsprobleme zwischen Winbind und Windows 2003 SP1 Dom?nencontrollern (*2k3sp1*). * MS-DFS Fehler mit Windows XP SP2 Clients. * Hohe CPU-Auslastungen durch Endlosschleifen in dem FindNext() Server Code. * Ung?ltigen SMB_ASSERT(), der smbd panic bei Dateien mit ACLs verursacht hat. Au?erdem gibt es eine die smb.conf Parameter betreffende ?nderung: * dos filetimes ist jet...
2005 Jun 14
1
Proper behavior of Interdomain Trust uid mappings
Hi there, I'm running Samba 3.0.14a-sernet on Suse 9.1 using ldapsam. I've got an interdomain trust setup across a vpn connection with a 2k3sp1 domain (DOMB). The trust works. What is strange is that a user from DOMB can't access any shares until they browse a share on our domain controller, say netlogon, then samba creates a new posix account for them in the ou=users base. I have nsswitch.conf using ldap, and samba configured to use w...
2006 Jun 02
4
smbmount and win2003 sp1
...lhost/share1 /tmp/mountest -o = username=3Ddomainu1,password=3Dpassword ERRDOS - ERRnoaccess (Access Denied.) SMB connection failed I also checked the release note about the issue, and found a fix on = 3.0.14a about: Compatibility issues between Winbind and Windows 2003 SP1 domain = controllers (*2k3sp1*). Does it fix my bug? My version is 3.0.21c. Why did I have the problem? Thanks, LatrellFrom inlovewithgod at gmail.com Fri Jun 2 13:49:33 2006 From: inlovewithgod at gmail.com (Jeremiah Martell) Date: Fri Jun 2 13:57:00 2006 Subject: [Samba] Getting NTLM group info about user Message-ID: &lt...
2005 Apr 12
0
Samba 3.0.14 and 3.0.15pre1 Available for Download
...ease of Samba. This is the version that production Samba servers should be running for all current bug-fixes. Please read the following important changes in this release. Common bugs fixed in 3.0.14 include: ~ o Compatibility issues between Winbind and Windows 2003 SP1 ~ domain controllers (*2k3sp1*). ~ o MS-DFS errors with Windows XP SP2 clients. ~ o High CPU loads caused by infinite loops in the FindNext() ~ server code. Samba 3.0.15pre1 is a preview release of the Samba 3.0.15 code base and is provided for testing only. This release is *not* intended for production servers. However...
2005 Apr 15
0
Samba 3.0.14a Available for Download
...ase of Samba. This is the version that production Samba servers should be running for all current bug-fixes. Please read the following important changes in this release. Common bugs fixed in 3.0.14a include: ~ o Compatibility issues between Winbind and Windows 2003 SP1 ~ domain controllers (*2k3sp1*). ~ o MS-DFS errors with Windows XP SP2 clients. ~ o High CPU loads caused by infinite loops in the FindNext() ~ server code. ~ o Fixed invalid ASSERT() call that caused an smbd panic ~ when accessing files with ACLs. ================ Download Details ================ The uncompressed...
2005 Apr 15
1
Samba 3.0.14a Available for Download
...ase of Samba. This is the version that production Samba servers should be running for all current bug-fixes. Please read the following important changes in this release. Common bugs fixed in 3.0.14a include: ~ o Compatibility issues between Winbind and Windows 2003 SP1 ~ domain controllers (*2k3sp1*). ~ o MS-DFS errors with Windows XP SP2 clients. ~ o High CPU loads caused by infinite loops in the FindNext() ~ server code. ~ o Fixed invalid ASSERT() call that caused an smbd panic ~ when accessing files with ACLs. ================ Download Details ================ The uncompressed...
2005 Apr 12
1
Samba 3.0.14 and 3.0.15pre1 Available for Download
...ease of Samba. This is the version that production Samba servers should be running for all current bug-fixes. Please read the following important changes in this release. Common bugs fixed in 3.0.14 include: ~ o Compatibility issues between Winbind and Windows 2003 SP1 ~ domain controllers (*2k3sp1*). ~ o MS-DFS errors with Windows XP SP2 clients. ~ o High CPU loads caused by infinite loops in the FindNext() ~ server code. Samba 3.0.15pre1 is a preview release of the Samba 3.0.15 code base and is provided for testing only. This release is *not* intended for production servers. However...
2005 Apr 14
1
Winbind User Login Troubles
I am running Samba version 3.0.9-1.3E.2 on a server that is joined to a windows server 2003 domain using ADS security. The samba server hosts a share called 'files'. I am having problems mounting this share using a new account I set up. getent passwd shows the information for the new account as does wbinfo -u. Mounting the share with the new users account using the net use command
2006 Jan 18
4
Linux/AD authentication stops working after ~5 minutes
I'm trying to do something fairly simple: login to a Linux box using a Windows AD-based account. I've followed the various recipes available online for configuring Linux (winbind, PAM, etc.) to this send, and I've got it working ... almost. I'm able to authenticate an AD-based user immediately after bringing up the Linux box, but a short time later (roughly 5 minutes, but it
2005 Jul 22
1
winbind lookup errors
Hello Samba folks, I have recently begun seeing some disturbing behavior from winbind. Winbind will fail to look up users and groups. Examples: The machine is configured to use winbind as a nss module. "getent passwd <username>" will yield no results. "wbinfo -n <username>" will yield "Could not lookup name <username>" "wbinfo -g"