Want to win a PS4? Go Premium and enter to win our High-Tech Treats giveaway. Enter to Win

x
?
Solved

Network changed from Domain to Private

Posted on 2017-06-19
11
Medium Priority
?
65 Views
Last Modified: 2017-06-24
It is a Server 2012 R2 Server. Somehow over the weekend the connection type changed from Domain to Private which in-turn changed the firewall settings. How do I get the network type back to Domain?
0
Comment
Question by:LockDown32
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
11 Comments
 
LVL 98

Expert Comment

by:John Hurst
ID: 42183821
There is not a setting to do this so far as I recall.

You can try TCP/IP Reset but I do not think this will change the NIC setting.

Open cmd.exe with Run as Administrator.

NETSH LAN /? to review options.

NETSH LAN Delete Profile name="name of profile"  

Then make a new profile.

You may need to restart the server after.
0
 
LVL 35

Expert Comment

by:sarabande
ID: 42183846
it looks as if the Domain Controller (DM) could not be found at start. you may ping to the DM server's ip  from command line. if the ping worked you may try to see your server from DM. if connectivity principally is ok, you could go to the network and sharing center in the system Settings, then double-click on the (private) icon of your network. with the next dialog you should be able to return to the domain.

Sara
0
 
LVL 15

Author Comment

by:LockDown32
ID: 42183876
This is on the solo Domain Controller. It is a static IP and that static IP information did not change, I am not sure where this "System Settings" is in Network and Sharing. I can't do a IP reset because I am remote.

   Attached is a screen shot of Network and Sharing from the server...
Capture.PNG
0
Concerto's Cloud Advisory Services

Want to avoid the missteps to gaining all the benefits of the cloud? Learn more about the different assessment options from our Cloud Advisory team.

 
LVL 98

Expert Comment

by:John Hurst
ID: 42183880
If you cannot change the setting remotely (not changeable in newer systems and I do not know why) then you or someone else needs to go on site.
0
 
LVL 15

Author Comment

by:LockDown32
ID: 42183885
I have no problem going on-site but I would at least like some idea of what I am supposed to do before going :)
0
 
LVL 98

Expert Comment

by:John Hurst
ID: 42183887
If the setting cannot be changed by changing the NIC in Network and Sharing (try that), then you need to reset the LAN profile as suggested above.
0
 
LVL 15

Author Comment

by:LockDown32
ID: 42183892
What I an struggling with is where and how to "change the NIC in Network and Sharing". The IP Address is fine and has not changed. What else is there to change?
0
 
LVL 98

Expert Comment

by:John Hurst
ID: 42183893
If you cannot right click and change to Domain, then the setting is not available to change. It has been removed in newer systems. I forget when exactly it changed. I think after Windows 7.
0
 
LVL 36

Expert Comment

by:Shaun Vermaak
ID: 42183898
You can do this via Powershell local or remote with this CMDLet
Set-NetConnectionProfile -InterfaceIndex <index number> -NetworkCategory DomainAuthenticated

Open in new window

0
 
LVL 15

Accepted Solution

by:
LockDown32 earned 0 total points
ID: 42183909
From a Thread on Server Fault:

Wheter the network of a domain controller is classified als domain network doesn't depend on the gateway configuration.

The behaviour of a false network classification can be caused the NLA (network location awareness) service starts before the domain is available. In this case the public or private network is choosen and not corrected afterwards.

How to check if this fault situation is given
When the domain controller after rebooting is in the public network, restart the NLA service or disconnect / reconnect the network. The domain controller should be in the domain network afterwards.

How to solve it
It may help to set the NLA Service to delayed start. Better, check why the domain needs long to be present. It seems that the domain needs longer to start when there are multiple network cards.


Stopping and starting the NLA service reset it to Domain Controller mode
0
 
LVL 15

Author Closing Comment

by:LockDown32
ID: 42191046
This is the only solution that worked....
0

Featured Post

 [eBook] Windows Nano Server

Download this FREE eBook and learn all you need to get started with Windows Nano Server, including deployment options, remote management
and troubleshooting tips and tricks

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

This program is used to assist in finding and resolving common problems with wireless connections.
This month, Experts Exchange’s free Course of the Month is focused on CompTIA IT Fundamentals.
In this tutorial you'll learn about bandwidth monitoring with flows and packet sniffing with our network monitoring solution PRTG Network Monitor (https://www.paessler.com/prtg). If you're interested in additional methods for monitoring bandwidt…
There's a multitude of different network monitoring solutions out there, and you're probably wondering what makes NetCrunch so special. It's completely agentless, but does let you create an agent, if you desire. It offers powerful scalability …

618 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question