Quantcast
Channel: File Services and Storage forum
Viewing all articles
Browse latest Browse all 13565

Network is set to domain but traffic being blocked as public network

$
0
0

Hi all.

I have a fresh install of Windows Server 2016 that's been added as a member to a Windows SBS Server 2011 domain. It has not been promoted or anything else. It has 2 network interfaces where one is connected to the rest of the network and it's been configure with static info. Network connectivity works fine in both directions. All updates have been installed as of yesterday (July 17, 2018). I created a share on this server that although accessible from the primary domain controller other computers on the network are refused.

In troubleshooting I've found that if I drop the firewall the share is accessible. When the firewall is back on it shows up as connected to a domain network and I've gone into the firewall and made sure that file and print sharing are allowed but still can't connect with the firewall up.

Another troubleshooting step was to turn on firewall logging for dropped packets on all three networks and creating a different name for each of the logs e.g. public networks firewall log is named "publicfirewall" and the private network firewall logs are named "privatefirewall". After enabling the firewall and trying to connect to the share the only log that's getting any entries is the one for the public network even though the NIC connected to the network comes up as in the domain network.

This is a basic install with very basic roles and/or features installed. Can anyone provide any guidance for fixing this?

Thanks

Joe


Viewing all articles
Browse latest Browse all 13565

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>