1) If the network appears as 'Private' or 'Public' network instead of 'Domain' network, restart the 'Network Location Awareness' service then check to see whether this has corrected (temporarily) identified the network as 'Domain'. If so, press on - if not, you have other problems.
2) determine the MAC address of the router by opening an administrative command prompt and typing:
ipconfig
...to determine the gateway IP address, then
arp -a | find "xxx.xxx.xxx.xxx"
...where xxx.xxx.xxx.xxx is the gateway IP address. The quotation marks ARE necessary. Note the MAC address which is in the format xx-xx-xx-xx-xx-xx
3) Locate and identify the GUID registry keys located under:
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\NetworkList\Signatures\Managed]
4) If there are 2 almost identical-looking keys, then one of them was the former domain profile (and current default domain profile), and the other is the new (but not default) domain profile. Look at the 22nd character in the name. '0' makes it the default; '1' is the secondary:
010103000F0000F0A00000000F0000F088C2775714494212F7E06586D446228321CE58E47AAB3AEDC640CA5DBE63F05B
010103000F0000F0A00001000F0000F088C2775714494212F7E06586D446228321CE58E47AAB3AEDC640CA5DBE63F05B
...look at the value for 'DefaultGatewayMac' under each key; the key showing the mac address identified in step 2) must become the default.
...also note the value for 'ProfileGuid' under each key
5) if the registry key having '0' (zero) in position 22 has the wrong value for 'DefaultGatewayMac'
...locate find the registry key under:
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\NetworkList\Profiles]
...that has the same value as 'ProfileGuid' and delete that key
...then delete the registry key having '0' in position 22
6) assuming the registry key with a '1' in position 22 has the correct value for 'DefaultGatewayMac'
...rename the key by changing the '1' in position 22 to a '0'
7) For the values stored in "Description" and "FirstNetwork", remove the spaces and trailing number from the domain name
8) For the value stored in "Source", remove '100' from the beginning of the value, leaving 'a0'
9) For the value in "ProfileGuid",
a) locate this in the data for the value "NetworkList" under the key:
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\NetworkList\NewNetworks]
...and delete this string from the data
b) locate the matching key name under:
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\NetworkList\Profiles]
...for the value stored in "ProfileName", delete the spaces and trailing number from the domain name
...change the value for "Category" to '2'
...add the DWORD "CategoryType" and leave set to '0'
10) REBOOT the DC
11) upon logging back into the DC as an administrator, immediately open the 'Network and Sharing Center' Control Panel applet to confirm whether the network has been detected 'Private' or 'Domain'
...and if it comes up as 'Domain' you're done. Otherwise,
12) repeat step 1) to correct the network detection
13) locate the registry key:
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NlaSvc]
...open the value "DependOnService" and add 'DNS' with a carriage return to the bottom of the list and then 'OK' to save
14) REBOOT the DC and the problem should be solved.
Comments (0)