Windows server 2008 неопознанная сеть

• Remove From My Forums

All replies

• Hi,
  Thanks for posting here.

  The Network Lists service (netprofm) works with the Network Location Awareness service (nlasvc) to identify networks and find the associated saved settings for the network, if any. The NLA service will use a Default Gateway or SSID to identify a network, so if the NIC has neither a Default Gateway or associated SSID, then NLA will determine that the network is Unidentified.

  Here is a whitepaper on NLA that partially describes how it works:

  http://msdn.microsoft.com/en-us/library/aa480195.aspx#lhnla_topic4b

  If you would like to set the profile to «Private» or «Public», you can perform the following steps:

  1. Open Administrative Tools -> Local Security Policy.

  2. Highlight the «Network List Manager Policies» item, then double click the «Unidentified Networks» on the right panel.

  3. Set the «Location Type» to «Private» or «Public».

  ---

  This posting is provided «AS IS» with no warranties, and confers no rights.

• Thanks for the answer.

  However, I would not want to set the Unidentified Networks to Private because I have more than 1 network adapters installed. I would like some of them to be Public instead. I tried setting Default Gateway on the network adapter to itself but Windows 2008 Server would just remove it.

  So, is there any service that I could install on the server itself (besides making it a domain controller) to solve this problem?

  Thanks you very much.

•   How would making it a domain controller solve this problem? The only difference would be that the private NIC network would be set to domain rather than private.

    What are these network adapters connected to? If they are connected to some network, what is the default gateway on other machines connected to that network?

  ---

  Bill

• Hi,

  Actually I do not know what service should be installed on the server to solve it. I installed Remote and Routing to make itself a gateway but it doesn’t solve the problem. Here’s how the network is being set up.

  Network A

  • Connected to internet via ISA server.
  • It has a domain server.
  • This network is identifed using the domain name.
  • This network is being set to Public to limit access to this server

  Network B

  • Connected to an isolated network with a few PCs.
  • Does not have any domain server or gateway.
  • I need to make this network a Private network.

  My problem is network B as it is identified as «Unidentified Network». I tried setting the network adapter TCP/IP Default Gateway to itself but Windows 2008 Server would just clear the field after I click OK. What should I install on the server itself solve this?

  Thanks.

• Hi,

  Thank you for the reply.
  I

  f the default gateway is not set the network will be displayed as «Unidentified network» because there is not enough information for Windows to uniquely identify this network.

  http://blogs.technet.com/networking/archive/2009/02/20/why-is-my-network-detected-as-unknown-by-windows-vista-or-windows-server-2008.aspx

  An «unidentified network» network will apply the Public network profile and the Public firewall profile. The user can manually change the network profile to Work or Home to have a less restrictive firewall profile applied. Also you can change the «unidentified network» to public or private firewall profile according to my first reply. In Windows 2008 and Vista, there is only one firewall profile applied per machine. In Windows 7 and Windows Server 2008 R2, you can apply multi network firewall profile to each NIC.  

  ---

  This posting is provided «AS IS» with no warranties, and confers no rights.

  • Marked as answer by

    Monday, August 24, 2009 9:48 AM

  • Unmarked as answer by
    Programatix
    Monday, August 24, 2009 10:46 AM

• Hi,

  Thanks for the reply.

  I understand why the network is displayed as «Unidentified network» but how to workaround it?

  I’ve done the following

  1) Set the Default Gateway ip to itself. Windows Server 2008 just remove it when I click OK.
  2) Set up remoting on the server to act as a gateway. I repeat step 1 and the same thing happen.

  I do not want to set «Unidentified network» to default to Private network as this would decrease network security as I have another network adapter which is currently also is marked as «Unidentified network», which I want to maintain it as a Public network.

  So, my question now is how do I set up the server to make the network identified?

  • Edited by
    Programatix
    Monday, August 24, 2009 10:50 AM

• Hi Programatix,

  What’s your Windows Server 2008 version? Is it R2?

  If it’s not R2. Windows Server 2008 only has one network profile per machine for both of your NICs.
  It seems that the NIC B is connected to a network which does not have a gateway device. You can try the following steps to add the DG.

  a)     Go to Control Panel >> Network and Internet >> Network and Sharing Center

  b)    Click ‘View Status’ next to the connection name.

  c)     Clicks the ‘Properties’ button at the bottom.

  d)     Highlight ‘Internet Protocol Version 4 (TCP/IPv4)’ and clicks ‘Properties’

  e)     In the properties dialog click ‘Advanced’

  f)     Under ‘Default gateways’ there will probably be a entry for ‘0.0.0.0’. Remove this entry. Add the correct Default Gateway here.

  g)    ‘OK’ out of all the property dialogs until you are at the ‘Network and Sharing Center’ again. The adapter will attempt to reconnect again.

  If the NLA still detect the “unidentified network”, it would not decrease your network security as an «unidentified network» network will apply the Public network profile and the Public firewall profile. However you can change the network profile to public via yourself.

  • Marked as answer by
    Wilson Jia
    Wednesday, August 26, 2009 10:52 AM
  • Unmarked as answer by
    Programatix
    Wednesday, August 26, 2009 12:51 PM

• Hi,

  As you have stated, NIC B is connected to a network which does not have a gateway device, so how would I get a correct Default Gateway IP? I’ve tried using its own IP for Default Gateway but Windows Server 2008 just remove it when I click OK. I actually wanted to make this NIC B as private. I have another NIC C which also does not have any gateway device and wanted it to remain as Public (this of course is not a problem).

  Again, the question is, how would I make NIC B to be identified as something, thus allowing me to permanently mark it as private? I’ve tried setting the server up with Remoting, but I still can’t use its own IP as Default Gateway.

  Thanks.

• Hi,

  As you ask how would I make NIC B to be identified as something. please check the answer in my previous reply.

  1. Open Administrative Tools -> Local Security Policy.

  2. Highlight the «Network List Manager Policies» item, then double click the «Unidentified Networks» on the right panel.

  3. Set the «Location Type» to «Private» or «Public».

  If your Windows Server is not Windows 2008 R2 or Window7. There is only ONE Network firewall profile applied to all of your NICs which means NIC A, B, C is either public or private or unidentified. Since your know the private network profile rule is less secure than public and unidentified network. When Windows could not determine your network is private (In your case there is a internet connection NIC A), It will keep high security network profile for a choice.

  For your reference, please refer to:
  http://blogs.technet.com/networking/archive/2009/02/20/why-is-my-network-detected-as-unknown-by-windows-vista-or-windows-server-2008.aspx

  If there is anything unclear, please let me know.
  Thanks.

  ---

  This posting is provided «AS IS» with no warranties, and confers no rights.

• Hi,

  Thanks for the reply.

  Yes, I am aware of the process of setting «Unidentified Networks» to «Private» and understand that Windows Server 2008 has only ONE network profile for all the NICs. But I would not want to set all «Unidentified Networks» to «Private», as I have a «Unidentified Networks» (NIC C) which I want to keep as «Public».

  Back to my original question, is there any service which is provided by Windows Server 2008 which I can install/enable to make itself as a gateway and allowing me to set NIC B’s Default Gateway to itself to have Windows 2008 recognize NIC B network, instead of detecting it as «Unidentified Network»?

•   It is very difficult when you keep changing the question. Originally you had one NIC. Then two. Now you have three!

    If you want to run a stange config on your machine, the default settings are not going to work. You will need to manually configure your own firewall configuration. And no, you cannot configure a NIC to use its own IP as a default gateway.

  ---

  Bill

• Hi,

  I wasn’t changing my question. In my original question, I mentioned that I have a server which is connected to an internal LAN. I did not say that it has only one NIC. This is to simplified the scenario as my original question is «I’m having problem where the network is detected as «unidentify network». What services should I install on the server to solve this? I do not want to install AD as the server is a Terminal Service server.»

  When it was suggested that I configure the «Unidentified Network» to be treated as Private instead of Public, I mentioned that I do not want to do that. I want to find a way to have it identified (by installing whatever required). This of course is bring the whole thng back to the original question.

  You then replied by rebuking me about my statement regarding would making the server a domain controller would solve the problem. I do not know whether it can resolve the problem or not as I haven’t tried it yet. When I attempted to do that, Windows warned me that it is not advised to do so because it is a Terminal Server.

  It was then I mentioned that I have 2 networks connected to this particular server just to show that I still do not want to make «Unidentified Network» as Private as the is another NIC which is connected to another network. At that moment I still hold true to my original question, what should I do to make it identified?

  Although I appreated Wilson Jia’s kindness in trying to solve my problem (instead of you barking at me), he keeps on asking me to configure «Unidentified Network» to Private.

  I introduced NIC C just to prove a point where configuring «Unidentified Network» to Private is not very safe and I do not want to do that. NIC C can be anything from a physical NIC to virtual NIC. In my point of view, this is not a strange network configuration. For the sake of avoiding you rebuking me further, here’s what my current network configuration is like,

  NIC A (Public) — Identified with the domain name.
  — Connected to a network with a domain. It has internet connectivity. This machine is not part of the domain.

  NIC B (Want to make this private by making this network identified)
  — Connected to an isolated network with limited access by selected PCs. The PCs in this network can access the Terminal server on this machine and file sharing is enabled.

  NIC C (Public) — Unidentified Network
  — Connected to virtual network (Hyper-V) which virtual machines as test machines.

  So, I still hold true to my original question, what to do (in term of installing services provided by Windows Server) to make network in NIC B identified?

•   Now we have Hyper-V as well!

      The NIC linked to a virtual network should not show up at all in the host OS. The only NIC which should appear in the host/parent partiton is a NIC to allow you to update the OS or connect to the OS in the parent partition for remote administration. The server should not be conncted directly to a public network.

     Servers work best if they are connected to a single network with a single NIC and a single default gateway. If you feel that one NIC cannot handle the traffic, use two NICs and team them so that they use just one IP.

     Having servers connected to multiple networks causes all sorts of problems. The basic problem is that you have more than one IP address associated with the machine’s name. When one machine needs to connect to another, it must resolve its name to an IP address. If it gets the «wrong» IP it may nt be able to communicate, because the IPit gets is in a different network.

    I would recommend that you make sure that the NIC linked to a virtual network does not have an IP in the parent partiton. See this discussion on what happens when you create a public virtual network.

  http://blogs.msdn.com/virtual_pc_guy/archive/2008/01/08/understanding-networking-with-hyper-v.aspx

    You should not be running Terminal Services on a machine which is hosting Hyper-V. If you really want to run TS on this machine, run it in a vm, not in the parent partition. The parent partition should run only one role, and that is Hyper-V.

  ---

  Bill

• Hi,

  Thanks for the advice regarding Hyper-V. Anyway I was just trying around with Hyper-V. It is also in my thought that TS should be hosted in Hyper-V but I think it’s too late for me to reconfigure the server and network as it was set up by previous administrator.

  Anyway, actually this particular server is used for development. It’s the company policy not to connect the server to any other network except the development network (via NIC B). From time to time, NIC A would be connected to domain network to get updates. Since NIC B is connected to an isolated network, it is «unidentified» but I need it to be set as private allow access to the TS. Any other network should be set to public.

  Any advice on how to secure this server while allowing PCs from the development network access to TS? I would be very grateful of any advice received. Btw, would connecting NIC A to domain network from time to time is safer compared to connecting NIC A to domain network 24×7? Or it doesn’t make any difference?

  • Edited by
    Programatix
    Thursday, August 27, 2009 7:59 AM

• I am having this exact same issue. There seems to be no answer from anyone as to how to resolve it. If you set a default gateway manually, it seems to change when you log out and back in, which does not help at all.

X:\Users\XXX>ipconfig /all

Настройка протокола IP для Windows

Имя компьютера . . . . . . . . . : XXXXXXXXX
Основной DNS-суффикс . . . . . . :
Тип узла. . . . . . . . . . . . . : Гибридный
IP-маршрутизация включена . . . . : Нет
WINS-прокси включен . . . . . . . : Нет

Ethernet adapter Подключение по локальной сети:

DNS-суффикс подключения . . . . . :
Описание. . . . . . . . . . . . . : Intel(R) I210 Gigabit Network Connection
Физический адрес. . . . . . . . . : 0C-C4-7A-04-17-3A
DHCP включен. . . . . . . . . . . : Нет
Автонастройка включена. . . . . . : Да
IPv4-адрес. . . . . . . . . . . . : 192.168.5.50(Основной)
Маска подсети . . . . . . . . . . : 255.255.255.0
Основной шлюз. . . . . . . . . : 0.0.0.0
192.168.5.240
DNS-серверы. . . . . . . . . . . : 192.168.5.240
NetBios через TCP/IP. . . . . . . . : Включен

Туннельный адаптер isatap.{C273C868-F7E7-4947-B90C-B9B746E6578E}:

Состояние среды. . . . . . . . : Среда передачи недоступна.
DNS-суффикс подключения . . . . . :
Описание. . . . . . . . . . . . . : Адаптер Microsoft ISATAP
Физический адрес. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP включен. . . . . . . . . . . : Нет
Автонастройка включена. . . . . . : Да

Туннельный адаптер Teredo Tunneling Pseudo-Interface:

Состояние среды. . . . . . . . : Среда передачи недоступна.
DNS-суффикс подключения . . . . . :
Описание. . . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
Физический адрес. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP включен. . . . . . . . . . . : Нет
Автонастройка включена. . . . . . : Да