Solved

Tried to Implement DFS, then Removed DFS and now //Server/share is inacessable

Posted on 2004-09-26
1
1,287 Views
Last Modified: 2008-01-09
Hi,

I was playing around with DFS, created a Domain Root for Team (which is also the name of a share on one of our machines that links to G:\Team on that machine). Below that are some other folders, like Team Folders (also shared individually) that house the file shares for individuals. Now, after creating the root and then removing it (ie no more DFS), the Team share is completely unaccessible from clients, who receive the message:

\\Server\Team refers to a location that is unavailable. It could be on a hard drive on this computer, or on a network. Check to make sure the disk is properly inserted...yadayadayada

I have tried removing the Team share and rebooting the machine and then putting it back on, but clients still receive the message as if the share is not there. Other shares do not appear to be affected.

Is DFS somehow persistant? What's going on? How do I get my old share back?

Hope you can help...
0
Comment
Question by:jbreg
1 Comment
 
LVL 33

Accepted Solution

by:
NJComputerNetworks earned 500 total points
ID: 12158936
Here is some general information on DFS: http://www.microsoft.com/windowsserver2003/techinfo/overview/dfsfaq.mspx

When you create a DFS root, your clients will access the root using \\domainname.com\dfsroot

In your case, you named the DFS root the same name as a share on the server.  \\domainname.com\team

Once your clients connect to \\domainname.com\team, they will see the share links that you create:

\\domainname.com\team\share1
\\domainname.com\team\share2
\\domainname.com\team\team ...etc

I think there may be a conflict with this name now...  Are you sure that you disabled DFS properly?  Here is a document that shows you how:  http://www.jsifaq.com/SUBJ/tip4900/rh4964.htm

I think you have two options:

1) verify that DFS is completely removed from AD and DNS
2) Change the name of the TEAM share to something like "TEAM DATA".

Also, just to be sure that this isn't a simple permissions issue, make sure that you verify that clients have appropriate permissions to access the TEAM share.

Another test would be this:

From the server

1) start --> RUN --> \\servername

This will show you that shares on the server.  Do you see the TEAM share?  Can you access it?

2) perform the same test from a client workstation

Thank you,

Joe Poandl MCSE

0

Featured Post

NAS Cloud Backup Strategies

This article explains backup scenarios when using network storage. We review the so-called “3-2-1 strategy” and summarize the methods you can use to send NAS data to the cloud

Question has a verified solution.

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

Suggested Solutions

Title # Comments Views Activity
Not a Schema Admin?  Schema Role on Non-AD Controller? 7 49
Trasfering FSMO roles 8 104
Unexpected Windows system folders on D drive 16 84
DHCP lease duration / Migration 8 53
On July 14th 2015, Windows Server 2003 will become End of Support, leaving hundreds of thousands of servers around the world that still run this 12 year old operating system vulnerable and potentially out of compliance in many organisations around t…
A quick step-by-step overview of installing and configuring Carbonite Server Backup.
This Micro Tutorial demonstrates using Microsoft Excel pivot tables, how to reverse engineer competitors' marketing strategies through backlinks.
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…

809 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