similar to: 3.0.7 - NT Create AndX Response, Error:, QUERY_PATH_INFO, Error:

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

Mates, I have configured samba 100 times, but this time, I'm doing something increadibly stupid that I just cannot see. Please HELP! I'm about to jump...... Background, Old samba sever (nemesis) being replaced with new one (bonza). Both are up and operating. All networking is OK, Name resolution is fine, etc. The problem is that all users can see all the shares on the

Recently I had the chance to look at smb service response times over OpenVPN using Wireshark/TShark. Here are 2 samples. In both samples a Win XP Pro machine is connecting to a server running samba-3.3.7 and openvpn-2.0.6_9 on FreeBSD 7.2-STABLE. Location #1 =================================================================== SMB RTT Statistics: Filter: Commands Calls Min

Hi, I'm trying to replace a windows fileserver server with a Fedora Core 2 samba server in our Windows 2000 ADS domain. A performance problem occurs when accessing certain samba shares from Windows Explorer on either an Windows XP or a W2K client machine. It can take up to a minute for explorer to list files in a share folder containing only a few files! It eventually does, but but reports

Hi, We're doing some of performance tests with Linux Samba v3. We're comparing WinXP/Win2k clients vs OS2 clients accessing a samba server. For one test, we're coping 10.000 small files. Let's say, we run the command copy \\sambaserver\10000files\*.* c:\data\10000files With an OS2 client it takes 23 seconds to complete. With an Windows client it takes 460 seconds to complete.

Hi, We're doing some of performance tests with Linux Samba v3. We're comparing WinXP/Win2k clients vs OS2 clients accessing a samba server. For one test, we're coping 10.000 small files. Let's say, we run the command copy \\sambaserver\10000files\*.* c:\data\10000files With an OS2 client it takes 23 seconds to complete. With an Windows client it takes 460 seconds to complete.

Listmates, I have had a few boxes where the 'matchname' message is filling my syslog with one new message ever ~40 seconds or so. No performance problems, just the log annoyance. An example of the messages are: Jan 11 13:43:03 nemesis smbd[2246]: [2010/01/11 13:43:03, 0] lib/util_sock.c:1685(get_peer_name) Jan 11 13:43:03 nemesis smbd[2246]: Matchname failed on Adrienne-PC.rbpllc.com

Dear all, My question is described as follows. Server: Linux Samba-3.3.1 Client: Windows XP with SP3 Step1: connect to the samba server. Step2: select a directory name ?test?. (The directory is created before testing.) The client will send a lot of QUERY_FILE_INFO requests. According to data captured by Wireshark, I find the following phenomenon: The client repeats exactly the same

Launching workstation local applications creates SMB traffic and STATUS_NO_SUCH_FILE errors I am using Samba 2.2.12 as a domain controller without any use of roaming profiles. Everything is working fine, but I have noticed some strange behavior. I've been working on a problem for quite some time. No matter what local application I launch on a workstation, I will see the following server

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

Guys, After upgrade to samba 3.3.4 on openSuSE 10.3, I'm getting: Jul 10 02:05:14 bonza smbd[31942]: [2009/07/10 02:05:14, 0] lib/util_sock.c:write_data(1136) Jul 10 02:05:14 bonza smbd[31942]: [2009/07/10 02:05:14, 0] lib/util_sock.c:get_peer_addr_internal(1676) Jul 10 02:05:14 bonza smbd[31942]: getpeername failed. Error was Transport endpoint is not connected Jul 10 02:05:14 bonza

Samba Version: 3.4.7 OS: Ubuntu Lucid 10.04 Setup: This samba box is a member of a win2k active directory domain and functions as a file server. Files/directories shared out utilize file system acls. smb.conf portion for share in question: [Accounting] comment = Accounting Share path = /netdrives/accounting browsable = yes read only = no map archive = no map system = yes

Mates, The saga continues, but THANK GOD 'make revert' WORKS. Here is my problem. I am trying to compile 3.0.7 from source and install it on my Mandrake 7.2 box. The gcc compiler is 2.95.3. Here is what I have done: [stop samba] # ./configure --prefix=/usr --with-smbmount # make # make install # /etc/rc.d/init.d/smb start Here is what I get: [root@Nemesis david]# tail

Mates, What would cause smbclient not to list my printer share?? (mandrake 7.2, 2.2.19 kernel) [david@Nemesis david]$ smbclient -U% -L localhost Domain=[RB_LAW] OS=[Unix] Server=[Samba 3.0.7] Sharename Type Comment --------- ---- ------- guillory Disk David Guillory Bertin Disk Darren Bertin Rankin

James, I have sent this to you directly and cc:ed the list for reasons that should become apparent below. THE SITUATION OS: mdk 7.2, 2.2.19 kernel - basically bone stock Latest addtions: samba 3.0.7-1 compiled from source (working fine); cups-1.1.18-1 from mdk rpm Reasons for additions: XP SP2 fun and games THE MYSTERY As any normal person does, I use

Listmates, After wrangling with the voltage value on the CyberPower 1000AVRLCD and now having 2 of them working, I though it would be a simple matter to move my APC BP650 from apcupsd to nut so that all 3 servers would be monitored on the same web interface. The APC is attached to an older box running openSuSE 11.0 with nut-2.2.2-66.1. (nut-classic). The APC BP650 uses a serial connection

I never thought it would happen to me, but it did... I have read threads about slow copies from WinXX to Linux/Samba on the list in the past, but I don't recall a concise answer regarding what the cause was. THE PROBLEM: Trying to copy an 8 meg file from Win95 to my Linux/Samba box (named "Nemesis" - for good reason), the transfer speed slows to a crawl. The Win95 copy dialog box

Greetings, in our small network with about 10 Clients I got a problem when opening files or directories. If there were no actions between server and client for about 2 minutes or more, the very first action (open file, change path, etc) needs a long long time. The problem occurs on some clients (win 2k/xp), but not on every client. I tried a working smb configuration from home, but still no

Cross-posting scares me, but... Have you looked at the latest RPMs for SuSE, from ftp://ftp.suse.com/pub/projects/samba/ ? They've worked like a charm for me, thus far (revision after revision, a simple rpm -U * seems to work...) -----Original Message----- From: david rankin [mailto:drankin@cox-internet.com] Sent: Mon 9/12/2005 5:30 PM To: samba; Suse Linux Subject: [SLE] SuSE 9.3 and

Mates, I dunno if nobody else is using the samba binaries to put 3.0.20-1 on SuSE 9.3 -- or -- if I'm just doing something stupid, but there seem to be library problems. Specifically, we are getting library errors for the *.so.2 libraries, regardless of whether we try via YAST or RPM. david@nemesis:~/Documents/linux/rpms/samba320> ll total 19970 -rw-r--r-- 1 david users 60998