Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I have a 3 site network A, B, and C. Each site has its own DC, that replicates to the others. Each site also has a local NAS (Thecus) device. The NAS devices should be accessible from every other site.

I'm having an issue where the NAS device at site A cannot be reached from A's DC, but every other machine everywhere else(and with any login account) can reach the shares.

From site A's DC, we can ping that NAS device and we can browse to the admin page.

My thought, is there must be some type of group policy restricting that machine from accessing that NAS device. I say the machine, because the login account can access it from the same site, on different machines, and from other sites as well. If we use another login on site A's DC, we still cannot browse to the share.

Where is this type of restriction defined in group policy? I haven't had a whole lot of experience with group policy.



I guess I forgot about an error we had received in the event logs. It's error 5722: "The session setup from the computer failed to authenticate. The name of the account referenced in the security database is . The following error occurred: Access is Denied.

Update This was resolved by applying a SMB patch for Windows Server 2008

share|improve this question
up vote 1 down vote accepted

Any Group Policy would likely apply to all Domain Controllers, not just the one in Site A. Troubleshooting why one machine can't get to another machine when everything else seems to work just find can get tricky. I don't know those NAS devices at all, so I don't know if they have any useful logging on them; if this were a Windows machine I'd ask to have the security-log turned on and see what it catches for this problem.

If there are no useful logging functions to exploit in the NAS, my next step is to try and see what a connection looks like on the wire. Microsoft error reporting is not always useful, and frequently the reason for a connection failure will show up on a network trace. That does take some skill for interpretation, though.

One thing to check before delving into packets is the Local Security Policy on that DC. Make sure it looks the same as your other DC's. When talking to non-Windows devices, sometimes that can have a very big effect on connectivity over SMB.

share|improve this answer
I did take a quick wireshark dump, and there were no SMB packets in the dump. Lasted for about 1 minute, with 3-4 attempts at trying different things to get connected. – MJ. Dec 9 '10 at 15:44

As you suspect, it seems to be an authentication/authorization issue. Try and use a "net use" command and connect to a samba share (i suppose you are using) manually, supplying the correct share username/password.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

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