Start a Conversation

Unsolved

This post is more than 5 years old

870

January 11th, 2014 12:00

Cannot access share on root vdm from domain controller

We are having trouble access shares from two of our domain contollers using the dns name.  We can access using the fqdn and by IP.  The domain controllers are running DNS and WINS.  When we try to access it just by dns name we get a network path not found error.  You can run a nslookup and the name resolves on those machines.  The domain controllers are server 2008 and server 2008 r2

Any ideas on how to fix this?  Thanks in advance for any help.

January 12th, 2014 18:00

Please consider moving this question as-is (no need to recreate) to the proper forum for maximum visibility.  Questions written to the users' own "Discussions" space don't get the same amount of attention and can go unanswered for a long time.

You can do so by selecting "Move" under ACTIONS along the upper-right.  Then search for and select: "Celerra Support Forum" or "VNX Support Forum".

Celerra Support Forum

VNX Support Forum

This has hints of having similarity to the following user's experience:

Cannot access CIFS shares after installing 2008R2 server.

Quite a bit was discussed and recommended (unjoin and rejoin to domain, review of SPN's, reviewing NTLM vs Kerberos, etc), but it probably would require a network trace and reviewing with EMC support to resolve.  I would suggest reviewing the comments and recommendations in the post to see if maybe there is anything that you can apply to your troubleshooting.  Ultimately though, it may be best for EMC Support to review and may be elusive enough to require packet captures.

3 Posts

January 13th, 2014 06:00

Thank you for the response.  I have moved this to the celerra support forum.

4 Operator

 • 

8.6K Posts

January 13th, 2014 07:00

Try running nas_checkup – it will point out a number of config problems

I assume the DNS name you are using is the same as the CIFS server name or an alias ?

3 Posts

January 13th, 2014 08:00

Yes, it is the same name. All of the workstations and servers in our environment can access it by that name with no problem. It is only those two domain controllers.

4 Operator

 • 

8.6K Posts

January 13th, 2014 09:00

my advice

- Troubleshoot the name resolution on these two systems, DNS, nbtstat, ....

- If that doesn’t help raise an SR – between debug logs and network trace it should be possible to find out.

From the initial symptoms my guess is that the problem isn’t on the VNX side but on the client config

No Events found!

Top