Bug 1495490

Summary:	smbclient rename throws NT_STATUS_OBJECT_NAME_INVALID
Product:	Red Hat Enterprise Linux 7	Reporter:	amitkuma
Component:	samba	Assignee:	Andreas Schneider <asn>
Status:	CLOSED ERRATA	QA Contact:	Andrej Dzilský <adzilsky>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	7.3	CC:	adzilsky, apeddire, asn, billmask, d.busby, gdeschner, jarrpa, rhack, tcameron
Target Milestone:	rc	Keywords:	Regression
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:	samba-4.7.1-2.el7	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-04-10 17:30:15 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Comment 3 Andreas Schneider 2017-10-20 12:58:26 UTC

Wow, I've created packet traces for SMB1 and SMB3. The setinfo command sends the same values but it fails with SMB3.

I will contact Microsoft, I don't see that Samba is doing something wrong.

Comment 7 Andrej Dzilský 2017-12-01 14:28:05 UTC

I've created test for this scenario. 

Everything should work after new version.

Comment 11 errata-xmlrpc 2018-04-10 17:30:15 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2018:0937