Bug 1495490 – smbclient rename throws NT_STATUS_OBJECT_NAME_INVALID

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 1495490 - smbclient rename throws NT_STATUS_OBJECT_NAME_INVALID

Summary:	smbclient rename throws NT_STATUS_OBJECT_NAME_INVALID

Status:	CLOSED ERRATA

Aliases:	None

Product:	Red Hat Enterprise Linux 7
Classification:	Red Hat
Component:	samba (Show other bugs)
Sub Component:
Version:	7.3
Hardware:	x86_64 Linux

Priority	unspecified Severity high
Target Milestone:	rc
Target Release:	---
Assigned To:	Andreas Schneider
QA Contact:	Andrej Dzilský
Docs Contact:

URL:
Whiteboard:
Keywords:	Regression

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2017-09-26 03:45 EDT by amitkuma
Modified:	2018-04-10 13:31 EDT (History)
CC List:	9 users (show)

See Also:
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 13:30:15 EDT
Type:	Bug
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

External Trackers
Tracker	ID	Priority	Status	Summary	Last Updated
Samba Project	13093	None	None	None	2017-10-23 05:05 EDT
Red Hat Product Errata	RHBA-2018:0937	None	None	None	2018-04-10 13:31 EDT

Groups: None (edit)

Comment 3 Andreas Schneider 2017-10-20 08:58:26 EDT

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 09:28:05 EST

I've created test for this scenario. 

Everything should work after new version.

Comment 11 errata-xmlrpc 2018-04-10 13:30:15 EDT

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

Note You need to log in before you can comment on or make changes to this bug.