Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Monday, October 28, 2019 9:12 AM
Hello,
on some Domain Member PCs (Win 10 1903) we get lots of 30800 Event Errors for SMB Client --> COnnectivity, which say:
"The server name cannot be resolved."
But the hostname attempted to resolve is the NetBIOS (or pre Windows 2000) Domain name of the domain, like if it tries to resolve CONTOSO. This obviously cannot be resolved, shoud it?
Will this cause any issues? We have some random issues with DFS shares accesibility, I wonder if it might be related?
kind regards,
Dieter
All replies (5)
Tuesday, October 29, 2019 8:44 AM
Hi,
>>Will this cause any issues? We have some random issues with DFS shares accesibility, I wonder if it might be related?
Yes. It might be related to DNS resolve problem.
Please use cmd command: nslookup, to check your name resolution process and screenshot it to help confirm the resaon.
The command: > NSlookup
>set d2
> [Name you want to resolve]
And you can try to use //IP address/Folder to access the SMB to check if the problem is solved.
Hope this can help you, if you have anything unclear, please let me know.
Best Regards,
Ellen
Please remember to mark the replies as answers if they help and unmark them if they provide no help.
If you have feedback for TechNet Subscriber Support, contact [email protected].
Tuesday, October 29, 2019 8:57 AM
I don't think that I have a general DNS resoluiton Problem.
C:\Users\tontsch>nslookup
Default Server: dc1-2019.mobileX.intra
Address: 192.168.0.4
> set d2
> aadc.mobilex.intra
Server: dc1-2019.mobileX.intra
Address: 192.168.0.4
**
SendRequest(), len 50
*** HEADER:***
*** opcode = QUERY, id = 2, rcode = NOERROR***
*** header flags: query, want recursion***
*** questions = 1, answers = 0, authority records = 0, additional = 0***
*** QUESTIONS:***
*** aadc.mobilex.intra.mobileX.intra, type = A, class = IN***
**
**
Got answer (118 bytes):
*** HEADER:***
*** opcode = QUERY, id = 2, rcode = NXDOMAIN***
*** header flags: response, auth. answer, want recursion, recursion avail.***
*** questions = 1, answers = 0, authority records = 1, additional = 0***
*** QUESTIONS:***
*** aadc.mobilex.intra.mobileX.intra, type = A, class = IN***
*** AUTHORITY RECORDS:***
*** -> mobilex.intra***
*** type = SOA, class = IN, dlen = 43***
*** ttl = 3600 (1 hour)***
*** primary name server = dc1-2019.mobilex.intra***
*** responsible mail addr = hostmaster***
*** serial = 1330619***
*** refresh = 900 (15 mins)***
*** retry = 600 (10 mins)***
*** expire = 86400 (1 day)***
*** default TTL = 3600 (1 hour)***
**
**
SendRequest(), len 50
*** HEADER:***
*** opcode = QUERY, id = 3, rcode = NOERROR***
*** header flags: query, want recursion***
*** questions = 1, answers = 0, authority records = 0, additional = 0***
*** QUESTIONS:***
*** aadc.mobilex.intra.mobileX.intra, type = AAAA, class = IN***
**
**
Got answer (118 bytes):
*** HEADER:***
*** opcode = QUERY, id = 3, rcode = NXDOMAIN***
*** header flags: response, auth. answer, want recursion, recursion avail.***
*** questions = 1, answers = 0, authority records = 1, additional = 0***
*** QUESTIONS:***
*** aadc.mobilex.intra.mobileX.intra, type = AAAA, class = IN***
*** AUTHORITY RECORDS:***
*** -> mobilex.intra***
*** type = SOA, class = IN, dlen = 43***
*** ttl = 3600 (1 hour)***
*** primary name server = dc1-2019.mobilex.intra***
*** responsible mail addr = hostmaster***
*** serial = 1330619***
*** refresh = 900 (15 mins)***
*** retry = 600 (10 mins)***
*** expire = 86400 (1 day)***
*** default TTL = 3600 (1 hour)***
**
**
SendRequest(), len 36
*** HEADER:***
*** opcode = QUERY, id = 4, rcode = NOERROR***
*** header flags: query, want recursion***
*** questions = 1, answers = 0, authority records = 0, additional = 0***
*** QUESTIONS:***
*** aadc.mobilex.intra, type = A, class = IN***
**
**
Got answer (52 bytes):
*** HEADER:***
*** opcode = QUERY, id = 4, rcode = NOERROR***
*** header flags: response, auth. answer, want recursion, recursion avail.***
*** questions = 1, answers = 1, authority records = 0, additional = 0***
*** QUESTIONS:***
*** aadc.mobilex.intra, type = A, class = IN***
*** ANSWERS:***
*** -> aadc.mobilex.intra***
*** type = A, class = IN, dlen = 4***
*** internet address = 192.168.0.64***
*** ttl = 1200 (20 mins)***
**
**
SendRequest(), len 36
*** HEADER:***
*** opcode = QUERY, id = 5, rcode = NOERROR***
*** header flags: query, want recursion***
*** questions = 1, answers = 0, authority records = 0, additional = 0***
*** QUESTIONS:***
*** aadc.mobilex.intra, type = AAAA, class = IN***
**
**
Got answer (91 bytes):
*** HEADER:***
*** opcode = QUERY, id = 5, rcode = NOERROR***
*** header flags: response, auth. answer, want recursion, recursion avail.***
*** questions = 1, answers = 0, authority records = 1, additional = 0***
*** QUESTIONS:***
*** aadc.mobilex.intra, type = AAAA, class = IN***
*** AUTHORITY RECORDS:***
*** -> mobilex.intra***
*** type = SOA, class = IN, dlen = 43***
*** ttl = 3600 (1 hour)***
*** primary name server = dc1-2019.mobilex.intra***
*** responsible mail addr = hostmaster***
*** serial = 1330619***
*** refresh = 900 (15 mins)***
*** retry = 600 (10 mins)***
*** expire = 86400 (1 day)***
*** default TTL = 3600 (1 hour)***
**
Name: aadc.mobilex.intra
Address: 192.168.0.64
My problem is that this error is because it attempts to resolve the hostname MOBILEXNEW which is not a host name, but the NetBIOS Name of my Active Directory Domain. In my opinion it is normal that this cannot be reolved, it does not exist in DNS. It is like I would ask you to resolve CONTOSO, nothing more and nothing less.
kind regards,
Dieter
Tuesday, October 29, 2019 9:47 AM
Hi,
>>My problem is that this error is because it attempts to resolve the hostname MOBILEXNEW which is not a host name, but the NetBIOS Name of my Active Directory Domain.
\Domainname\folder is a DFS access shared folder method.
\hostname\folder is a SMB access shared folder method.
Which one didi you ues?
Best regards,
Ellen
Please remember to mark the replies as answers if they help and unmark them if they provide no help.
If you have feedback for TechNet Subscriber Support, contact [email protected].
Tuesday, October 29, 2019 10:39 AM
\hostname\folder always works. But we use \domainname\folder, the DFS approach. The late ron e is the one which causes random problems.
But I am also in touch with the MS support, and one last suggestion from their side was to grant EVERYONE:Read Access to DFSRoots on each of my DFS Namespace Servers (we have 4). I figured out that everyone hat no access on any of the servers neither to DFSRoot nor to the folder. Additionally on one of the servers permission inheritance from DFSRoots downwards was not enabled. I have now enabled inherintance on each server for DFSRoots and below, and I have added EVERYONE with READ Access to DFSRoots.
My ACL now is (on each server the same):
Path : Microsoft.PowerShell.Core\FileSystem::C:\DFSRoots
Owner : BUILTIN\Administratoren
Group : MOBILEXNEW\Domänen-Benutzer
Access : Everyone Allow Read, Synchronize
*** NT AUTHORITY\SYSTEM Allow FullControl***
*** BUILTIN\Administratoren Allow FullControl***
*** BUILTIN\Benutzer Allow ReadAndExecute, Synchronize***
*** BUILTIN\Benutzer Allow AppendData***
*** BUILTIN\Benutzer Allow CreateFiles***
*** CREATOR OWNER Allow 268435456***
I do not know if this is correct though.
Thursday, October 31, 2019 7:16 AM
Hi,
Due to limited resources in the forum, it is recommended to continue to contact with MS support about your qusetion.
Best regards,
Ellen
Please remember to mark the replies as answers if they help and unmark them if they provide no help.
If you have feedback for TechNet Subscriber Support, contact [email protected].