Win7x64 fails to recognize type of network (home, domain, public)
Problem: Windows 7 Enterprise x64 fails to detect the networ type, where it should select Domain Network and Sharing Center reports it as an "Unidentified Network" thus taking the settings from the public network which, according to our company policies, drop all incoming packages for security purposes, disabling agent reporting for the several agents the company uses (antivirus, software distribution, etc.) Scenario: Windows Server 2003 Domain, Static IP Address for all Win7 x64 computers that present the trouble (actually almost all computers use static ip). DNS servers were pinged succesfully, DNS suffixes were tested and working, as a matter of fact all settings are working well for the rest of the computers with Windows XP x86 and Windows Vista x86. We have doublechecked every setting so my question is how does this detection work? does it work with static ip? do I have to check the Domain Controller? In advance thanks for your attention.
July 23rd, 2011 12:31pm

Hi, Based on my knowledge, the only NLA changing is multiple active profiles in Windows 7: http://blogs.technet.com/b/networking/archive/2010/09/08/network-location-awareness-nla-and-how-it-relates-to-windows-firewall-profiles.aspx I just wonder the difference between the Vista machines and the Windows 7 machines. Such as VLAN setting, network connection. If these machines was in a child domain, please check: http://support.microsoft.com/default.aspx?scid=kb;EN-US;980873 The Network Location Awareness (NLA) service expects to be able to enumerate the domain’s forest name to choose the right network profile for the connection. The service does this by calling DsGetDcName on the forest root name and issuing an LDAP query on UDP port 389 to a root Domain Controller. The service expects to be able to connect to the PDC in the forest domain to populate the following registry subkey: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\NetworkList\Nla\Cache\IntranetForests If something hinders the DNS name resolution or the connection attempt to the DC, NLA is not able to set the appropriate network profile on the connection. Hope that helps Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
Free Windows Admin Tool Kit Click here and download it now
July 26th, 2011 5:41am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics