Network showing up as Network 2 when it should be the domain network

CatholicTV
CatholicTV used Ask the Experts™
on
I have a server running Server 2008 R2 that is domain joined that the network connection says Network 2 (private) instead of the domain network. The machine fucntions fine on the network and it can see the domain servers and other servers on the network that it works with. It used to show the domain network but for a few months now it doesn’t.

Windows Firewall = off
File and Printer Sharing = on

Even a reboot does not fix the situation.

I also have one other server that it’s nic shows up and unidentified network and it too can do business on the network without issue but the nic just doesn’t display the domain network.
Comment
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
Distinguished Expert 2017

Commented:
Windows 2008 has (requires) both IPv4 and IPv6 protocols to be active, see whether network 2 refers to the IPv6 section/portion.
What you are seeing is the name assigned by Windoze when it created the network and you can rename it in Network and Sharing Center -> Manage network connections.

I'm not that keen on the "unidentified network" though.

Author

Commented:
Thanks for the input. Neither of these solutions are correcting the issue.
Exploring SQL Server 2016: Fundamentals

Learn the fundamentals of Microsoft SQL Server, a relational database management system that stores and retrieves data when requested by other software applications.

Distinguished Expert 2017

Commented:
Unfortunately, it is hard to guess what your issue is.

Do you have a single NIC? Is the computer booted and logged into the domain?
If this is a mobile system, does the LAN employ an 802.1x such that this system fails to authenticate and is thus placed on a different Kansas/segment?

Author

Commented:
Single NIC on a domain server. I have many of the same configuration that operate normally. It has been a big mystery to me why I have two servers with these issues.

Even with the NIC's not displaying the domain as the network the servers are able to communicate with file shares and other network appliances.
I'll try this again.
Windoze names your network connections in the order they were discovered.  Something in it detected "Network 1"; but, then a driver update or a change in how the system detected the network made it go away and be redetected as "Network 2"

I regularly see PC's that are up to "Network 5" or 6 and it is just a name you don't have to worry about.

If you go to network connections, right click on its entry, and choose properties, you'll find that all the settings are fine.
Distinguished Expert 2017
Commented:
The dilemma the asker and I see deals with the connection name should not change when it is on an AD domain. (Default to work type policy)

Do more with

Expert Office
Submit tech questions to Ask the Experts™ at any time to receive solutions, advice, and new ideas from leading industry professionals.

Start 7-Day Free Trial