Solved

Cannot Access DFS Share from XP Clients, UNC is fine

Posted on 2009-05-06
4
5,199 Views
Last Modified: 2012-05-06
I have been running DFS for a while now. There is a namespace \\XXXX\Public and underneath the folders Shared & Secure.

Up until a few days ago these were present on servers in 2 sites in London & Kent (and replicating). The Kent server was just a temp server, so I have recently added a new permanent server and effectively moved the DFS shares from the temp to the new permanent server using DFS replication. I have disabled the DFS folders on the old servers.

The trouble is whilst the 2003 terminal servers see the new DFS share fine, most of the XP clients do not. When you try and access the DFS share you get the following message:

"\\XXXX\Public\Shared is not accessible. You might not have permission to use this network resource....

Configuration information could not be read from the domain controller, either because the machine is unavailable, or access has been denied.

If you access the path using the true server UNC it works fine \\XXXXX\SharedDrive

I have tried using dfsutil with the following switches /pktflush, /spcflush, /purgemupcache with no success.

The results of dfsutil /pktinfo are as follows

Entry: \XXXXX\public
ShortEntry: \XXXXX\public
Expires in 0 seconds
UseCount: 1 Type:0x8081 ( REFERRAL_SVC DFS FAILBACK_ENABLED )
   0:[\XXXXX\Public] State:0x119 ( ACTIVE TARGETSET )

Entry: \XXXXX\public\shared
ShortEntry: \XXXXX\public\shared
Expires in 0 seconds
UseCount: 0 Type:0x8010 ( OUTSIDE_MY_DOM FAILBACK_ENABLED )
   0:[\XXXXX\SharedDrive] State:0x121 ( TARGETSET )

It may be worth adding that I have created a new DFS root on the new server and the clients can access it with no problems.

I really don't want to have to delete and recreate the dfs links if possible because the replication is tied into it and I'm worried it might break.

Any ideas would be greating appreciated.
0
Comment
Question by:delkent
  • 2
  • 2
4 Comments
 
LVL 38

Expert Comment

by:ChiefIT
ID: 24313892
Lots of things can cause this. Most likely it is the inability to access the DFS share by netbios name resolution.

I would like to see if a few things may be the solution first off.

Since you can access one of the root servers, maybe your problem is more of a security component than a communications one. Do you have internet explorer enhanced security on the server and/or client. This would prevent you from running .exe,.bat, .xls, .vbs, .msi, and other operating system intrusive files. You could try to add the unc path as a trusted site in internet explorer to see if this is your issue.

Now that the security component is check and found to not be the problem, maybe we should check the permissions of the SHARE as well as the permissions of NTFS. When setting up the namespace, you will have to configure your namespace's share permissions. Those allow you access to the share. Like any other share, the share permissions allow you access to the folders and subfolders within the share from a remote location. Then, the NTFS share allows you access to the drive sectors the share resides on. With the inability to access the share, it sounds like your SHARE permissions are off, not the NTFS permissions. To redo this, you may have to recreate the namespace and edit the share permissions to full control. It's easiest to control the permissions at the NTFS level than the share level.  
0
 

Author Comment

by:delkent
ID: 24317473
Hi - the DFS folder share permissions were everyone - full control, so I'm not sure that's it.

I'm thinking I will need to recreate the namespace but it is a last resort as I will have to set up replication again and that has proved to be a bit shaky if there is existing data in a directory
0
 
LVL 38

Expert Comment

by:ChiefIT
ID: 24337335
Well, let's do a lookup to the namespace:

http://support.microsoft.com/kb/830578

Let's use this tool to troubleshoot the namespace connection. NBlookup troubleshoots netbios translation.

Do you have a WINS server?
0
 

Accepted Solution

by:
delkent earned 0 total points
ID: 24483773
Hi there are no WINS servers on the network.

Thanks for your help, but the only thing I could do to get it working is delete and recreate the namespace. Everything seems to work fine now
0

Featured Post

Enterprise Mobility and BYOD For Dummies

Like “For Dummies” books, you can read this in whatever order you choose and learn about mobility and BYOD; and how to put a competitive mobile infrastructure in place. Developed for SMBs and large enterprises alike, you will find helpful use cases, planning, and implementation.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

Sometimes people don't understand why download speed shows differently for Windows than Linux.Specially, this article covers and shows the solution for throughput difference for Windows than a Linux machine. For this, I arranged a test scenario.I…
Today, still in the boom of Apple, PC's and products, nearly 50% of the computer users use Windows as graphical operating systems. If you are among those users who love windows, but are grappling to keep the system's hard drive optimized, then you s…
Two types of users will appreciate AOMEI Backupper Pro: 1 - Those with PCIe drives (and haven't found cloning software that works on them). 2 - Those who want a fast clone of their boot drive (no re-boots needed) and it can clone your drive wh…
The Email Laundry PDF encryption service allows companies to send confidential encrypted  emails to anybody. The PDF document can also contain attachments that are embedded in the encrypted PDF. The password is randomly generated by The Email Laundr…

679 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question