Is it possibe to setup a DP on a workstation in another domain

[mbartosh]

I am trying to setup a DP on a workstation in domain that is not in the same
domain as the site server. Is this possible? I keep getting the message:
Cannot establish connection to
["Display=\\C004545\SMSDIST$\"]MSWNET:["SMS_SITE=A01"]\\C004545\SMSDIST$\

I have setup many DPs in the same domain as the site server, but this is the
first time I have tried to setup one in another domain. I have put the site
server machine account in the local admin group on the dp without success.
--
Mike Bartosh
Systems Specialist
Apria Healthcare

[Garth]

Is there a trust between the domains? Can you manually connect from the site
server to the other PC? You do know that Workstations are not supported as
DPs within SMS 2003.

"mbartosh" <mbar...@discussions.microsoft.com> wrote in message
news:E83E9E16-3DCC-4CF3...@microsoft.com...

[mbartosh]

We do have a two way trust between our two domains. A DP can be setup as a
workstation share.

The problem is that the site server is being denied access to the share. I
ran the at command: "at 9:30 cmd /interactive" on the site server, and then
from the command windows I did a dir on the share \\xxxxx\smsdist$ which
returned "access denied". Until I resolve this problem, the DP is not going
to populate.

I think I have tried every combination to give the share permission for the
site server to access it, but no luck. I put the machine account for the
site server in the local admins group on the DP among other things.

--
Mike Bartosh
Systems Specialist
Apria Healthcare

[Garth]

A DP is NOT supported on workstations within SMS 2k3, it might work but....

I think that you posted on myITforum.com as well and the issue is that your
are trying to create a DP across forests. Which is not supported. All SMS
roles must exist within the same forest. Create a separate child primary
site and connect it to the primary site, this will allow for applications to
be distributed to the other forest.

"mbartosh" <mbar...@discussions.microsoft.com> wrote in message

news:9B1B38E0-F45F-4FDC...@microsoft.com...

[Thorsten Lau]

solution 1:
Add the DP with its fqdn to the hosts file. Windows will then use this fqdn
instead of the siteservers one, and authentication should work.

solution 2:
allow anonymous logons to the share (local group policy)
or try this regkey first: http://support.microsoft.com/kb/281308/en-us