WAN-LAN Architecture Question

I have a Win 2000 Advanced Server that has been serving as a file server and
Terminal Server. This server has a 20-user Server License and a 10-user TS
License. I want to separate the file server from the terminal server.

So...
I have purchased a new Win 2003 Server. I have purchased 3 5-CALs giving me
a total of 20 User/Device licenses.

What I am looking to do is place all of the LAN devices on the new server
domain AD. I want the Win 2000 server licensing to be used for the Remote
users, thereby taking advantage of these server licenses.

So here are my questions:
Do both servers have to be in the same domain?
If the servers have to be on the same domain, will the Win 2000 server be
treated as a single device, regardless of how many TS clients are logged into
that server?
Also, I have two NIC cards on both of these servers. Can I connect the two
servers in such a way that one set of NIC cards is used soley for the
communication between the servers?

Thanks!

> I have purchased a new Win 2003 Server. I have purchased 3 5-CALs giving me
> a total of 20 User/Device licenses.
>
> What I am looking to do is place all of the LAN devices on the new server
> domain AD. I want the Win 2000 server licensing to be used for the Remote
> users, thereby taking advantage of these server licenses.

You have to buy 2003 TS licenses. You can't transfer 2000 TS cals to 2003 TS
>
> So here are my questions:
> Do both servers have to be in the same domain? Yes
> If the servers have to be on the same domain, will the Win 2000 server be
> treated as a single device, regardless of how many TS clients are logged into
> that server? Sorry - don't understand the question
> Also, I have two NIC cards on both of these servers. Can I connect the two
> servers in such a way that one set of NIC cards is used soley for the
> communication between the servers? Not a great idea imo since you could double your bandwidth to both servers if you do adapter teaming and use a managed switch that supports it.
>
> Thanks!

I do not want to use the 2003 server for TS. The TS will remain on the 2000
server. The Remote users will login to the 2000 server. That server will
provide access to the file server (2003). I only want the 2003 server to
provide access to files.


"Joshua Bolton" wrote:

>
> > I have purchased a new Win 2003 Server. I have purchased 3 5-CALs giving me
> > a total of 20 User/Device licenses.
> >
> > What I am looking to do is place all of the LAN devices on the new server
> > domain AD. I want the Win 2000 server licensing to be used for the Remote
> > users, thereby taking advantage of these server licenses.
>
> You have to buy 2003 TS licenses. You can't transfer 2000 TS cals to 2003 TS
> >
> > So here are my questions:
> > Do both servers have to be in the same domain? Yes
> > If the servers have to be on the same domain, will the Win 2000 server be
> > treated as a single device, regardless of how many TS clients are logged into
> > that server? Sorry - don't understand the question
> > Also, I have two NIC cards on both of these servers. Can I connect the two
> > servers in such a way that one set of NIC cards is used soley for the
> > communication between the servers? Not a great idea imo since you could double your bandwidth to both servers if you do adapter teaming and use a managed switch that supports it.
> >
> > Thanks!

Thanks for that clarification.

You can have 2000 remain a DC and have the 2003 server just as a member
server for file access.

Licensing: you have 20 W2K cals and 10 W2k TS calls. You have added (3) 5
packs W3K server for 15 '03 cals [unless I am misreading 3 5-cals].

Since for each TS session you have to have a TS cal as well as a Client Cal
this means 10 TS users also used 10 client cals. Leaving you only 10 cals
for direct network access. If you were to have all 20 2000 cals used and the
clients were accessing the 2003 server you would need 20 2003 cals where you
only have 15 now.

The TS sessions should be able to map to the 2003 server for file/folder
access from the 2000 server.

Actually the server comes with 5 lic giving me a total of 20. I was hoping
that I could do the reverse of what you are suggesting (have the 2003 be the
DC and let the 2000 be a computer on the domain) or to have the domains
remain separate and merely map the drives on 2003 that I need for the remote
users on the 2000 server. I prefer to do the latter, but I am really looking
to minimize my license effect. The remote users will not always be using the
2000 connection. This is only used for looking up corporate accounting info.
The old way of licensing the server worked just fine with this setup. Now
with User/Device licensing it seems to be less appealing for these types of
users. So far I find the wk3 to be less than appealing for my dollar. That
is too bad.

"Joshua Bolton" wrote:

> Thanks for that clarification.
>
> You can have 2000 remain a DC and have the 2003 server just as a member
> server for file access.
>
> Licensing: you have 20 W2K cals and 10 W2k TS calls. You have added (3) 5
> packs W3K server for 15 '03 cals [unless I am misreading 3 5-cals].
>
> Since for each TS session you have to have a TS cal as well as a Client Cal
> this means 10 TS users also used 10 client cals. Leaving you only 10 cals
> for direct network access. If you were to have all 20 2000 cals used and the
> clients were accessing the 2003 server you would need 20 2003 cals where you
> only have 15 now.
>
> The TS sessions should be able to map to the 2003 server for file/folder
> access from the 2000 server.

How about this:
Can I set the 2000 server DC and add the 3 5-user 2003 adds to the 2000
server (backwards compatibility is possible, right?)?

"David Langschied" wrote:

> Actually the server comes with 5 lic giving me a total of 20. I was hoping
> that I could do the reverse of what you are suggesting (have the 2003 be the
> DC and let the 2000 be a computer on the domain) or to have the domains
> remain separate and merely map the drives on 2003 that I need for the remote
> users on the 2000 server. I prefer to do the latter, but I am really looking
> to minimize my license effect. The remote users will not always be using the
> 2000 connection. This is only used for looking up corporate accounting info.
> The old way of licensing the server worked just fine with this setup. Now
> with User/Device licensing it seems to be less appealing for these types of
> users. So far I find the wk3 to be less than appealing for my dollar. That
> is too bad.
>
> "Joshua Bolton" wrote:
>
> > Thanks for that clarification.
> >
> > You can have 2000 remain a DC and have the 2003 server just as a member
> > server for file access.
> >
> > Licensing: you have 20 W2K cals and 10 W2k TS calls. You have added (3) 5
> > packs W3K server for 15 '03 cals [unless I am misreading 3 5-cals].
> >
> > Since for each TS session you have to have a TS cal as well as a Client Cal
> > this means 10 TS users also used 10 client cals. Leaving you only 10 cals
> > for direct network access. If you were to have all 20 2000 cals used and the
> > clients were accessing the 2003 server you would need 20 2003 cals where you
> > only have 15 now.
> >
> > The TS sessions should be able to map to the 2003 server for file/folder
> > access from the 2000 server.