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
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
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
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
Tomorrow I've got an expert overhere and we are going to test some scenarios to eliminate things.
To be continued.
Paul
ASKER
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.
ASKER
Own comment gives extra info for the solution.
ASKER
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