RPC/HTTP - Client in different domain?
 

Greetings,
TIA for any input.

I've got some remote staff that currently use RPC/HTTP (we configure
the box on the local LAN and then ship it offsite).

They're currently in WORKGROUP mode, but I'm going to be creating an
AD 2003 Domain for them (NOTE: Their offsite LAN is not connected in
any way to our corporate LAN except via the Internet and RPC/HTTP...no
VPN either).

Will these clients still be able to authenticate/login to their
mailbox via RPC/HTTP if the machine account is a member of a different
domain?

When Outlook launches, they can specify the domain at login (e.g.
domain\username) so I'm hoping this would work.

Thanks again,
CB

RPC/HTTP - Client in different domain?
 

Will the domain for them be under the same root as your current domain?

I don't think the machine accounts have any influence on RPC over HTTP
authentication....they are authenticating with their domain\user account....


"CB" wrote in message
...
Greetings,
TIA for any input.

I've got some remote staff that currently use RPC/HTTP (we configure
the box on the local LAN and then ship it offsite).

They're currently in WORKGROUP mode, but I'm going to be creating an
AD 2003 Domain for them (NOTE: Their offsite LAN is not connected in
any way to our corporate LAN except via the Internet and RPC/HTTP...no
VPN either).

Will these clients still be able to authenticate/login to their
mailbox via RPC/HTTP if the machine account is a member of a different
domain?

When Outlook launches, they can specify the domain at login (e.g.
domain\username) so I'm hoping this would work.

Thanks again,
CB

RPC/HTTP - Client in different domain?
 

Actually, this domain is not connected in any way (physically or
logically) to the 'Exchange Domain'.

After doing some more searching through this newsgroup, it appears
there are others who are operating in this fashion.

Thx,
CB

On Wed, 1 Nov 2006 12:23:11 -0500, "Betelgeuse"
wrote:

Will the domain for them be under the same root as your current domain?

I don't think the machine accounts have any influence on RPC over HTTP
authentication....they are authenticating with their domain\user account....


"CB" wrote in message
.. .
Greetings,
TIA for any input.

I've got some remote staff that currently use RPC/HTTP (we configure
the box on the local LAN and then ship it offsite).

They're currently in WORKGROUP mode, but I'm going to be creating an
AD 2003 Domain for them (NOTE: Their offsite LAN is not connected in
any way to our corporate LAN except via the Internet and RPC/HTTP...no
VPN either).

Will these clients still be able to authenticate/login to their
mailbox via RPC/HTTP if the machine account is a member of a different
domain?

When Outlook launches, they can specify the domain at login (e.g.
domain\username) so I'm hoping this would work.

Thanks again,
CB

RPC/HTTP - Client in different domain?
 

yes. they'll need to login to outlook specifically, not use the windows
login credentials though.

--
Diane Poremsky [MVP - Outlook]
Author, Teach Yourself Outlook 2003 in 24 Hours
Coauthor, OneNote 2003 for Windows (Visual QuickStart Guide)
Need Help with Common Tasks? http://www.outlook-tips.net/beginner/
Outlook 2007: http://www.slipstick.com/outlook/ol2007/

Outlook Tips: http://www.outlook-tips.net/
Outlook & Exchange Solutions Center: http://www.slipstick.com
Subscribe to Exchange Messaging Outlook newsletter:



"CB" wrote in message
...
Greetings,
TIA for any input.

I've got some remote staff that currently use RPC/HTTP (we configure
the box on the local LAN and then ship it offsite).

They're currently in WORKGROUP mode, but I'm going to be creating an
AD 2003 Domain for them (NOTE: Their offsite LAN is not connected in
any way to our corporate LAN except via the Internet and RPC/HTTP...no
VPN either).

Will these clients still be able to authenticate/login to their
mailbox via RPC/HTTP if the machine account is a member of a different
domain?

When Outlook launches, they can specify the domain at login (e.g.
domain\username) so I'm hoping this would work.

Thanks again,
CB