similar to: No subject

I was running 3.0.25c (I think) LDAP PDC for a couple of years and just tried swapping in a new 3.5.4 setup. I had some problems so I wiped all the entries and *.tdb files, and started from scratch. Problem in a nutshell: I can't browse the domain normally, nor can I logon to the domain. However I can access the server shares fine if I point to the server specifically. SOMETIMES this will

I'm trying to use a Samba (3.0.37) share on my ASUS RT-ac66R router as a destination for scans from my Kodak Office Hero 6.1 all-in-one printer. I'm currently getting an invalid User ID or Password error message. I have been unable to increase the Samba log level at all even after editing the log level in smb.conf. Before an old router running DDWRT (including Samba) failed, scanning to

Samba 3.0.28a-0.fc8 & Windows XP. When logging on to machine 'A' one of my users gets an "Access Denied" message for a particular cookie file -- 'statse'. When logging on to another machine ('B'), there is no problem. I have tried, when logged in as administrator (mapped to root on the server), to read the cookie file on both machines. Machine 'A'

Hello, I replaced an NT4 server by a Samba 3.0.14a ldap server following the instructions in 'Samba by example'. Everything works fine except for some files on a W2003 SP2 server: - when the W2003 server uses the Linux PDC, from a WinXP client, some files are not writable, and ACLs can be listed but not changed. - when the NT4 server is up, the same files on the W2003 server can be

I have two domains, one called CORP (which is 2003 AD) and the other is called LABS (which is running Samba 3.5.4-5.1.2). I have established bi-directional trust between them and most of the basic tests show apparent success. However there are a couple of issues left that I am trying to chase down. First issue is that I would like to filter out the local (LABS) users and groups in winbind if

When I made the move to 3.0, I noticed that smbclient no longer works with null passwords. Am I missing something? I read the FAQ, which suggests that the server is rejecting the null password. But I know that null passwords work fine for the 2.2.8a client, so the server is not the issue. The FAQ recommends "smbclient -L host -U%", but I don't want to set the username to null. I

I think I've found out why MacOS 10.5.x (Leopard) clients are unable to connect to Samba shares when authenticating with Kerberos. Basically, the Leopard Macs insert a few extra bytes (Padding and reqFlags, according to wireshark) into the security blob within the Session Setup AndX Request packet, bytes whose start tag is 0xa1, in a spot where Samba's parser expects 0xa2. The critical

Here is a second, somewhat related question to my last one. When looking over the network trace I have ran into something I cannot explain. It may be quite proper, in which case I am misreading the trace. But I would appreciate it if someone would explain this to me. In packet 109 of the trace (during a login with no profile on the server), I see a "NT Create AndX request"

I'm using samba-3.0.23d-19 on openSUSE 10.2 with an LDAP PDC arrangement I'm trying to sort out some problems with adding a trust relationship. Specifically, smbpasswd is failing when I try to create/modify the domain account. Further investigation shows that it is also failing to modify workstation accounts. However it is able to modify user accounts fine. The big difference here seems

Good day time! We've noticed the following issue with Samba 3.0.1 on Linux. When SMB client asks for the first time on FID for a locking or read request on an opened file, it causes an ACK to be sent from client side. Windows server also requests ACK BUT much more rarely. Sending ACK causes additional overhead when working in heavy locking and unlocking environment. Windows server

Good day time! We've noticed the following issue with Samba 3.0.1 on Linux. When SMB client asks for the first time on FID for a locking or read request on an opened file, it causes an ACK to be sent from client side. Windows server also requests ACK BUT much more rarely. Sending ACK causes additional overhead when working in heavy locking and unlocking environment. Windows server

I keep getting this kind of stuff in /var/log/messages Jan 18 17:45:03 bulldog tripplite_usb[9979]: libusb_get_interrupt() returned -110 instead of 8 Should I be worried about it? upsc seems to work fine... I tried building the 2.0.5 but none of the included spec files seemed to work with opensuse 10.2 and adapting their 2.0.4 spec file didn't seem to work out well either. Building from

I keep getting this kind of stuff in /var/log/messages Jan 18 17:45:03 bulldog tripplite_usb[9979]: libusb_get_interrupt() returned -110 instead of 8 Should I be worried about it? upsc seems to work fine... I tried building the 2.0.5 but none of the included spec files seemed to work with opensuse 10.2 and adapting their 2.0.4 spec file didn't seem to work out well either. Building from

When I made the move to 3.0, I noticed that smbclient no longer works with null passwords. Am I missing something? I read the FAQ, which suggests that the server is rejecting the null password. But I know that null passwords work fine for the 2.2.8a client, so the server is not the issue. The FAQ recommends "smbclient -L host -U%", but I don't want to set the username to null. I

I use Samba 3.14.17 and later test Samba 3.6.9. The computer is WINs server on Samba. wins support = yes All work good. But now I see that NetBIOS clients cannot to re-register their names on WINs, when he change IP. >From WinXP SP3 I do nbtstat -RR Answer: NetBIOS-names registered by this computer were changed. >From server: relay2# nmblookup -U 10.0.0.1 -R -S aiy querying aiy on

Hi all, we have got 4 Samba Servers. All BDCs for "MYDOMAIN", except by SERVER3 that is a PDC. All of them have 3 physical Network interfaces, from which 2 are used by samba. Each of them has a several ip aliases, except by SERVER1 which has only primary ip numbers on its interfaces. When I try to join a new Windows client (XP SP3) to the domain. It asks our wins server for

Dear Samba gurus, I am setting up file sharing between a new linux box running RedhHat 7.3 and a W98 PC, and almost have things running but have run into a problem that is beyond my ability. I have W98 set up for PlainText password, and have set up Samba to match. Everything seems fine on the linux box. When I enter: smbclient //irisarian/rout -U Gerry%PassWd the connection succeds and

Hello List We run a Solaris9 Server running Samba 3.0.20, Local Users (no winbind) but authenticating against ADS. There are up to 800 concurrent users, mostly Windows XP SP3. When clients access MyDocuments, which is redirected to the Samba share, we observe several "Session Setup AndX Request"s followed by "Session Setup AndX Response, Error:

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi! I have a user who is running a Samba server to store data files for his ArcView 3.3 application. Client operating system is Windows XP professional. With Samba2 (2.2.8a) this was working quite fine, it usually took less than a few seconds to load and render one of the GIS presentations with ArcView. We then did an upgrade to Samba3 (3.0.20b)

I'm running the samba-client-3.0.20-0.1 SUSE RPM. I was using the version that came with 9.3 but upgraded to see if this specific problem would go away. Guest access does not appear to be working correctly, and it looks like the problem is due to guest not getting mapped into the LDAP query correctly. Specifically, I can login with local account, join workstation to the domain, browse