search for: query_file_info

....004886 10.16.37.96 10.240.47.86 SMB NT Create AndX Request, Path: \1000\0D02_1707.IN 29 1.005129 10.240.47.86 10.16.37.96 SMB NT Create AndX Response, FID: 0x1cf0 30 1.005373 10.16.37.96 10.240.47.86 SMB Trans2 Request, QUERY_FILE_INFO, FID: 0x1cf0, Query File Internal Info 31 1.005615 10.240.47.86 10.16.37.96 SMB Trans2 Response, QUERY_FILE_INFO 32 1.006102 10.16.37.96 10.240.47.86 SMB Trans2 Request, QUERY_FILE_INFO, FID: 0x1cf0, Query File Basic Info 33 1.006104 1...

....004886 10.16.37.96 10.240.47.86 SMB NT Create AndX Request, Path: \1000\0D02_1707.IN 29 1.005129 10.240.47.86 10.16.37.96 SMB NT Create AndX Response, FID: 0x1cf0 30 1.005373 10.16.37.96 10.240.47.86 SMB Trans2 Request, QUERY_FILE_INFO, FID: 0x1cf0, Query File Internal Info 31 1.005615 10.240.47.86 10.16.37.96 SMB Trans2 Response, QUERY_FILE_INFO 32 1.006102 10.16.37.96 10.240.47.86 SMB Trans2 Request, QUERY_FILE_INFO, FID: 0x1cf0, Query File Basic Info 33 1.006104 1...

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 queries many times before giving up. The whole network log repeats exactly the same sequence, only the FID is different every time. In my test FID changes from 0x3002 to 0x306a. I...

...N). 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 Response c->s Trans2 Request, SET_FILE_INFO c<-s Trans2 Response c->s Trans2 Request, QUERY_FILE_INFO, Query File Basic Info (1004) c<-s Trans2 Response c->s Write AndX Request, 1 byte at offset 119 <-- sigh c<-s Write AndX Response, 1 byte c->s Trans2 Request, QUERY_FILE_INFO, Query File Standard Info (258) c<-s Trans2 Response c->s Write AndX Request, 1 byte at offset 155 &...

...YYY SMB NT Create AndX Request, FID: 0x1dc7, Path: \Mp5data\Mp5Backups\Backup 2004-2011 1038 0.001180 192.168.0.YYY 192.168.0.XX SMB NT Create AndX Response, FID: 0x1dc7 1039 0.001407 192.168.0.XX 192.168.0.YYY SMB Trans2 Request, QUERY_FILE_INFO, FID: 0x1dc7, Query File Internal Info 1040 0.001452 192.168.0.YYY 192.168.0.XX SMB Trans2 Response, FID: 0x1dc7, QUERY_FILE_INFO 1041 0.001841 192.168.0.XX 192.168.0.YYY SMB Trans2 Request, QUERY_FILE_INFO, FID: 0x1dc7, Query File Standard In...

...prising difference between the 16MB > and 32MB transfers. For approximately .8 seconds before the transfer > begins, the following conversation occurs over and over: > > Windows>Linux Write AndX Request > Linux>Windows Write AndX Response > Windows>Linux Trans2 Request, QUERY_FILE_INFO, FID: 0x212a, Query File > Standard Info > Linux>Windows Trans2 Response, QUERY_FILE_INFO > > I have tried all of the recommended SAMBA performance tweaks that I > can find, but none seem to affect this dropoff. Has anyone seen this? > It appears to be a bug in either Samba o...

...1264 0.12484 0.93606 0.14180 Transaction2 Commands Calls Min RTT Max RTT Avg RTT FIND_FIRST2 204 0.12546 0.54965 0.14905 QUERY_FS_INFO 93 0.12489 0.20448 0.13657 QUERY_PATH_INFO 425 0.12507 0.36258 0.13878 QUERY_FILE_INFO 2371 0.12427 0.88422 0.13971 SET_FILE_INFO 5 0.12780 0.13102 0.12943 GET_DFS_REFERRAL 1 0.12902 0.12902 0.12902 NT Transaction Commands Calls Min RTT Max RTT Avg RTT NT IOCTL 15 0.12761 0.21489 0.14543...

...process is identical up to the point that the cookies are read: a. successful read: -> Read AndX Request, FID: 0x1402, 172 bytes at offset 0 <- Read AndX Response, FID: 0x1402, 172 bytes The data is definitely there in this response packet. -> Trans2 Request, QUERY_FILE_INFO, FID: 0x1402, Query File Network Open Info <- Trans2 Response, FID: 0x1402, QUERY_FILE_INFO -> Read AndX Request, FID: 0x1402, 172 bytes at offset 0 <- Read AndX Response, FID: 0x1402, 172 bytes The data is in this packet as well !! -> Close Requ...

...). The popup window only appears after 80 seconds. On another XP workstation (in the same room, same switch ...), it works OK. We have dumped the network traffic from both these workstations, and the result is that from the buggy workstation, the amount of traffic is around 30Mb, with the same QUERY_FILE_INFO sent thousands of times (subcommand 0x0007). This problem is having a big impact on our performance. Is it a known issue ? (We can provide the dumps) Thanks a lot. Jean-Philippe FARCY, Administrateur Syst?me SIGMA Informatique http://www.sigma.fr

...me point before the Delayed Write Failure and eventually a return status of STATUS_INVALID_HANDLE triggers the error message when the application attempts to access the now presumably stale handle? From the various network traces I've captured the STATUS_INVALID_HANDLE is in response to a QUERY_FILE_INFO on the problem file. What's puzzled me is that I'm seeing many STATUS_INVALID_HANDLE responses that don't correlate to any visible errors on the client side. Should we be expecting many STATUS_INVALID_HANDLE responses relating to files in a network based roaming profile? I'm co...

Hello mailinglist, I have a strange problem, which occurs sometimes on some WinXP clients. It is not 100% reproducable for me, but it returns regular. The problem is, that somehow a user can't delete a directory. All files in the directory will be removed successfully, but the directory itself not. Deleting with the Explorer or over the cmd-console returns in the same result. First the

...Protocol Info 175 315.610912 192.168.4.230 192.168.4.210 SMB NT Create AndX Response, FID: 0x169e No. Time Source Destination Protocol Info 176 315.611072 192.168.4.210 192.168.4.230 SMB Trans2 Request, QUERY_FILE_INFO, FID: 0x169e, Query File Stream Info No. Time Source Destination Protocol Info 177 315.611243 192.168.4.230 192.168.4.210 SMB Trans2 Response, QUERY_FILE_INFO No. Time Source Destination Protocol I...

Hello again, Jeremy and other Samba experts, I'm sorry to be such a pain in your neck(s), but I still need your help in looking for help trying to find out why SMB2/3.1.1 in Samba 4.6.5 performs so much worse than SMB/1.5 in Samba 3.6.15 in scenarios with a huge number of small files. As requested by Jeremy, I have done wireshark "pcapng" captures of the four scenarios as

...; claiming a write error regarding the thunderbird or firefox profile. At the same time all Desktop symbols are disappearing. The issue can be worked around by logging out and in again. >From wireshark network captures we can see the server sending an STATUS_INVALID_HANDLE is in response to a QUERY_FILE_INFO on the problem file. The setup: - OS Solaris11 / x86 - Samba 3.5.10 - some The server was recently updated from OpenSolaris running Samba 3.4.x any suggestions are really appreciated.... Thx Carsten Output from testparm is here: [global] dos charset = CP850 unix charset = CP850...

...168.40.46 192.168.40.2 SMB NT Create AndX Request, FID: 0x724f, Path: \spoolss 346 1.002522 192.168.40.2 192.168.40.46 SMB NT Create AndX Response, FID: 0x724f 347 1.005342 192.168.40.46 192.168.40.2 SMB Trans2 Request, QUERY_FILE_INFO, FID: 0x724f, Query File Standard Info 348 1.005404 192.168.40.2 192.168.40.46 SMB Trans2 Response, FID: 0x724f, QUERY_FILE_INFO 349 1.008716 192.168.40.46 192.168.40.2 DCERPC Bind: call_id: 1, 2 context items, 1st SPOOLSS V1.0 350 1.008797...