Re: Best Practice for multiple servers
From: Doug (anonymous_at_discussions.microsoft.com)
Date: 07/01/04
- Next message: Stephanie Doakes [MSFT]: "RE: Adding Trusted Certificate Does not work (for me)"
- Previous message: Doug: "Re: Best Practice for multiple servers"
- In reply to: Lanwench [MVP - Exchange]: "Re: Best Practice for multiple servers"
- Next in thread: Lanwench [MVP - Exchange]: "Re: Best Practice for multiple servers"
- Reply: Lanwench [MVP - Exchange]: "Re: Best Practice for multiple servers"
- Messages sorted by: [ date ] [ thread ]
Date: Thu, 1 Jul 2004 06:36:00 -0700
>-----Original Message-----
>Doug wrote:
>> Hi All,
>>
>> I wondered if I could get some advice on implementing my
>> system. I will have a SBS 2003 Standard running one of
my
>> businesses.
>>
>> I have a second business that will be on Win2K Server
with
>> separate SQL Server 2000 machine.
>
>Will this be on its own domain?
>>
>> Both businesses are separate with the exception of 1
>> employee, who should be able to access BOTH setups.
>
>Where are the networks/domains? Are you talking about
remote access of some
>sort?
>
>> I
>> wanted separate domains, but SBS2003 won't trust any
other
>> domains. My question is how do I get that 1 employee to
be
>> able to easily access both setups? He will need the
>> functionality of the SBS2003 (email, files, etc.) but
also
>> be able to get into the SQL server via the Win2K server
>> authentication. I was hoping to avoid having the second
>> business authenticate through the SBS2003.
>
>If they're in one office, he can access resources on the
other domain if he
>provides the correct credentials for it when mapping a
drive - for example,
>in a login script (and presuming he can reach the other
network & ping the
>other server by name):
>
>net use x: \\server\share /user:otherdomain\username
<enter>
>
>>
>>> I will eventually have a remote office connecting to
the SBS2003.
>>
>> Thanks in advance for any suggestions.
>
>
REPLIES TO YOUR POST:
>"Will this be on its own domain?"
It depends. I was hoping to have it in its own domain
because there are 18 clients accessing only the SQL server
and only 10 accessing the SBS2003 (total = 28 users). I
thought it would be better to get CALs for Win2K for those
who will only be using the SQL server. But if I can't use
2 domains in this scenario for the 1 employee then perhaps
I would use 1 domain through the SBS2003.
>Where are the networks/domains? Are you talking about
remote access of some
>sort?
Both networks are in the same physical location. I have
not set up the network yet. They currently have several
separate peer-to-peer networks that I hope to eliminate.
There will be no remote access other than through Remote
Web Workplace for a couple of users. In the future they
may have a remote office connecting to the SBS2003.
>If they're in one office, he can access resources on the
other domain if he
>provides the correct credentials for it when mapping a
drive - for example...
Will this affect SQL server access?
- Next message: Stephanie Doakes [MSFT]: "RE: Adding Trusted Certificate Does not work (for me)"
- Previous message: Doug: "Re: Best Practice for multiple servers"
- In reply to: Lanwench [MVP - Exchange]: "Re: Best Practice for multiple servers"
- Next in thread: Lanwench [MVP - Exchange]: "Re: Best Practice for multiple servers"
- Reply: Lanwench [MVP - Exchange]: "Re: Best Practice for multiple servers"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|