Go Premium for a chance to win a PS4. Enter to Win

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

Cross domain share access

Hi Everybody,

We have the following problem on our domains:
There are 2 active domains. D.local and P.local. On the P.local domain the P.local domain is trusted, external trust type and non transitive.

On the P.local domain is a server with a share that is public for all users. Now when connecting to the share via \\x.x.24.35\Diasys from the D.local domain there is a challenge response. But the idea is that we don’t want a challenge response so we can start a batch file for al the users from the D.domain on the P.domain

Who has tips or ideas?

Thanx Paul
0
paulvanhelden
Asked:
paulvanhelden
  • 4
  • 2
2 Solutions
 
Darius GhassemCommented:
You need to create a Universal Group or Global Group on D.local then add this Group into Domain Local Group in P.local then add this Domain Local Group to the Share folder with proper permissions
0
 
paulvanheldenAuthor Commented:
Darius,

I did do something like that, and will try it out this coming day's on tuesday I can give you a responce if it works or not.

Thank you,
Paul
0
 
Darius GhassemCommented:
Sounds good let me know
0
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.

 
paulvanheldenAuthor Commented:
We have tried this solution, but still got some issues. From within the domain as a not domain user this works, but from the D.domain to the P.domain users still get the challenge responce screen.
Tomorrow I've got an expert overhere and we are going to test some scenarios to eliminate things.

To be continued.
Paul
0
 
paulvanheldenAuthor Commented:
When we switched from ip to names in the unc path declaration everything works. It looks like the outsourcing party has blocked some kind off acces on the ip level. But when using names eg. Server.d.local we could connect to the share. So the local group connected to this share with the group controlling all users works fine, and with the users we mean the users from both the D.local as the P.local.
0
 
paulvanheldenAuthor Commented:
Own comment gives extra info for the solution.
0

Featured Post

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!

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