[cifs-protocol] [REG:113102210883291] - [MS-SMB2] NT_STATUS_REQUEST_NOT_ACCEPTED?

Edgar Olougouna edgaro at microsoft.com
Wed Nov 6 09:45:33 MST 2013

It appears that the previous ETW were not decodable. The files might have been corrupted when emailing or before. Can you please recollect the ETW and network trace and upload to the workspace I have created for this case. If it's possible, please run the t.cmd in a new folder.
From an elevated command prompt:
t.cmd srvon
Start network capture
Reproduce the issue
t.cmd srvoff
Stop network capture

Upload the t.cab and network trace to the workspace.
I will be sending you the workspace information in a separate email.


-----Original Message-----
From: Edgar Olougouna 
Sent: Monday, November 04, 2013 4:50 PM
To: Volker.Lendecke at sernet.de
Cc: cifs-protocol at samba.org; MSSolve Case Email
Subject: RE: [REG:113102210883291] - [cifs-protocol] [MS-SMB2] NT_STATUS_REQUEST_NOT_ACCEPTED?


I will investigate and follow-up on this case.


-----Original Message-----
From: Volker Lendecke [mailto:Volker.Lendecke at SerNet.DE]
Sent: Tuesday, October 29, 2013 3:41 PM
To: Sebastian Canevari
Cc: pfif at tridgell.net; cifs-protocol at samba.org
Subject: Re: [cifs-protocol] [MS-SMB2] NT_STATUS_REQUEST_NOT_ACCEPTED? 

On Tue, Oct 29, 2013 at 08:05:25PM +0000, Sebastian Canevari wrote: 
> Looking into the script, it seems like the reason for that message is
that an "off" switch is being used before an "on" switch.

Hmmmm. You don't want to know the reason why it failed ... 

Well, I'll tell you anyway: My freakin mail client stripped the ^M from the line endings while saving t.txt. Sorry for the noise. :-)

Attached find the cab and cap files. 



SerNet GmbH, Bahnhofsallee 1b, 37081 Göttingen
phone: +49-551-370000-0, fax: +49-551-370000-9 AG Göttingen, HRB 2816,
GF: Dr. Johannes Loxen http://www.sernet.de, mailto:kontakt at sernet.de

-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: t.cmd_win8.txt
URL: <http://lists.samba.org/pipermail/cifs-protocol/attachments/20131106/446459d0/attachment-0001.txt>

More information about the cifs-protocol mailing list