Hidden Share access via VPN and FQDN

[PatrickFarrell]

DCDIAG doesn’t actually flag DNS being misconfigured in many cases. I wrote up a post for DNS config so I don’t have to always retype it

Active Directory DNS Refresher

It’s DNS. It’s always DNS. No, DNS is fine, it’s not DNS, trust me. It was DNS. I’m posting because in the last few weeks we’ve had a few posts that turned out to be misconfigurations with DNS in a domain environment. Things like Domain controllers pointing at themself first for DNS, or having a public DNS server on the NIC of the Domain Controller or the clients. Hopefully this will help some people get out in front of potential issues. The general rules for DNS in an AD E…

Ok that being said, I don’t think DNS is your issue here, but check it anyway to make sure you are set properly to avoid future replication issues.. To rule Sophos out, can you hit the hidden share from a machine on the same network? (I can’t imagine it’s Sophos, but might as well rule it out).

And just so I’m making sure I’m reading this right, both home$ and documents point to the same folder on the file system? If they don’t, have you granted permissions both to the share and the file system?

I’m heading out for the night been up about 24 hours, but those questions will get the next person who reads the thread started. I’ll check back in a few hours.