Hi All,

I've noticed an issue when I setup my Win8.1 computer with a Static IP it goes to the public network.

When I use DHCP it use the Domain network. 

I need my computer to have a static as I perform network management tasks from my computer via SNMP and the servers have my IP as an acceptable IP.

I have noticed this same issue on my Windows 2012 R2 server, Static IP uses unidentified network, and DHCP uses the domain network.  

Is this a known issue????

Thx,

1. Servers are computers that have static IP addresses in majority of cases.

2. Workstations have IP  assigned by DHCP usually, namely when there are a lot of them. DHCP brings more network parameters, not only IP addresses.

3. You have not given any detailed information on the type of network. I mean workgroup or Active Directory.

4. Most important are firewall settings of workstation and server. Network location seemed to be a "simple picture".

5. There are articles that explain network location

http://www.windowsecurity.com/articles-tutorials/firewalls_and_VPN/Windows-Firewall-Domain-Networks-Private-Networks-Public-Networks.html

http://windows.microsoft.com/en-us/windows7/choosing-a-network-location

http://windows.microsoft.com/en-us/windows-vista/choosing-a-network-location

http://windows.microsoft.com/en-us/windows7/switching-between-your-home-and-workplace-networks

http://www.minasi.com/newsletters/nws1304.htm

http://www.7tutorials.com/network-locations-explained

Regards

Milos

• Edited by Milos Puchta Tuesday, November 26, 2013 6:01 PM

1. Servers are computers that have static IP addresses in majority of cases.

2. Workstations have IP  assigned by DHCP usually, namely when there are a lot of them. DHCP brings more network parameters, not only IP addresses.

3. You have not given any detailed information on the type of network. I mean workgroup or Active Directory.

4. Most important are firewall settings of workstation and server. Network location seemed to be a "simple picture".

5. There are articles that explain network location

http://www.windowsecurity.com/articles-tutorials/firewalls_and_VPN/Windows-Firewall-Domain-Networks-Private-Networks-Public-Networks.html

http://windows.microsoft.com/en-us/windows7/choosing-a-network-location

http://windows.microsoft.com/en-us/windows-vista/choosing-a-network-location

http://windows.microsoft.com/en-us/windows7/switching-between-your-home-and-workplace-networks

http://www.minasi.com/newsletters/nws1304.htm

http://www.7tutorials.com/network-locations-explained

Regards

Milos

• Edited by Milos Puchta Tuesday, November 26, 2013 6:01 PM

1. Servers are computers that have static IP addresses in majority of cases.

2. Workstations have IP  assigned by DHCP usually, namely when there are a lot of them. DHCP brings more network parameters, not only IP addresses.

3. You have not given any detailed information on the type of network. I mean workgroup or Active Directory.

4. Most important are firewall settings of workstation and server. Network location seemed to be a "simple picture".

5. There are articles that explain network location

http://www.windowsecurity.com/articles-tutorials/firewalls_and_VPN/Windows-Firewall-Domain-Networks-Private-Networks-Public-Networks.html

http://windows.microsoft.com/en-us/windows7/choosing-a-network-location

http://windows.microsoft.com/en-us/windows-vista/choosing-a-network-location

http://windows.microsoft.com/en-us/windows7/switching-between-your-home-and-workplace-networks

http://www.minasi.com/newsletters/nws1304.htm

http://www.7tutorials.com/network-locations-explained

Regards

Milos

• Edited by Milos Puchta Tuesday, November 26, 2013 6:01 PM

1. Servers are computers that have static IP addresses in majority of cases.

2. Workstations have IP  assigned by DHCP usually, namely when there are a lot of them. DHCP brings more network parameters, not only IP addresses.

3. You have not given any detailed information on the type of network. I mean workgroup or Active Directory.

4. Most important are firewall settings of workstation and server. Network location seemed to be a "simple picture".

5. There are articles that explain network location

http://www.windowsecurity.com/articles-tutorials/firewalls_and_VPN/Windows-Firewall-Domain-Networks-Private-Networks-Public-Networks.html

http://windows.microsoft.com/en-us/windows7/choosing-a-network-location

http://windows.microsoft.com/en-us/windows-vista/choosing-a-network-location

http://windows.microsoft.com/en-us/windows7/switching-between-your-home-and-workplace-networks

http://www.minasi.com/newsletters/nws1304.htm

http://www.7tutorials.com/network-locations-explained

Regards

Milos

• Edited by Milos Puchta Tuesday, November 26, 2013 6:01 PM

Milos,

They are all on a domain.

Firewall is disabled for the domain but on for public.

This is different behavior from Windows 7.

Let me know what info you want

Hi,

I suggest you check the event viewer, do you find any error messages about this issue? Such as netlogon error?

Here is a similiar thread:

http://social.technet.microsoft.com/Forums/windows/en-US/c2fb2e59-43fb-4111-a4f6-2431e8e81dd4/active-network-changes-when-reconfiguring-from-dhcp-to-static-ip-address?forum=w7itpronetworking

In that case, the issue was solved by enabling the "PortFast" option on the network switches.

Please refer to this KB:

Event ID 5719 is logged when you start a computer

http://support.microsoft.com/kb/938449/en-us

Regards,

Yolanda

Hi Yolanda,

Thanks for the info but enabling Portfast on my switch is not an option. This is a very strange issue especially on my Windows 2012 R2 server!

I do have the event ID 5719 so I guess Ill look in to solutions for that.

Its just strange that if I change either my Win8 computer or W2K12 R2 server to DHCP it goes right to the Domain Network.

Thx

Hi,

Since this logon error was recorded in your PC, have you tried other solutions listed in KB 938449? I think it worth a try. And please paste the whole event log about this issue here for further analyzing.

Regards,

Yolanda

Hi All,

I've noticed an issue when I setup my Win8.1 computer with a Static IP it goes to the public network.

When I use DHCP it use the Domain network. 

I need my computer to have a static as I perform network management tasks from my computer via SNMP and the servers have my IP as an acceptable IP.

I have noticed this same issue on my Windows 2012 R2 server, Static IP uses unidentified network, and DHCP uses the domain network.  

Is this a known issue????

 

Thx,

The suggestions in KB 938449 are nothing more than Band-Aid fixes that should not be necessary and my problem is when I use a static as opposed to a dynamic IP address.

Using DHCP or Static should work the same just one is static and the other is receiving the settings elsewhere.

When I use DHCP with Windows 8.1 or Windows 2012 R2 the connection status is normal but when I use a Static IP it connects to an unidentified network.

I added the DNS suffix and disabled/re-enabled the NIC and it worked until I rebooted and it connected to the unidentified network again.

Thanks to all for the continued help and I hope Microsoft will provide a real fix soon.

It seems that this issue is related with the netlogon, maybe these links can provide some help:

Netlogon 5719 and the Disappearing Domain [Controller]

http://blogs.technet.com/b/instan/archive/2008/09/18/netlogon-5719-and-the-disappearing-domain.aspx

A Netlogon event ID 5719 event message is logged when you start a Windows based computer

http://support.microsoft.com/kb/247922/en-us

Enable debug logging for the logon service

http://support.microsoft.com/kb/109626