Hi,

I am looking to install a server that will offer web and ftp services.
For failover, I would like to use Windows 2003 Server Standard because
I will have three other identical servers performing other tasks which
could be swapped with the 'web server' in case of a problem. I don't
want to use Web Edition for that reason and because it doesn't appear
to offer XML.

I will need initally secure login's for both services but hope to host
our internet domain site at some point. What I really want to know is
about licencing. I understand that casual surfers could access the
server via the Anonymous account, but would I have to have a Windows
2003 CAL for each user I want to authenticate, e.g.:

Customer A is allowed specific access to a directory which is blocked
from public access. Customer B wants to be able to read and write FTP
files into a protected directory which has no public access. Do I need
a Windows CAL for Customer A and B.

I think I've just answered my own question but no harm in making sure...

Also reading an earlier post, if the server is in a DMZ, i assume I
need 1 CAl to access the server from the LAN:

LAN - FW - DMZ - FW - Internet

Would a future exchange server go into the DMZ as well especially if I
will have users connecting via VPN and Terminal Services?

Thanks or any help,

IC

--
IC

Since I posted the DMZ reply that you quoted, I thought I should try to
answer this one for you, too!

1. Customers A and B should have separate CALs (as I understand licensing
requirements). As I just wrote in another thread: "Remember to work with
your OEM, Retailer, VAR or Microsoft Account team to resolve licensing
discrepancies."

2. Servers in the DMZ should require one (1) CAL per unique authenticated
user connecting to it. (see licensing disclaimer above ;-> )

3. Your Exchange server could go in your internal LAN and you would then
allow access to it over specific ports from your VPN / TS servers.

LAN -------- FW/ISA --------- DMZ --------- FW/ISA ------- INTERNET
| EXCH. | | VPN / TS |


Hope this is helpful!

--
Ryan Sokolowski
MCSE, CCNA, CCDA, BCFP
Microsoft Enterprise Engineering Center

"A troubleshooter's best tool is the Event Viewer and understanding the
events and messages contained therein."

This posting is provided "AS IS" with no warranties, and confers no rights.

"Ictop" <ictop@potci.org> wrote in message
news:111020042309178979%ictop@potci.org...