Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1155
  • Last Modified:

Stand-Alone DFS errors

I have created a stand alone DFS namespace on a Windows Server 2008 (Enterprise) - it is in a workgroup. When I try to browse to the DFS share from a computer on another subnet I get the error network path not found, but all other shares on the server are accessible. I have ports 135-139 and port 445 opened on the firewall. If I try to map a drive to the share (\\server\namespace) it prompts for credentials and maps properly, but the links then give the error "linkname is inaccessible - the network location could not be found".
0
jsharp7429
Asked:
jsharp7429
  • 3
  • 3
3 Solutions
 
Justin YeungSenior Systems EngineerCommented:
did you use FQDN on the DFS path? it looks like it can't browse to it with just UNC path.
0
 
jsharp7429Author Commented:
I am using the IP to map the drive. Would I still need to use the FQDN?
0
 
Justin YeungSenior Systems EngineerCommented:
since it is in workgroup you will have to input user name as

workgroupname\username on 2008server local user and group
and password can't be blank as the default local policy unless you disabled it.
0
Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
jsharp7429Author Commented:
The same issue occurs when using the credentials as specified.
0
 
Justin YeungSenior Systems EngineerCommented:
can you browse to the root of DFS by using the DFS server credential?

and are the shared foldesr below it under the same server? or redirected to a different shared location?

verify if you can browse to the shared location by the real unc path.

since you are in workgroup environment, you might need the actually account/password for the real server that you are accessing.
0
 
jsharp7429Author Commented:
It turns out that since DFS uses NetBios for resolution by default, I needed to add an entry in the LMHOST file on the clients to allow them to resolve since they were on different subnets. Also, after reading your post - I started thinking about authentication, and while I was using the proper credentials, I was only entering them when I mapped a drive. I discovered that we had a group policy enabled that was blocking the storage of credentials. Once that was disabled and the LMHOST file was modified, it worked like a charm. Thans for your help!
0

Featured Post

Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

  • 3
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now