Link to home
Create AccountLog in
Avatar of Gene Weeg
Gene WeegFlag for United States of America

asked on

Server unable to join domain

I have a 2012 Server R2 that stop allowing us to RDP into it a week ago.  We finally got to the Datacenter and see that it is no longer joined to the domain.  Our engineer intalled the latest updates from Microsoft.  Still now joy after that.  This server is a controller for our ShoreTel phone server,  Any help would be appreciated because VM to email is not working currently.


Error message is "The following error occured atempting to join the domain 'ABD.com'"


The specified network name is no longer available.

Avatar of Edward Pamias
Edward Pamias
Flag of United States of America image

I was looking through some things online and found this.


Specified network name is no longer available. Step 1: Type windows feature in the Search box, then click Turn Windows features on or off. Step 2: Scroll down to SMB 1.0/CIFS File Sharing Support and then check the box next to it. Click OK to save changes.  And just to be on the safe side I posted something from Microsoft as well. Personally I would read the Microsoft suggestions first. If none of this helps you I am sure another expert would be able to assist.


https://learn.microsoft.com/en-us/answers/questions/1162623/specified-network-name-is-no-longer-available

Avatar of Gene Weeg

ASKER

That feature is enabled. Thanks for the thought. 

I am just throwing ideas your way until another expert arrives. Possible firewall issue? Ports being blocked?

server are side by side on the same subnet. firewall is not in the mix.

I was asking about the firewall because I found this online.


The Windows Firewall with Advanced Security is a host-based firewall that runs on Windows Server 2012 and is turned on by default

Can you get to \\dc\netlogon from the client in Windows explorer?


Try running Get-SmbServerConfiguration from the client from the Powershell console.


SMB 1.0 may be installed, but not enabled:


EnableSMB1Protocol                     : False

EnableSMB2Protocol                     : True


SMB2 should also be enabled if it is not:


Set-SmbServerConfiguration -EnableSMB2Protocol $true


You should also check the health of the DCs that service that subnet: https://lazyadmin.nl/it/dcdiag/


Perhaps someone created a "hardening" security GPO that disabled SMB1.  You should verify these settings stick after a restart.

ASKER CERTIFIED SOLUTION
Avatar of Gene Weeg
Gene Weeg
Flag of United States of America image

Link to home
membership
Create a free account to see this answer
Signing up is free and takes 30 seconds. No credit card required.
See answer