similar to: domain_client_validate error with Samba 3.2.13 on Debian Lenny

Hi, I have asked that last week with a little different subject, but the problem remains. When connecting with a Windows machine (not part of the domain) to the Samba server, the client is not authenticating, even when the user exists in the domain. Domain master is a Windows 2003 SBS machine, the Samba server is a Debian Lenny machine. The problem is occurring with Samba 3.2.13, with Samba

Hi Samba users - I recently upgraded my domain at home from being controlled by two somewhat messed up Windows DCs (one 2000 and the other 2003, messed up by my own inexpert management..) to a nice clean new single 2003 DC (SBS, if it matters). I rejoined all workstations, including a Redhat Fedora FC3 based machine, to the new domain. (Actually, I migrated all of the Windows workstations

All, we have a SAMBA server set up that has been working great for everyone in the corporate office, not to long ago I connected one of our foreigh offices to us through a VPN. All of our users authenticate to our PDC, our users in our foreign office, who is on the same domain but we have them on a different subnet, are not able to gain access to the SAMBA shares, here in the corporate office.

Hi I havee been trying to setup my Redhat 8.0 Linux as BDC, i have NT4 as my PDC. My smb.conf [global] workgroup=ITERNAL netbios name=TRIC server string=server Samba load printers=no printcap name=cups printing=cups print command=lp -d %p %s; rm %s invalid users=root log file=/var/log/samba/log.%m max log size=1000 syslog=0 smbpasswd file=/etc/samba/smbpasswd security=DOMAIN encrypt

Hi, I want vpn clients which have a valid x509 Cert and a valid user account in the M$ domain can access to the LAN. The M$ DC is an SBS2003 Server in mixed mode. I don't want to manage two user db's. I want the vpn server to ask the domain controller for a valid user account.So I've installed the nessecary stuff on the vpn server. The interresting things here are: samba/winbind

Hi, as I wrote before: I'm not able to connect a Windows XP Pro notebook to a Samba 3.0.4 server. All the other machines (most Windows XP Pro, but also a few Windows 2000 and Windows 98) can connect without any problem. This one machine is not part of the NT domain because it needs to connect 1 or 2 times a week only, and is on the road most of the time. The machine could connect

I?m running Debian Linux 3.0 r1 with Samba 2.2.8a and I have got printing problems: --- when I print something the job don't appear in the window printing status, so I have no way to check the actual status of the job, or to delete the job from window printer status in Win2K. here is configurations file of smb.conf: [global] workgroup = Gertian log level = 99 queuepause

Hi, In our network, I have set up a samba server in a workgroup. We're now migrating to a domain, using SBS 2003. When I locally login on XP and access the samba server, it works just fine. But, when I login on the domain and then try to access the same samba box, it doesn't accept my password. The username for my samba account and account on the domain are the same. Also, the name of

Hi, Samba 3.0.8 installed on Debian Linux server and setup to authenticate with Windows 2000 ADS. The samba config as follows. [global] workgroup = TEST_NT_DOMAIN realm = TEST-NT.ORG server string = TEST SAMBA security = ADS obey pam restrictions = Yes password server = 10.10.20.253 10.10.20.227 passwd program = /usr/bin/passwd %u

Hi, after the installation of Samba 3.04 (upgrade from 3.02) a single XP notebook cannot connect to any share. The log shows these messages: [2004/05/17 11:48:18, 0] lib/util_sock.c:read_socket_data(367) read_socket_data: recv failure for 4. Error = Connection reset by peer [2004/05/17 11:48:18, 1] smbd/service.c:close_cnum(801) andreasxp (192.168.1.102) closed connection to service

Hi, I' m not very happy with Samba3 as I have very heavy problems with filenames containing umlaut characters. I have installed a new Debian 3 server for a client with Samba 3.0.1 (Debian packages), and copied over the data from a SuSE 6.4 (Samba 2.2.8a) system by mounting the hard disk into the new system. Now, I cannot access the files and directories with umlaut characters anymore. I

hello, i have this pcmcia card with two rs-232 connectors - http://www.sunix.com.tw/ipc/sunix_en/detail.php?class_a=16&prod_id=57#spec it is sunix CBS2000X with Oxford CF950 UART (16C950 compatible) host controller. but it doesn't seem to work with fbsd, i have added this record do pucdata.c { "Sunix CBS2000X", { 0x1409, 0x7168, 0, 0 },

-----BEGIN PGP SIGNED MESSAGE----- Im currently running some tests for a samba/CUPS based print server. The print server is a member of an NT domain and uses winbind to import NT domain users. Users accessing the print server will be not from the same domain but from trusted domains. Everything basically seems to work, once you use sufficiently new versions of cups and samba. (I'm on Debian

Hi, I am running Samba 3.0.1 on a Debian/Sid machine. I have installed winbind to access the AD of the local network, which I want to use for UNIX logons. wbinfo -u shows all the users of the AD, but "getent passwd" only shows the contents of the file /etc/passwd. I have been following the instruction for winbind (Chapter 21) in the Samba-HOWTO-Collection. Any comments would be

Release Announcements ===================== This is a security release in order to address CVE-2009-1886 and CVE-2009-1888. o CVE-2009-1886: In Samba 3.2.0 to 3.2.12 (inclusive), the smbclient commands dealing with file names treat user input as a format string to asprintf. With a maliciously crafted file name smbclient can be made to execute code triggered by the server.

Release Announcements ===================== This is a security release in order to address CVE-2009-1886 and CVE-2009-1888. o CVE-2009-1886: In Samba 3.2.0 to 3.2.12 (inclusive), the smbclient commands dealing with file names treat user input as a format string to asprintf. With a maliciously crafted file name smbclient can be made to execute code triggered by the server.

I have a problem with a Member Server on Samba 3.0.28a running on Ubuntu Heady. Both systems were recently upgraded using Ubuntu's automated upgrade. It's also possible I broke a working configuration by accident. The shares on the Member server are visible on the XP clients and some users can authenticate properly. At least one user on one XP desktop cannot. The shares are visible

Hello all! We recently upgraded from Samba 2.2.3 to Samba 2.999+3.0.alpha20-3 on debian 3.0. Ever since then users are unable to change their own passwords on their W2k machine. What happens is when they try to change it a process (passwd) gets stuck with the users name. The only way to fix this is to kill the passwd process the user started. I haven't changed the "passwd chat"

Hi! I have a samba 2.2.3a-12 on a Linux Debian box (lets call it pdcMachine) with a 2.4.16 kernel acting as a PDC of some domain (lets call it myDomain). I have a samba 2.999+3.0.alpha20-4 workstation (debian,kernel 2.4.19) (lets call it wstMachine) and i'm trying to join wstMachine to myDomain. I added: workgroup = myDomain password server = * security = domain encrypt passwords =

Hello everyone! I'm trying (unsuccessfully until now) configure two Samba servers: - Server A. Acting as PDC in a Windows 2000/XP domain and as profile server. - Server B. Acting as profile server. I have users whose profiles are in server A and others whose profiles are in the server B. The server where each user's profile lives is identified by the main group (GID) of the user (that