mitchell1981 Posted January 30, 2017 Posted January 30, 2017 Not sure what is going on here, but before when we typed in: \\domainname\ We would be presented with the domain shares, Netlogon and Sysvol. Now it doesn't work. It just says the network path was not found. If we specify one of the shares such as: \\domainname\sysvol it works fine. Pinging the domain name returns one of the domain controllers as it should. Also, if we put in any of the domain controllers: \\dc01\ it works and shows the shares. Does anyone know how the domain share itself is configured and how I check it? It appears to be breaking some of our group policy scripts.
Fazza Posted January 30, 2017 Posted January 30, 2017 Not seen the issue before myself but it sounds like a possible DNS issue so that might be a starting point for you. 1
mitchell1981 Posted January 30, 2017 Author Posted January 30, 2017 Yes, have been using the FQDN. It seems very odd to me that everything works as expected apart from going direct to the domain name. Can't see anything obviously wrong in DNS but will keep looking.
mtillbrook Posted February 6, 2017 Posted February 6, 2017 sounds like a DNS issue. Try and ping your domain name from CMD and see what you get? You should be able to ping domainname.local and get a responce back from a domain controller. If you don't get anything then your DNS is not well!
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now