[1803, au] Windows Firewall - Domain network detected as Private

[DJ-1701]

Got a bit of a weird one... just over a week ago, my machine (or at least the Windows Defender Firewall) decided it was no longer on a Domain network, but a Private network and so items such as Remote Desktop, VNC, SIMS, etc were no longer being allowed by default.

 

Reinstalling my machine, twice, it is still believing it is connected to a Private network, not domain... this also appeared to happen on 1809 as well as 1803... any ideas?

[Oaktech]

add the domain dns suffix to the connection details.

 

Network and sharing -> ethernet -> properties -> click IPv4 -> properties -> advanced -> DNS tab -> add the domain suffix in the 'dns suffix for this connection' box. See if it helps.

[DJ-1701]

add the domain dns suffix to the connection details.

 

Network and sharing -> ethernet -> properties -> click IPv4 -> properties -> advanced -> DNS tab -> add the domain suffix in the 'dns suffix for this connection' box. See if it helps.

 

Thanks very much for the suggestion, but unfortunately it still persists in believing it's Private and not Domain... real headscratcher.

[Oaktech]

Thanks very much for the suggestion, but unfortunately it still persists in believing it's Private and not Domain... real headscratcher.

 

A*se...

 

Tried any of these? https://www.itechtics.com/change-network-type-windows-10/#Ways_to_change_network_types_in_Windows_10

[DJ-1701]

A*se...

 

Tried any of these? https://www.itechtics.com/change-network-type-windows-10/#Ways_to_change_network_types_in_Windows_10

 

Unfortunately seems to create a new network connection after altering the registry. Using powershell commands it refuses to change it to Domain. Bah.

[Mako]

Does your machine have a static IP?

 

Not familiar with a W10 network but last time I had this on W7 it was due to a DHCP/DNS issue. I narrowed it down by finding out that assigning the machine a static IP on the network range made it see that it was a domain network, removing static and allowing DHCP to take over made it go back to an unidentified network. Some clearing up of DHCP and DNS later and all was resolved.

[DJ-1701]

Does your machine have a static IP?

 

Not familiar with a W10 network but last time I had this on W7 it was due to a DHCP/DNS issue. I narrowed it down by finding out that assigning the machine a static IP on the network range made it see that it was a domain network, removing static and allowing DHCP to take over made it go back to an unidentified network. Some clearing up of DHCP and DNS later and all was resolved.

 

It's dynamic. Thanks I will give that a go when I am next at the machine.

[Duke5A]

Windows uses DNS to determine if it's on a domain network or not. What does your DNS settings look like? Should point to one of your domain controllers.

 

After a storm a few years ago I was bringing the data center back up and virtual machines came back up out of order. The domain controllers were powered on last. All of the other virtual machines had no DNS for a few minutes and all defaulted to public network. Nothing would talk to each other. That was fun.

[DJ-1701]

Well... I haven't tried either of those yet, as when I left the computer yesterday it was rebuilding, after I deleted the account in AD... to my supprise it was working fine... then I added it to the Active Directory group for Direct Access... and then it went nuts... so might be an issue for others on site. For the time being I have reinstalled the machine again without being in the Direct Access group (as I generally don't take the machine home), and plan on testing this on a virtual machine. Thanks for the help everyone, I will update when I have setup another machine with Direct Access enabled... and that I can connect to remotely to try things as and when suggested.

 

In the mean time, if anyone else has any thoughts, especially with Direct Access looking like the cause, please keep them coming. We have had Direct Access working for years before now, so very strange!

[DJ-1701]

Looking at Direct Access, it appears it was using an old certificate... selected a new one from the current CA and working fine. Annoying how that would affect the machine at work. Thanks all to everyone who chipped in to help.