search for: transaction2

...EC43F6FD95FC SMB - NT Create AndX 172.16.5.230 172.16.33.235 00:04:58.406173 298.406173 13:48:44.346851 (193) EC43F6FD95FC Local #1 SMB - NT Create AndX 172.16.33.235 172.16.5.230 00:04:58.417457 298.417457 13:48:44.347210 (248) Local #1 EC43F6FD95FC SMB - Transaction2 172.16.5.230 172.16.33.235 00:04:58.417816 298.417816 13:48:44.359812 (186) EC43F6FD95FC Local #1 SMB - Transaction2 172.16.33.235 172.16.5.230 00:04:58.430418 298.430418 13:48:44.360141 (99) Local #1 EC43F6FD95FC SMB - Close 172.16.5.230 172.16.33.235...

running Version 3.6.23-14.el6_6 I'm having slow save times with folders names ~something.. ie. /www/~bin/content.txt. doing this via a windows share.. when I save file it has a moment (few seconds) of hesitation.. then saves. When I do /www/bin/content.txt. the file saves instantly. Is there anywhere I can change a setting to fix this? or is this a bug. I've looked in the logs

...e 0.025427 192.168.2.37 -> 192.168.51.1 SMB Session Setup AndX Request, User: EXPRESS-11AIQI4\Administrator; Tree Connect AndX, Path: \\192.168.51.1\DATA 0.039981 192.168.51.1 -> 192.168.2.37 SMB Session Setup AndX Response; Tree Connect AndX 0.040262 192.168.2.37 -> 192.168.51.1 SMB Transaction2 Request QUERY_PATH_INFORMATION, Path: 0.051879 192.168.51.1 -> 192.168.2.37 SMB Transaction2 Response QUERY_PATH_INFORMATION 0.052291 192.168.2.37 -> 192.168.51.1 SMB Transaction2 Request FIND_FIRST2, Pattern: \* 1.519710 192.168.2.37 -> 192.168.51.1 SMB Transaction2 Request FIND_FIR...

...l Request server client SMB Negotiate Protocol Response client server SMB Session Setup AndX Request, User: domain\uid server client SMB Session Setup AndX Response client server SMB Tree Connect AndX Request, Path: \\server\share server client SMB Tree Connect AndX Response client server SMB Transaction2 Request QUERY_FS_INFORMATION server client SMB Transaction2 Response QUERY_FS_INFORMATION client server SMB Transaction2 Request QUERY_FS_INFORMATION server client SMB Transaction2 Response QUERY_FS_INFORMATION client server SMB Transaction2 Request QUERY_PATH_INFORMATION, Path: server client...

...n and do the same thing again, but otherwise the Mac has to reboot. Anyone else seen this ?? 170.957153 1.2.3.4.127 -> 1.2.3.4.135 SMB Open Request, Path: \._Hard Drive_asr.dmg 170.957424 1.2.3.4.135 -> 1.2.3.4.127 SMB Open Response, FID: 0x29ee 170.957816 1.2.3.4.127 -> 1.2.3.4.135 SMB Transaction2 Request FIND_FIRST2, Pattern: \._Hard Drive_asr.dmg 170.958063 1.2.3.4.135 -> 1.2.3.4.127 SMB Transaction2 Response FIND_FIRST2, Files: ._Hard Drive_asr.dmg 170.958337 1.2.3.4.127 -> 1.2.3.4.135 SMB Read AndX Request, FID: 0x29ee, 512 bytes at offset 0 170.958417 1.2.3.4.135 -> 1.2.3.4.127...

...ol 1 0.20911 0.20911 0.20911 Session Setup AndX 4 0.13362 0.15055 0.14006 Logoff AndX 1 0.13913 0.13913 0.13913 Tree Connect AndX 6 0.12751 0.15108 0.13548 NT Create AndX 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.139...

...amba 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 drive (root folder) but when I click on a folder inside the root directory, the client first sends Open AndX command and the server responds for that, after that the client sends Query Information2 and the server responds for that and afte...

...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 Negotiation, Tree Connect AndX and Open AndX, the Windows XP machine sends transaction2 command. It first sends Trans2_Request, FIND_FIRST2 command with the level of interest as SMB_INFO_QUERY_EA_SIZE. I send the response for this request. I have totally 3 files (for implementation purpose I have only 3 files) in the shared drive. I could form the packet and send response for this...

Good afternoon all, I have a few questions, and just joined the list and plan on staying. I had 2 Samba servers at work, both running apache, etc, that we develop on from work and at home over a vpn. My vpn upload speed is 25K, and at one time windows 2000 could save a document in less than 4 seconds from across the vpn using textpad. We recently downgraded our crappy 7.1 redhat versions to 6.2

..., inode = 359229, file_id = 6). 8< Snipped a bunch of cleanup messages >8 [2002/06/12 17:16:10, 3] smbd/server.c:exit_server(492) Server exit (oplock break failure) The tcpdump over the same period indicates that the file is available. When the 'NT Create AndX Request' and 'Transaction2' request is sent by the Windows box, Samba responds with a 'Locking AndX Request' which the Windows box acknowledges. There is a 30 second delay which is followed by traffic showing the traffic related to the expiration of the timeout. Full logs of these sessions are here: ftp://ft...

...set .... ..0. = Syn: Not set .... ...0 = Fin: Not set Window size: 65396 Checksum: 0x36d6 (correct) NetBIOS Session Service Message Type: Session message Length: 72 SMB (Server Message Block Protocol) SMB Header Server Component: SMB SMB Command: Transaction2 (0x32) NT Status: STATUS_SUCCESS (0x00000000) Flags: 0x18 0... .... = Request/Response: Message is a request to the server .0.. .... = Notify: Notify client only on open ..0. .... = Oplocks: OpLock not requested/granted ...1 .... = Can...

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

I've upgraded one of my client boxes to Windows 64 bit edition but now it cannot login to the Samba PDC, instead it gives a RPC error after entering the password. The Win32 boxes can still login fine. I can get accounts without admin rights to login but those with the rights are given a message stating "The system cannot log you on due to the following error: A remote procedure call