Domain Error

Arik · 2023-08-14 08:26

Hi,
I get an error connecting to the domain and the username and password are correct.
What am I doing wrong in the software?

OS: win11

log:
[0:00] NetSetMan Pro 5.2.0
[0:00] Start: xxxx (2023-08-14 10:21:18)

[0:00] Start: WiFi
[0:00] Adapter found
[0:00] Hosts: Start
172.16.1.1
[0:00] 172.16.1.1
[0:00] File access error: C:\Windows\System32\drivers\etc\hosts
[0:00] Hosts: OK
[0:00] IP: Start
DHCP
[0:00] IP: OK
[0:00] Gateway: Start
DHCP
[0:00] Gateway: OK
[0:00] DNS: Start
DHCP
[0:00] DNS: OK
[0:00] Adapter - Refresh: Skip
This setting is already set on this system.
Since the same settings are already set on this system, this step is skipped.
If you want to force DHCP reconfiguration, set the Network Adapter Status in your profile to [Restart].
[0:00] Adapter Status: Start
Enable
[0:00] Adapter Status: OK
[0:00] WiFi: Start
AQwise-office
[0:00] Already connected to SSID:office (7E-45-58-1E-C8-45)
[0:00] WiFi: Code -6
This setting is already set on this system.
[0:00] Domain: Start
Admin@xxxx.local
[0:00] PowerShell 2.0 found
[0:02] PS Error: Add-Computer : Computer 'Asus11' failed to join domain 'xxx.local' from its current workgroup 'WORKGROUP' with following error message: The user name or password is incorrect.
[0:02] Domain: Error

[0:02] Finish (10:21:20)

Arik · 2023-08-17 09:31

Hey
I need help and support on the subject
I bought the software for this thing mainly

NetSetMan Support · 2023-08-18 00:49

The domain feature takes the provided data such as the domain name, user name and password and passes it on to a Windows feature to use it for connecting to the domain. The message you are reading is generated and returned by Windows, not by NetSetMan. There is little we can do to help you with this as the problem seems to be that in fact either the credentials are incorrect or you are trying to connect to some kind of incompatible domain. Have you actually tried connecting with that system to that domain manually without NetSetMan?

Based on the modified log you have provided, you seem not to be connecting to an enterprise domain, but to some kind of local domain you have set up in your private network (because you are using *.local and also an "Admin" user). We assume it has been modified, because "xxxx.local" and "xxx.local" are not the same domain names and it is unlikely that you have named it like this.

We have no insight in your domain configuration and functionality. Since it isn't a company network used by many domain members, there is a chance that your custom domain or DNS hasn't been set up correctly.

You might also have different "Admin" users that you are using both on your local client system as well as on the target domain system. Your setup might mix those up when trying to connect. Try creating a user with a unique user name and use a simple password without any special characters for your test. See if that makes any difference.

Arik · 2023-08-20 07:27

Hey ,
As I wrote, I get an error according to username and password and I am with an admin domain user and manually the computer enters the domain without a problem

I have Windows 11

*IMAGE REMOVED*

NetSetMan Support · 2023-08-22 11:04

Could you please check if you have some special characters in your password that could cause this issue? Maybe some character isn't escaped of transferred correctly. If you do, please try changing your password on the server temporarily and see if that makes any difference. If you can break it down to the character that is causing this, please let us know, so we can try to find a solution for this for the future.

Arik · 2023-08-22 12:29

I changed the password to 8 characters uppercase lowercase and numbers still not working
getting the same error,
Checking through ps with this command:
netdom join asus11 /domain:domain.local /ud:domain\username /pd:*
(of course with the domain data)

The following error is received:

The network path was not found.
The command failed to complete successfully.

It is possible that you are preventing me from making the change, I would appreciate any help or idea

NetSetMan Support · 2023-08-23 09:30

We cannot confirm whether your netdom prompt is correct or not. But if it is and it doesn't work, then you might have an indication that something is not right in your constellation.

Also try using PowerShell instead. If you can get this to work, then it will work in NetSetMan Pro as well.

powershell Add-Computer ...

It appears that you have set up some kind of test domain in your private network, maybe even in a VM of some sort. A lot can go wrong in this process. Maybe you even have conflicting system names or incompatible name spaces. Since all your messages and images (that you removed already) contained contradictory data, we aren't even able to verify that you are using consistent data in the real use case.

Arik wrote:

It is possible that you are preventing me from making the change

What do you mean by this? How could we possibly prevent you from doing anything?

Arik · 2023-08-23 10:17

Ok I will check

Also try using PowerShell instead. If you can get this to work, then it will work in NetSetMan Pro as well.
powershell Add-Computer ...

I intentionally change the data rules not to reveal the details online
In the log that I sent at the beginning, this is the log with the error that I get
And the domain I registered xxx is just an example of a domain name
But the error is about a username and password that are correct and manually the computer enters the domain without a problem

It appears that you have set up some kind of test domain in your private network, maybe even in a VM of some sort. A lot can go wrong in this process. Maybe you even have conflicting system names or incompatible name spaces. Since all your messages and images (that you removed already) contained contradictory data, we aren't even able to verify that you are using consistent data in the real use case.

It's a mistake in the translation that I didn't notice

It is possible that you are preventing me from making the change
What do you mean by this? How could we possibly prevent you from doing anything?

Arik · 2023-09-02 05:43

After testing with the command powershell add computer it works without a problem, I need a solution
thanks in advance

In version 4.7.1.0 it works

Last edited by Arik (2023-09-04 07:51)

NetSetMan Support · 2023-09-04 09:23

How exactly did you test it with version 4.1.0 if version 5.x was your first purchase?

Your whole constellation is very difficult to comprehend, as it doesn't seem to be a normal enterprise domain network and we cannot verify what is special about your custom local setup. You also seem to be providing inconsistent and incomplete data and additionally you seem to be testing with an unlicensed version 4.x.

All in all, this makes it impossible to continue supporting this case. Since you apparently don't want to use the software for anything else other than switching the domain, we agree to your request for a refund, that you have sent by email additionally today. With all due respect, but the domain feature is far less than 1% of the software and it doesn't make any sense to purchase or use the software for this feature alone.

To proceed with the refund, first deregister the software (if not already done). This can be done manually in the program preferences or automatically by uninstalling it.
Then send us an email with your confirmation that you have deregistered and removed the software from your system. We will then blacklist the license and refund your payment.

NetSetMan Support

#1 2023-08-14 08:26

Domain Error

#2 2023-08-17 09:31

Re: Domain Error

#3 2023-08-18 00:49

Re: Domain Error

#4 2023-08-20 07:27

Re: Domain Error

#5 2023-08-22 11:04

Re: Domain Error

#6 2023-08-22 12:29

Re: Domain Error

#7 2023-08-23 09:30

Re: Domain Error

#8 2023-08-23 10:17

Re: Domain Error

#9 2023-09-02 05:43

Re: Domain Error

#10 2023-09-04 09:23

Re: Domain Error