Moving Win Server 2012 R2 - Unidentified Network Post-Reboot with TCP/IPv4 Settings

Hello,
I have a weird (for me) problem. After moving the server to another physical location, it stopped identifying the network correctly.
He sees her as an "unidentified network" and despite being "guided" after restart, there is again an "unidentified network"

The new server with the new system was pre-configured in the office.
The server has 4 network cards (actually two double) - all were turned on but only one was plugged in - previously unplugged from the computer. There is one network with two gates in the company.
The network card with the cable plugged in had " Out of hand "TCP / IPv4 protocol properties set rigidly (IP 192.168.1.40, mask 255.255.255.0, gateway 192.168.1.1 and DNS 192.168.1.1 second dns empty)
As a side note, the TCP / IPv6 protocol was enabled (auto settings)

Windows gave this network the name "Network 2" / private and everything worked beautifully. After restart, he always got up and quickly recognized the network as "Network 2" / private.
However, server location is somewhere else.

After moving the server to the closet (the second part of the company) and plugging it directly into the switch (the same network card) began to "bounce back".
First, it takes a moment "Network identification" (which I did not notice in the previous connection in the office) and then Identifies the network as "Unidentified network".
I note that I have changed nothing in the settings and the server is in the same network, just say "two swiche closer".

And now there is a second curiosity:
In this state, I enter the card settings, disable the tcp / ipv6 protocol. I do apply and ... in a moment instead of "Unidentified network" / public appears the desired "Network 2" / private.
Now restart the system and ... again "Unidentified network". I enter the card settings - this time I turn on the TCP / IPv6 protocol - save and ... "Network 2" again After restart "unidentified network"
I tested all the cards - they behave the same. I turned off three other cards so that there was only one - continue the same symptom.

How to force Windows to select / see this "Network 2" and not always identify it. Or what to check / improve on the network so that the system can detect it correctly.

Delete all networks and reinstall the drivers. If you can't Set up connection via network connection No. 2.

Added after 41 [seconds]:

marek003 wrote:

How to force Windows to select / see this "Network 2"

Delete connection 1

Added after 49 [seconds]:

marek003 wrote:

I enter the card settings

Not in the card settings but in the network settings.

barteksmrek wrote:

Delete all networks and reinstall the drivers. If you can't Set up connection via network connection No. 2.

I don't know if we understand each other well.
Let me remind you that we are talking about Win server 2012 R2 (similar to W8) and about LAN (not WiFi)
Where should I delete "all networks"? What drivers are you talking about? To the net?
And if to the network card you think that moving the "clean" server without any installations in the meantime could have disturbed the driver?

This is not winXP, I don't have "network connections" here. Windows identifies the network itself as "Network 2" I do not know what you mean by "set up a connection using network connection 2" This is what I would like to do, that is, force Windows to always assign (without checking) the connection "network 2" and nothing more did not check - Just how ???

barteksmrek wrote:

marek003 wrote:
How to force Windows to select / see this "Network 2"

Delete connection 1
...
Not in the card settings but in the network settings.

Here I will repeat that it is not XP and W7. There are "network and sharing settings" but there are no such things as selecting / deleting a given network.

marek003 wrote:

. Here are "network and sharing settings"

but not from card updates.

@barteksmrek What do NIC drivers have to do with it?

Windows network locations can be removed in the following way from the control panel:







On the other hand, I'm pretty sure it won't solve network problems. Make sure the cables you connect to are OK.

barteksmrek wrote:

but not from card updates.

I wrote that not from the card.

Added after 1 [minutes]:

sylweksylwina wrote:

@barteksmrek What do the network card drivers have for this?

Most likely a problem with the switch configuration. Attempt to test this port on the switch to which you connect the server card, e.g. a laptop, and check how it behaves. Is pinging the gateway and dns server. What switches do you use on the network?

best regards

marek003 wrote:

As a side note, the TCP / IPv6 protocol was enabled (auto settings)

What for? Is it on this IPv6 network?
The network in both locations is the same? Is there any router that divides this network into two parts? "Two gates" are skro ...

There is indeed a problem for this server getting an IP number from a DHCP server.
Although it was not elsewhere in the network.
But other devices connected to this switch which is now connected to the server have no problem with that.

For now, I managed that in the settings for unidentified wines network sets a private, not public network and I can now connect and have IP number permanently entered (I turned off IP6

Nevertheless, the problem remained and now the question is how to diagnose it?

I have two gates only because the company is in the middle of nowhere and it often happens that one of the internet providers "gets off" (netia / local air). Then (if needed) each user has a "bat" file on the computer replacing the gates so that they can connect to the internet if necessary.

This solution has worked for years.

It is true that recently netia has changed my router (with VOIP - there is a different IP here) but it works with the fact that I have trouble getting access to the DNS server IP - I have to manually enter it in workstations because without it there is no connection through this gate - maybe there is something here?

And you can't pass a second link through the same router to make the gateway one?

Don't you have a second NAT?

tape wrote:

And you can't pass a second link through the same router to make the gateway one?

I admit that I do not know the router model that has two WAN "sockets"
or I don't have enough knowledge about configuration - I am an economist and an IT specialist from a jump.

You know - it suited me a lot that there are two gates on two routers.
With this method I do a simple "segregation".
Some users (through a router that transmits a certain pool of IP numbers [DHCP server]) are connected to one gateway with a slower internet, while others (from another IP pool) are "reserved" by the other router, they connect to it and have very fast internet. (This router has a Dhcp server set to pool [end] 150-151 and it has an IP address reservation, of course, outside the first router pool.

But I am open to any efficient solution. In addition, maybe I will broaden my knowledge. I note that I have two Internet providers, and I want to divide the network into those who always connect to only one fast network (unless the program will change the gateway in the event of a failure so far) and an automatic IP pool that connects to a slower network - they in case failures do not need to be connected to another network.

xury wrote:

Don't you have a second NAT?

As a company, I have two external IP numbers and it suits me very well. I don't know what exactly do you mean?

Describe how connected these routers are to each other and what address they have. I suspect there is a problem somewhere.
It would also be good to include a network topology.

There are plenty of devices that support two or more connections. In more advanced models, you can freely configure who has what to access, which links can use. You set routes depending on your needs, etc. Your solution unnecessarily complicates the configuration of the devices.

best regards

I admit that so far I have not "played" with drawing the network. I will do it in my free time.

I will add: I do not know devices with two WLANs, but I understand that there are devices for link management - except that in my case a device with two WLANs / connections could not be "passed"

One "internet access" [netii router] is in the office (download / shipping speed: 10/1).
Second internet access [router-TP-Link local supplier] is in the production building - located to the office about 250 meters in a straight line (speed of this internet is: download / shipping: 10/10)
I will draw the network in the near future.

At present, only the word: that between the switch in the office to which the router with "internet" is connected and the switch on the production to which the second router with internet is connected, there is optical fiber and one swich to which (by the way) is connected one working station.

Did you solve the problem? Have you ever tried to enter public DNS in server settings? After setting up your network, I can see that there is no domain controller in it. I think that most of the problems would be solved, as I said before, adding an additional, operator-independent router that supports at least two WAN links or completely replacing the suppliers' devices. If you have optical fiber between locations, you can easily pull both internet connections to one place. This solution guarantees that users will not even feel the failure of a single link, well except for a decrease in send / receive speed or at least without any control over all the traffic in the company. The cost of such a solution is easily accessible.

best regards