I just installed Win8.1 on an HP laptop.  Networking on the laptop works fine as long as I use DHCP, which is how it is configured for general network access.   The problem occurs when I define a Static IP address; the interface gets created as an "unidentified network" and I have no network access.  I have a very simple test network configuration in that all I am trying to do is configure a single firewall appliance using this laptop.  I do not have a DHCP server on this simple test segment (Laptop direct connected to the FW interface).  Is there any way to utilize a Static IP address in Win8.1?  I have read through numerous threads describing Domain login issues, DNS suffix configuration, deleting DEFAULT route, etc..  None of these seem applicable based on my simple, direct connected scenario.  I also opened the local group policy editor and set the unidentified networks to "private" with no luck. 

It appears that I have physical connectivity in that "link" is enabled/disabled when I connect and disconnect the laptop from the FW management interface.  I have had no problem with this configuration using previous Windows editions.  Has anyone figured out how to use Win8.1 with Static IPs or is the indication that Win8.1 should not be used as a lab device?   

Changing the security policy has always worked for me, even on isolated networks like private virtual networks before any other devices are attached.

What IP config are you trying to set up on this machine?

Regarding the security policy, I took the shotgun approach and turned off the firewall with no luck. 

I'm not sure what you are looking for regarding the IP config.  I set the interface configuration for a static IP on the 10.x.x.x/24 network, which is the same network the device I am trying to connect to is on.  There should be no routing involved; just an ARP to reach the address I want to connect to but the local interface remains an "unidentified network".

I don't think that will help. He does not want this interface to connect to the router or anything else on that network. He wants to connect to a different device in a different network and a different IP subnet.

I just installed Win8.1 on an HP laptop.  Networking on the laptop works fine as long as I use DHCP, which is how it is configured for general network access.   The problem occurs when I define a Static IP address; the interface gets created as an "unidentified network" and I have no network access.  I have a very simple test network configuration in that all I am trying to do is configure a single firewall appliance using this laptop.  I do not have a DHCP server on this simple test segment (Laptop direct connected to the FW interface).  Is there any way to utilize a Static IP address in Win8.1?  I have read through numerous threads describing Domain login issues, DNS suffix configuration, deleting DEFAULT route, etc..  None of these seem applicable based on my simple, direct connected scenario.  I also opened the local group policy editor and set the unidentified networks to "private" with no luck. 

It appears that I have physical connectivity in that "link" is enabled/disabled when I connect and disconnect the laptop from the FW management interface.  I have had no problem with this configuration using previous Windows editions.  Has anyone figured out how to use Win8.1 with Static IPs or is the indication that Win8.1 should not be used as a lab device?   

Static addresses are not as important as they used to be, DHCP tend to hold the same IP address for each client. This assumes fault tolerate power as box uses RAM and not flash memory.

You are missing the point. An address from DHCP would be useless. This is a second interface in the machine connected to a different network with a different IP subnet.

Static addresses are not as important as they used to be, DHCP tend to hold the same IP address for each client. This assumes fault tolerate power as box uses RAM and not flash memory

If you are using segmented networks, better is to use Active Directory instea

The bottom line is that Win8.1 seems to treats the assignment of a static IP address differently than previous versions.  I'm trying to determine if this is expected behavior and is there any way around it?  If I can't use a static address on the interface, why am I allowed to assign it?         

Windows 8.1 does not treat this any differently, in fact I've recently done this myself with a Windows 8.1 laptop and a WiFi device that I needed a direct connection to in order to configure the Wifi device. The device's default IP was 192.168.0.1, I assigned 192.168.0.2 with a default gateway of 192.168.0.1 to my laptop and had no problems with the connection. The fact that the connection shows as Unidentified should not be a problem.

I don't know exactly what the problem you're encountering is caused by, but it isn't a limitation or difference in Windows 8.1.

• Marked as answer by Karen HuMicrosoft contingent staff, Moderator Monday, February 17, 2014 1:38 PM

There is some difference. What exactly I can't figure out yet.

Windows 8/8.1/2012/2012 R2 all use SMB 3. This is a layer 3 problem.

Previous versions have a completely different TCP stack.

I have the same exact issue with server 2012 R2 on 6 servers with 10Gb connection right now.
Banged my head against the wall for a week until I just added DHCP and set IP reservations.
That solved my issue, and that should lead us in the right direction.

I wish a MS person would chime in to this point.

I have the same exact issue with server 2012 R2 on 6 servers with 10Gb connection right now.
Banged my head against the wall for a week until I just added DHCP and set IP reservations.
That solved my issue, and that should lead us in the right direction.

How (where) add DHCP and set IP reservations?

I'd like to try this on Server 2008 R2 ...

on server 2008 r2, right click on the network adapter icon

get the status page up

click on properties

click on ipv4 and select properties

select alternate configuation

there you can set the desire IP address

make sure your DHCP has some unused areas for static clients

eg 192.168.0.1 is the DHCP/Gateway, so allocate 100-250 for DHCP leaving 2-99 for static users

on server 2008 r2, right click on the network adapter icon

get the status page up

click on properties

click on ipv4 and select properties

select alternate configuation

there you can set the desire IP address

make sure your DHCP has some unused areas for static clients

eg 192.168.0.1 is the DHCP/Gateway, so allocate 100-250 for DHCP leaving 2-99 for static users

My response was in no way abusive and should not have been marked as such. Vegan Fanatic's response did not even come close to addressing the questions at hand which were:

1. How to add the DHCP role.
2. How to create a DHCP reservation.

In fact, the setting described in his response is specifically for situations where DHCP already exists in a primary location but not in a secondary location (for example DHCP on a corporate network and static IP addressing on a home network with a laptop that is used in both locations).

Vegan Fanatic clearly doesn't understand the technology here. If he did so, he'd realize that his response is completely and utterly incorrect and should not have been posted in the first place let alone being marked as a proposed answer.

I will be reporting this latest incident to our Canadian MVP lead as Vegan Fanatic has a long history of getting involved in threads where he is out of his depth technically and rather than helping customers with their problems winds up doing nothing more than causing confusion. When called upon his errors, his pattern of behaviour is to mark such posts as being abusive rather than doing the right thing and admitting that he is wrong.

there was no mention of using a DHCP role or a server by the ori

there was no mention of using a DHCP role or a server by the original

• Edited by Bill-777 Saturday, August 23, 2014 8:42 PM funky fonts - wtf webadmin?
• Proposed as answer by bbabraham 13 hours 41 minutes ago

• Edited by Bill-777 Saturday, August 23, 2014 8:42 PM funky fonts - wtf webadmin?

This isn't a solution for people using static IPs...You've simply by passed the problem.

Actually, if Windows marks your network as "Unidentified" it's often a "deal killer". We have dozens of Windows 7 boxes all exhibiting the "Unidentified network" issue on boot up. At this point, there is no network connection, AT ALL. Resetting the adapter by disabling and enabling it, WILL get Windows to go ahead an identify the network properly. However, up until then, you may as well have the network cable disconnected.

Setting the adapter to DHCP works fine, however. Of course this is also unacceptable, since our goal is static ip assignments.

I believe the problem is actually on the networking side: On our network back at the office everything "just works". However, in the bigger picture, slamming the network off, simply because it fails some arbitrary test is a really dickheaded way to design a networking subsystem! The ideal solution would be to allow one to simply bypass the entire subsystem, but unfortunately, that is not one of the provided options.

Thank you! I'm on Windows 7 and had the same problem as the OP. Simple network but setting a static IP creates "unidentified network" rendering the network useless.

As you advised, simply resetting the adapter by disabling and re-enabling it forced Windows to identify the network and now the connection/network is perfect!

I think this easiest of tricks will probably be the fix for the OP too!

Much appreciated.:)