Hello I have a couple of Windows 7 Professional PC’s on which NLA incorrectly detects the network as a Work network when it should be a Domain one. · Our 2003 Domain controllers are on one subnet and our workstations are on another · There are no restrictions between the subnets · The workstation in question is a member of the domain and logs into the domain with no issue · Other Workstations correctly detect the network as Domain How can I change the network location to make it a Domain one? Any help appreciated Thanks

Hi, The Domain network location type is automatically applied to your computer if it is joined to an Active Directory domain. If your computer is joined to a domain, then you cannot change the network location type. So if the computer is joined to a domain, the Network Location type will be automatically applied. I suggest to disable the firewall for a test. Also, you may check this in Clean Boot to determine whether the 3rd party software cause this. In addition, please check whether the connectivity between the computer and domain controller is good. Hope this 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.

mitred wrote: Hello I have a couple of Windows 7 Professional PCs on which NLA incorrectly detects the network as a Work network when it should be a Domain one.   ·        Our 2003 Domain controllers are on one subnet and our workstations are on another ·        There are no restrictions between the subnets ·        The workstation in question is a member of the domain and logs into the domain with no issue ·        Other Workstations correctly detect the network as Domain   How can I change the network location to make it a Domain one?   Any help appreciated   Thanks   Have you tried to renew the network address on the troubled machines? Sometimes this can be linked to DHCP, too. As the machines are on a different subnet, who is responsible for registering the IP-addresses of the workstations; do the workstations register directly with the AD server - is this the duty of the DHCP server/device or what other means ensure that your IP-addresses are correctly maintained on your AD name-servers? Wolfgang

Thanks for the responses. I have tried turning the firewall of and it makes no difference. I have moved one of the Windows 7 PC's onto the same subnet as one of the domain controllers and given it a fixed IP address but it still detects it as a work network. Connectivity seems good, I log on to the domain fine and can ping the domain controllers OK.

mitred wrote: Thanks for the responses. I have tried turning the firewall of and it makes no difference.  I have moved one of the Windows 7 PC's onto the same subnet as one of the domain controllers and given it a fixed IP address but it still detects it as a work network.  Connectivity seems good, I log on to the domain fine and can ping the domain controllers OK.   Can you resolve the correct DNS name of your workstation on the server? (You can test that via "nslookup workstationname servername") And which DNS-server is configured on the workstation? Wolfgang

Yes, DNS all seems to be working fine. The name is resolved correctly on two of the local dns servers which are also DC's. These are the DNS servers which the client has configured. Thanks

Hi, You may try to login with another user or re-join the domain for a test. Meantime, to restart the Network Location Awareness service if the issue still persists.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.