Can't connect new PC to domain

[psb]

Hi there,

I can ping the NAS from the PC using its IP address. That works fine. However, I just tried ping domainname.local and it didn't work. What does this tell me?

I didn't have any issues joining other PCs to the domain. Does Win10 work differently?

Could you let me know in layman's terms how I resolve this? Thanks!

[storageman]

Hi Do you have always this problem.
Could you ping your domain ? ex : ping DC.local
You said you have change the DNS Name Could you verify the entry of ALL Domain Service in DNS (GC,DC,site, etc) verify all entry have have goo domain name
Your PC is synchro time ? Same time with your DC controller
COuld you ping fqdn dns of your DC and fqdn of your domaine name ?

If you can t ping your DomainName work arround your DNS Client with Suffixe or make a static entry four your DC on hosts file of windows and time very important for join Domain
Good luck

He already checked the date/time NTP difference.
Why would Qnap not suggested hosts file change?

Kinda hope it's not just as simple as that!

psb, put a entry in hosts file c:\Windows\System32\Drivers\etc\hosts.
xxx.xxx.xxx.xxx yourqnap.domain

Then try ping domain/authentication again.

[psb]

Thanks for that! I'll try. Could you explain exactly how? This the content of the hosts file at the moment:

# Copyright (c) 1993-2009 Microsoft Corp.
#
# This is a sample HOSTS file used by Microsoft TCP/IP for Windows.
#
# This file contains the mappings of IP addresses to host names. Each
# entry should be kept on an individual line. The IP address should
# be placed in the first column followed by the corresponding host name.
# The IP address and the host name should be separated by at least one
# space.
#
# Additionally, comments (such as these) may be inserted on individual
# lines or following the machine name denoted by a '#' symbol.
#
# For example:
#
# 102.54.94.97 rhino.acme.com # source server
# 38.25.63.10 x.acme.com # x client host

# localhost name resolution is handled within DNS itself.
# 127.0.0.1 localhost
# ::1 localhost

[storageman]

Sorry, but are you in the right job?
I already told you what to try. Good luck.

[psb]

Sorry, but are you in the right job?
I already told you what to try. Good luck.

There's no need to be patronising. I'm just making sure I do it exactly right to avoid any potential hiccups, as I've not edited a hosts file before.

[lmecharle]

ahahah storageman I think the same.
you are noob psb no pb everybody begin job one day ??

# Copyright (c) 1993-2009 Microsoft Corp.
#
# This is a sample HOSTS file used by Microsoft TCP/IP for Windows.
#
# This file contains the mappings of IP addresses to host names. Each
# entry should be kept on an individual line. The IP address should
# be placed in the first column followed by the corresponding host name.
# The IP address and the host name should be separated by at least one
# space.
#
# Additionally, comments (such as these) may be inserted on individual
# lines or following the machine name denoted by a '#' symbol.
#
# For example:
#
# 102.54.94.97 rhino.acme.com # source server
# 38.25.63.10 x.acme.com # x client host

# localhost name resolution is handled within DNS itself.
# 127.0.0.1 localhost
# ::1 localhost
IP.OF.YOUR.DC name.domain.local

example
172.17.30.10 qnap.com (for example)


Could you post result about this command please

ipconfig /all

[psb]

Noob eh? I'm the owner of this equipment and the user. I'm not an IT professional, so I'm just here looking for support on an issue that goes beyond my current knowledge. I guess you guys have never posted on a forum for advice about something you don't know inside out - you just know everything about everything, right?

So I can now ping the DC using the domain name. Previously I could only ping the IP. However, I still can't join the domain.

[storageman]

I'm guessing this is some screwy DNS issue. Editing the hosts file is really a fudge solution. It doesn't affect how the Qnap reads DNS, just the Windows 10 machine.

Go back to Qnap and pester them for an answer. They wrote the software!

[psb]

It's been escalated to the next level of support. I'll post back.

[storageman]

As lmecharle suggested, have a good look at "ipconfig /all" (you run from command prompt)

If a machine is joined to a domain, this shows vital information on domain, IP addresses and DNS.

[lmecharle]

Hi
I read again your first post you said you change the DNS NAME of your Domain.
I have 2 question
How many interface are configured on your NAS ?
Have verified ALL IP address and DOmain of all entries on you TAB DNS on Domain Controller Configuration of your Web Interface Qnap.

Yesterday i had some problem to join Domain because theyre bad address ton DNS of Domain for GC DC entries of DNS.
Good luck

[psb]

What a complete pain the backside this has been. I've been back and forth with qnap support. It usually takes them 2 days to reply each time, sometimes longer, so it's frustrating.

I'm doing everything exactly as they say. I can ping the nas ip and name, I'm pointing to the DNS server, i get the option to log in, but it never works. The username and password is correct - it's been checked and changed. It's an administrator. No matter what we try, it doesnt work.

Qnap haven't a clue. They cannot resolve the issue and said try another windows 10 computer... which I don't have. Every other PC here runs windows 7.

[storageman]

What a complete pain the backside this has been. I've been back and forth with qnap support. It usually takes them 2 days to reply each time, sometimes longer, so it's frustrating.

I'm doing everything exactly as they say. I can ping the nas ip and name, I'm pointing to the DNS server, i get the option to log in, but it never works. The username and password is correct - it's been checked and changed. It's an administrator. No matter what we try, it doesnt work.

Qnap haven't a clue. They cannot resolve the issue and said try another windows 10 computer... which I don't have. Every other PC here runs windows 7.

Because yet again they are obsessed with adding more and more features to QTS that they haven't the resources or the technical knowledge to support.
Qnap, stop adding features for a year and fix what's there now!

[psb]

We're going to stop using it and find another network solution for the business, as this isn't good enough for us. Anyone have any recommendations for other NAS soltuions with AD Domain Control?

[storageman]

Why don't you run Windows Server domain controller from Virtualization Station?