Unable to connect to mapped drive

lumencreative · 2 Jul 2018 at 13:14

We've got a Dell Poweredge server running Hyper-V on Bare Metal. On this we have 2 VM's. One for Active Directory and file sharing and one for our accounts software.

Both servers are running and have been running fine for 6 months since I installed them, but since Friday I've not been able to access the mapped drive for the accounts vm.

I can still RDP to the server and everything is running fine, but when I try to access the mapped drive, I get the following error:

///////////////////////////////////////////////////////////////////////////////////////////////////////////////////
X:\ is not accessible

We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again.
///////////////////////////////////////////////////////////////////////////////////////////////////////////////////

I can access every mapped drive from the VM with our active directory on it, but not the accounts VM.

Nothing has been changed so I'm really stumped. Have tried removing and remapping the drive but nothing.

lumencreative · 2 Jul 2018 at 13:15

Forgot to add, I also cannot access the accounts VM by typing \\SERVERNAME\ in explorer. That brings up the following error

///////////////////////////////////////////////////////////////////////////////////////////////////////////////////
\\SERVERNAME is not accessible. You might not have permission to use this network resource.
Contact the administrator of this server to find out if you have access permission.

We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again.
///////////////////////////////////////////////////////////////////////////////////////////////////////////////////

PiKe · 2 Jul 2018 at 13:23

Check your DNS settings.

lumencreative · 2 Jul 2018 at 13:33

PiKe said:
Check your DNS settings.

DNS settings on both the Server and the Client are fine. DNS is pointing the the AD server.

Armageus · 2 Jul 2018 at 13:59

Can you ping it via IP address?
If so can you access it via IP Address e.g. \\192.168.1.x\ ?
If so then it's still likely a DNS issue.

lumencreative · 2 Jul 2018 at 14:49

Armageus said:
Can you ping it via IP address?
If so can you access it via IP Address e.g. \\192.168.1.x\ ?
If so then it's still likely a DNS issue.

I can ping the server via its IP address and I can also ping the server via its SEVERNAME.

I have just removed the accounts VM from the domain. Server rebooted, and is now a member of WORKGROUP. If I try to re-join the domain, it comes up with an error saying 'The supplied user buffer is not valid for the requested operation'.

However, I have noticed that I can map the drive if I do so using the local admin user credentials for the accounts VM but obviously this isn't ideal.

covenantuk · 4 Jul 2018 at 13:28

Is your Domain running Windows 2016 DCs?

If so: https://social.technet.microsoft.co...a-windows2016-server-solved?forum=winserverDS - should be resolved by patching them up to date

You could also try deleting/recreating the machine account before you join the computer back to the domain.

Next time before you remove from the domain, you can go to ADUC and right click/Reset Machine Account. This should reset a faulty authentication link betwen domain and server

paradigm · 4 Jul 2018 at 18:57

covenantuk said:
Next time before you remove from the domain, you can go to ADUC and right click/Reset Machine Account. This should reset a faulty authentication link betwen domain and server

Or, from the affected client machine/member server run an administrative PowerShell window and use:

Reset-ComputerMachinePassword -server domaincontroller.fullyqualified.tld -credential [email protected]