up vote 2 down vote favorite
share [g+] share [fb]

One of the lab computers at the school I administer is not able to access a any shares under the \\ad\data$ directory. I can access it from any other computer on the network. If I use the IP \\192.168.1.248\data$ I can access the files properly. If I use the FQDN: \\ad.domain.name\data$ it also works. Any other computer at the school is also able to access this share properly.

When I try to access the share with \\ad\data$ I get the message "You do not have permission to access \\ad\data$. Contact your administrator to request access." I am logged in with the domain administrator account.

Any idea on what would cause a single domain computer to not be able to access a share that it should have access to?

The server is running Windows Server 2008 and the computer is running Windows 7 SP1.

UPDATE

Issue is now happening on multiple other computers on the network, staff computers and student computers. I am starting to think there is something seriously wrong with the Active Directory server.

link|improve this question
75% accept rate
I would recommend asking for a moderator to move your question to ServerFault.com as this kind of issue is exactly in SF's wheelhouse – Scott Chamberlain Feb 29 at 18:58
feedback

3 Answers

up vote 1 down vote

I have seen an issue like this and it was caused by the DNS being set not to append the domain name automatically.

So, I would check that Append primary and connection specific DNS suffixes is selected and that Append parent suffixes of the primary DNS suffix is ticked.

This can be found via

Control Panel\Network and Internet\Network and Sharing Center
Local Area Connection Status
Properties
Internet Protocol Version 4 (TCP/IPv4) and/or Internet Protocol Version 6 (TCP/IPv6) 
Properties
Advanced
DNS
link|improve this answer
I checked and this this setting was already set this way. – Nick Feb 2 at 16:28
If you open up a command prompt and type nslookup ad does it give different results from what you get if you type nslookup ad.domain.name ? – sgmoore Feb 2 at 17:59
The results are the same and when I do nslookup ad it shows me the ad.domain.name along with the correct address – Nick Feb 2 at 18:05
feedback
up vote 0 down vote

It could be possible that the client computer is using saved credentials. You can check using the Windows Credential Manager under Control panel.

Does this occur under a Local Admin account, eg *machine_name*\Administrator?

Is the machine authenticating to the domain controller properly?

link|improve this answer
There are no saved credentials on the client computer. The local admin account has the same issues as the domain accounts. The machine is logging into the domain fine, it is applying group policies as expected. – Nick Feb 2 at 16:34
feedback
up vote 0 down vote

Make sure that you aren't already connecting to \ad using different (or old) credentials. I've seen similar issues when I had a mapped drive connected to a share on a server using my "regular" domain account and then I tried to connect to another share on the same server using my domain "admin" account.

Does a reboot resolve the problem?

link|improve this answer
feedback

Your Answer

 
or
required, but never shown
discard

Not the answer you're looking for? Browse other questions tagged or ask your own question.