similar to: What controls the Read AndX Request byte size?

After migrating a particular W2K file service to Samba 3.0.21c on SuSE 9.3 Pro (a DMS with winbindd against a W2K3 ADS), the W2K clients are suffering performance issues (in a switched LAN). Looking at the traffic with Ethereal (latest SVN), it looks like the client writes the data in *1 byte* pieces likes this (c=client, s=server): c->s NT Create AndX Request c<-s NT Create AndX

This sounds more like an Windows problem, but it is an interaction with Samba and I'm hoping someone has an idea of where to start looking. 3 times in the past week I've had a user (different user each time) come to me saying their P: drive is inaccessible, access denied. The P: drive is set in the user's Active Directory Profile as their home directory \\sambaserver\home$\%username%

We are experiencing some slowness when opening files from a Samba file share using Microsoft Word 2003. Upon examination with Ethereal it became apparent that Session Setup AndX calls are taking a long time to complete, varying from 2 to 8 seconds between the time the client provides an NTLMSSP_AUTH and the server responds. I have also noticed a peculiar NetBIOS name query for

Does samba server handle multiple smb commands (not necessarily andx commands) within one packet? If a client were to send commands such as 0x2f, 0x32, 0x32 in one packet instead of three separate packets, does samba server handle it i.e. respond to each of the three requests?

Hi all I have two samba PDC installed according to these specifications: domain FOOBAR with pdc server name: BAR (ip 192.168.1.1) opensuse 11.1 samba-3.5.6-15.1 openldap2-2.4.12-5.6.1 smbldap-tools-0.9.5-25.1 A winxp called USUARIO1 joined to the FOOBAR domain (ip 192.168.1.100) domain LAPAZ with pdc server name: SERVERLPZ (ip 192.168.10.4) openSUSE 12.2 samba-3.6.7-48.12.1.i586

Hi all, I'm running version 3.0.28a on Ubuntu linux, and apparently from a day to another I got performance issues: without any change in smb.conf (except a few added shares) I have mac osx and linux clients getting a very slow upload/download speed. I've checked with other protocols, like scp and performances are good, so I can exclude a network/hardware problem. Other clients are

Samba errors with smb QUERY_PATH_INFO, Error: STATUS_OBJECT_NAME_NOT_FOUNDFrom: Timothy D Newcomb Subject: Samba errors with smb QUERY_PATH_INFO, Error: STATUS_OBJECT_NAME_NOT_FOUND > Did you get an answer for this ? I am seeing it on an XP box and I have > the same problem..slow load time...in "my computer" Tim, No I didn't, thanks for the reply. I just figured that

Hi, Iam trying to setup Samba version 3.2.3 on Redhat (RHEL5) server to use Active Directory for authentication. I followed the instructions from article in following website: http://technet.microsoft.com/en-au/magazine/dd228986.aspx Setup Winbind + Samba + Kerberos and it seems to work fine. I can see the users in Active Directory through winbind as well as authenticate users using NTLM

In a follow-up to a previous post a couple weeks back, we've implemented a Samba 3.0.20 (Suse packages on 10.0 - recompiled to include idmap_rid) server to replace the Windows 2000 file server in our Win2003 Active Directory. For the most part things have been going well, but occassionally people will get access denied errors to things that they were accessing just fine minutes before. With

Hello everyone, I'm currently writing an SMB client program but I ran into a nasty bug. The problem occurs if I send an trans2 request (find first2 for example) after an andx create request; the returned error in the trans2 request is STATUS_INVALID_INFO_CLASS. I have no idea what that means...did not find any information regarding this. The error/problem does not occur when I don't

Hi, list: Our printers are using samba-3.0.37, and we hit a problem recently when doing file transfer to Windows 2008 Server Clusters. The error occurs when the printer attempts to locate the file path and uses the server IP address rather than the hostname: ====================================================== 18 21.335677 13.121.8.162 13.121.8.3 SMB Session Setup AndX Request,

Hi, I am having a lot of trouble with getting 0s2 to talk with samba. They seem to be making the right noises at handshake time, and seem to set up a session no problems (using ethereal, monitoring packets). However, when it comes to actually transferring information (such as doing a listing of a share from the os2 box) it crashes with the error: Open AndX Request, Path: \OSO001.MSG; Read

I've been here before but I'm still battling with getting Samba to work right with my XP Pro clients. In a nutshell, when I try to access a share, it asks for a username and password. I enter a username and password and it simply goes right back to the prompt, asking again. This is when it's set up as a domain controller. I should note: I CAN join the domain. I DO have my

Hi list, I am encountering a problem in connecting a Windows 2003 to a Samba 3.0.21b server. The Samba server is configured to have a security = share option, so that no password is needed. I can connect to the server by typing "net use z: \\192.168.51.1\data", and it is successful. However, if I try to do "dir z:", no file found! Same behaviour are found in Windows

Hi, I am enhancing the Samba Server on our product (VxWorks on the box) to support Long Name. So I started implementing the dialect "LM1.2X002" (first dialect that supports Long Name, the current dialect that we support are PC Network Program). I have implemented the Negotiation, Tree Connect AndX, Open AndX and Transaction2 (FIND_FIRST2) commands etc. I am able to open the shared

Hi, I am enhancing the Samba Server on our product (VxWorks on the box) to support Long Name. So I started implementing the dialect "LM1.2X002" (first dialects that support Long Name, the current dialect that we support is PC Network Program). I have implemented the Negotiation, Tree Connect AndX and Open AndX command. When I try access the shared drive of our product, after the

I had samba running fine on a Fedora 6 machine. I've upgraded to Fedora 11 and I'm getting huge delays when first accessing a folder. With Fedora 11 I'm ussing samba-3.3.2-0.33.fc11.i586. I'm getting about 60+ second delays before being requested to enter my username/password. I've used WireShark and can see 1) Session Setup AndX Request, NTLMSSP_NEGOTIATE 2) 20 seconds

<earlier, David Rankin wrote to no avail:> Mates, I have been watching a developing problem over the past few weeks. Most likely a M$ patch to XP that has caused problems. What happens is that XP clients try to open the standard "File" -> "Open" dialog (like in word, or whatever) and the file open dialog hangs and stops responding for 15 seconds or so. I have

I noticed your comments on the samba web site about the performance issue you were experiencing with the delay in opening files. I am having similar issues when accessing files off the server, I was wondering if you ever found a resolution or cause to the problem. The strange thing is that I have two identical computers and am experiencing the issue only on one. Sincerely, Frank Damen IT

Hi All, I'm really sad that Win2k3 server runs a lot better in a shared folder that keep a file based database that Windows 9x and WinNT clients. Explaining it better... Here in Brazil, unfortunaly we still have a lot business that is based in the old file shared database, like Dataflex, Clipper and like. Then, they need a robust and fast server to centralize that files. With Windows98