Windows client connecting to UCS / Samba server - The join operation was not successful

939 views Asked by At

Using Univention Corporate Server UCS, I have the following Linux distribution:

root@ucs:~# cat /etc/*-release
DISTRIB_ID=Univention
DISTRIB_RELEASE="4.2-2 errata159"
DISTRIB_CODENAME=Lesum

DISTRIB_DESCRIPTION="Univention Corporate Server 4.2-2 errata159 (Lesum)"
PRETTY_NAME="Debian GNU/Linux 8 (jessie)"
NAME="Debian GNU/Linux"
VERSION_ID="8"
VERSION="8 (jessie)"
ID=debian
HOME_URL="http://www.debian.org/"
SUPPORT_URL="http://www.debian.org/support"
BUG_REPORT_URL="https://bugs.debian.org/"

and the following Samba version:

root@ucs:~# samba -V
Version 4.6.1-Debian

On this Linux machine I have configured the package:

Active Directory-compatible Domain Controller

I configured one user there: myuser which is under the group: Domain Users.

My problem is, when trying to connect to the local domain defined there: mydomain.intranet

I get the error:

The join operation was not successful. This could be because an existing computer account having name "MYUSER-PC" was previously created using a different set of credentials. Use a different computer name, or contact your administrator to remove any stale conflicting account. The error was:

Access is denied

as you can see on the following image:

enter image description here

Any idea on how to troubleshoot this?

Thanks.

1

There are 1 answers

0
AudioBubble On BEST ANSWER

Greetings from Univention,

this might not be the best Site to ask for solutions for these kind of problems, as Jeff already mention.

We would like to invite you to Univention Help where a lot of greatly experienced Community members and our Staff would love to help you.

Beside that, did you try to join your domain with your myuser user? This won't work as your user doesn't have the proper rights to add Machines to your Domain. Have you tried it with the User Administrator as shown in this image?

You also want to make sure, that there isn't already a Machine with the name DELL-INSIPRON existent in your domain, but I assume that this won't be the case.