This is the error message I get when trying to access any shared folder on a domain controller through its UNC path.

This specifically is the SYSVOL folder so it should be accessible for all domain members.

Sharing and security permissions are properly set.

Other domain controllers and shares are accessible through UNC paths.

I can, however access this share on its FQDN (<server>.<domain>.local).

So far every related article I've found is pointing toward SMB security, however, this hasn't been tampered with in any way.

Thoughts and suggestions anyone?

I think the machine is unavailable or you don't have access.





Luke

never put you in the geeks category before ...

Is it replicating properly?

yep.

yay - I'm not geeky enough to have a fucking clue what you're talking about Kuif

nor me!

I was tempted to say "have you turned it off and on again?", but thought that would be an unhelpful cliche.

try creating a hosts file in windows system or system32 (google hosts files in windows)

it might be a wierd wins issue - ms claims you don't need wins servers in their domains now but I've been given lots of advice to still include a wins server as a lot of their legacy code works alot better with either a wins server installed or a hosts file.

in the hosts file put the name of the controller that's giving you problems and then add the ip address of that machine next to it.

You could also try revoking the controller's rights and removing it from the ad and then re-adding it and re-promoting it.

M

I was just about to say that, but Goose beet me to it.......

w00t sensible advice!

Shame it's a case of "been there, done that". Tried the hosts and lmhosts files, with and without wins.

Problem is it can find the server without problems, it keeps denying access to shares though.

Gonna demote, disjoin, rejoin and promote, see what happens...

It's like running a guild then?


Luke

Yea, shame I cant demote it, turn it over to some other unlucky chelsea fan and walk away

aye the hosts thing was a "you never know" thing

My next step would be take it out and then re add it to the domain.

make sure you use the ad domain admin account as that ensures it's nothing funny with your admin account.

If that doesn't work try \\servername\c$ that should always work.

If that doesn't work I hate to say it, it might be quicker to just reinstall the server from scratch.

other questions to ask.

is it a Windows 2000 AD domain or Windows 2003 AD Domain ?

Make sure you're not trying to add a windows 2003 server to a windows 2000 domain as I've heard you need to upgrade your AD to 2003 accross the board before windows 2003 servers are happy there.

Check nobody has installed any screwy software on the server. I know nobody should have but just check the easy stuff first.

With these things it's often some stupid thing that was left out or unconfigured during install that trips you up.

Always start with the DUH! solutions first and work up, as it can save you a ton of work diagnosing something that was actually a red herring all along.

Have you given all the AD Controllers trusted rights?
Are you having any issues with DNS?

M