Windows Server 2019 (VMWare) Share not readable through domain name

Question

I am using the latest windows sever 2019 with VM Ware. It's an active AD that has DNS. (This is a test server). I can't read nor write to the share when using the domain name, but I can with the server name. How can I solve this?

The domain name is: gerda.local
The server name is: gerda-test

The output of nslookup gerda.local is:
DNS request timed out.
timeout was 2 seconds.
Server: UnKnown
Address: ::1

Name: gerda.local
Address: 192.168.0.1

So the following doesn't work: \gerda.local\Kaas\Test.txt
But this does work: \gerda-test\Kaas\Test.txt

Answer 1

*C:\Users\Hwillems>nslookup gerda.local
Server: GERDA-TEST.gerda.local
Address: 192.168.0.1

Name: gerda.local
Address: 192.168.0.1
The domain name is: gerda.local
The server name is: gerda-test
So, the following doesn't work: \gerda.local\Kaas\Test.txt
But this does work: \gerda-test\Kaas\Test.txt*

Hello, do you have DFS configured in your environment? - Accessing a share with only the domain name will trigger DFS based share access - This is definitely a DFS issue then.

Accessing the share directly works - No DNS Issue.

from this output I see only the DFS cache for Sysvol.

C:\Users\Administrator>dfsutil /pktinfo
1 entries...
Entry: \gerda.local\sysvol
ShortEntry: \gerda.local\sysvol
Expires in 504 seconds
UseCount: 0 Type:0x1 ( DFS )
0:[\GERDA-TEST.gerda.local\sysvol] AccessStatus: 0 ( ACTIVE ).

If you are using DFS , then you may have to navigate to DFSmgmt.msc on the server (Gerda-test) and make sure there are no issues with the namespaces and root configuration.

Answer 2

Hi,

Seems like DNS resolution issue, check event logs on the DC and provide logs from system, also provide export of "dcdiag /v" is also a nice way of getting more details.

Answer 3

@JimmySalian-2011

Log Name:      Microsoft-Windows-User Device Registration/Admin  
Source:        Microsoft-Windows-User Device Registration  
Date:          10/10/2022 2:46:25 PM  
Event ID:      304  
Task Category: None  
Level:         Error  
Keywords:        
User:          SYSTEM  
Computer:      GERDA-TEST.gerda.local  
Description:  
Automatic registration failed at join phase.   
Exit code: Unknown HResult Error code: 0x801c001d   
Server error:    
Tenant type: undefined   
Registration type: undefined   
Debug Output:   
joinMode: Join  
drsInstance: undefined  
registrationType: undefined  
tenantType: undefined  
tenantId: undefined  
configLocation: undefined  
errorPhase: discover  
adalCorrelationId: undefined  
adalLog:  
undefined  
adalResponseCode: 0x0  
  
Event Xml:  
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">  
  <System>  
    <Provider Name="Microsoft-Windows-User Device Registration" Guid="{23b8d46b-67dd-40a3-b636-d43e50552c6d}" />  
    <EventID>304</EventID>  
    <Version>0</Version>  
    <Level>2</Level>  
    <Task>0</Task>  
    <Opcode>0</Opcode>  
    <Keywords>0x8000000000000000</Keywords>  
    <TimeCreated SystemTime="2022-10-10T12:46:25.463872700Z" />  
    <EventRecordID>358</EventRecordID>  
    <Correlation />  
    <Execution ProcessID="5772" ThreadID="5776" />  
    <Channel>Microsoft-Windows-User Device Registration/Admin</Channel>  
    <Computer>GERDA-TEST.gerda.local</Computer>  
    <Security UserID="S-1-5-18" />  
  </System>  
  <EventData>  
    <Data Name="ExitCode">-2145648611</Data>  
    <Data Name="ServerErrorMessage">  
    </Data>  
    <Data Name="TenantType">undefined</Data>  
    <Data Name="JoinType">undefined</Data>  
    <Data Name="DebugOutput">joinMode: Join  
drsInstance: undefined  
registrationType: undefined  
tenantType: undefined  
tenantId: undefined  
configLocation: undefined  
errorPhase: discover  
adalCorrelationId: undefined  
adalLog:  
undefined  
adalResponseCode: 0x0  
</Data>  
  </EventData>  
</Event>  
  
Log Name:      Microsoft-Windows-User Device Registration/Admin  
Source:        Microsoft-Windows-User Device Registration  
Date:          10/10/2022 2:46:25 PM  
Event ID:      307  
Task Category: None  
Level:         Error  
Keywords:        
User:          SYSTEM  
Computer:      GERDA-TEST.gerda.local  
Description:  
Automatic registration failed. Failed to lookup the registration service information from Active Directory. Exit code: Unknown HResult Error code: 0x801c001d. See http://go.microsoft.com/fwlink/?LinkId=623042  
Event Xml:  
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">  
  <System>  
    <Provider Name="Microsoft-Windows-User Device Registration" Guid="{23b8d46b-67dd-40a3-b636-d43e50552c6d}" />  
    <EventID>307</EventID>  
    <Version>0</Version>  
    <Level>2</Level>  
    <Task>0</Task>  
    <Opcode>0</Opcode>  
    <Keywords>0x8000000000000000</Keywords>  
    <TimeCreated SystemTime="2022-10-10T12:46:25.463826200Z" />  
    <EventRecordID>357</EventRecordID>  
    <Correlation ActivityID="{e163fa9f-dca5-0001-8c0f-64e1a5dcd801}" />  
    <Execution ProcessID="5772" ThreadID="5776" />  
    <Channel>Microsoft-Windows-User Device Registration/Admin</Channel>  
    <Computer>GERDA-TEST.gerda.local</Computer>  
    <Security UserID="S-1-5-18" />  
  </System>  
  <EventData>  
    <Data Name="ExitCode">-2145648611</Data>  
  </EventData>  
</Event>  
  
Log Name:      Application  
Source:        Microsoft-Windows-Perflib  
Date:          10/10/2022 2:46:09 PM  
Event ID:      1023  
Task Category: None  
Level:         Error  
Keywords:        
User:          SYSTEM  
Computer:      GERDA-TEST.gerda.local  
Description:  
Windows cannot load the extensible counter DLL "C:\Windows\system32\ntdsperf.dll" (Win32 error code The specified module could not be found.).  
Event Xml:  
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">  
  <System>  
    <Provider Name="Microsoft-Windows-Perflib" Guid="{13b197bd-7cee-4b4e-8dd0-59314ce374ce}" />  
    <EventID>1023</EventID>  
    <Version>1</Version>  
    <Level>2</Level>  
    <Task>0</Task>  
    <Opcode>0</Opcode>  
    <Keywords>0x8000000000000000</Keywords>  
    <TimeCreated SystemTime="2022-10-10T12:46:09.555246100Z" />  
    <EventRecordID>1379</EventRecordID>  
    <Correlation />  
    <Execution ProcessID="3644" ThreadID="4176" />  
    <Channel>Application</Channel>  
    <Computer>GERDA-TEST.gerda.local</Computer>  
    <Security UserID="S-1-5-18" />  
  </System>  
  <EventData>  
    <Data Name="Library">C:\Windows\system32\ntdsperf.dll</Data>  
    <Data Name="Win32Error">126</Data>  
  </EventData>  
</Event>  

And other commands

C:\Users\Administrator>dfsutil /pktinfo  
1 entries...  
Entry: \gerda.local\sysvol  
ShortEntry: \gerda.local\sysvol  
Expires in 831 seconds  
UseCount: 0 Type:0x1 ( DFS )  
   0:[\GERDA-TEST.gerda.local\sysvol] AccessStatus: 0 ( ACTIVE )  
  
  
DfsUtil command completed successfully.  
  
C:\Users\Administrator>dfsutil /spcinfo  
[*][GERDA-TEST.gerda.local]  
[*][GERDA]  
[*][gerda.local]  
[-][GERDA]  
[+][gerda.local]  
        [+GERDA-TEST.gerda.local] AccessStatus: 0  
  
DfsUtil command completed successfully.  
  
C:\Users\Administrator>  

https://hastebin.com/livumoyupa.bat

Answer 4

Hi,

Thank you for posting your query.

Kindly follow the steps provided below.

Select the virtual machine and select VM > Settings.

On the Options tab, select Shared Folders.

Select a folder sharing option.

(Optional) To map a drive to the Shared Folders directory, select Map as a network drive in Windows guests.

This directory contains all of the shared folders that you enable. Workstation Pro selects the drive letter.

Click Add to add a shared folder.

On Windows hosts, the Add Shared Folder wizard starts. On Linux hosts, the Shared Folder Properties dialog box opens.

Browse to, or type, the path on the host system to the directory to share.

If you specify a directory on a network share, such as D:\share, Workstation Pro always attempts to use that path. If the directory is later connected to the host on a different drive letter, Workstation Pro cannot locate the shared folder.

Specify the name of the shared folder as it should appear inside the virtual machine and click Next.

Characters that the guest operating system considers illegal in a share name appear differently when viewed inside the guest. For example, if you use an asterisk in a share name, you see %002A instead of * in the share name on the guest. Illegal characters are converted to their ASCII hexadecimal value.

Select shared folder attributes.

Click Finish to add the shared folder.

The shared folder appears in the Folders list. The check box next to folder name indicates that the folder is being shared. You can deselect this check box to disable sharing for the folder.

Click OK to save your changes.

Go to this link for your reference https://docs.vmware.com/en/VMware-Workstation-Pro/16.0/com.vmware.ws.using.doc/GUID-D6D9A5FD-7F5F-4C95-AFAB-EDE9335F5562.html

Note: This is a non-Microsoft website kindly take precautions before downloading anything.

Do not hesitate to message us if you need further assistance.

-------------------------------------------------------------------------------------------------------------------------------------------

If the answer is helpful kindly click Accept as Answer and upvote it.

Answer 5

Also this is the result from ns lookup

C:\Users\Hwillems>nslookup gerda.local  
Server:  GERDA-TEST.gerda.local  
Address:  192.168.0.1  
  
Name:    gerda.local  
Address:  192.168.0.1