You can buy a license for an Internet solution  that is based on CPU
pricing instead of CAL provided the extranet users are not employees.
Config can be done based on the SPS Extranet white paper:
www.microsoft.com/.../Extranet.asp

Interesting. When I bought Sharepoint in May, they said they didn't offer
server or CPU-based CALs, only CAL's based on users accessing the portal.

Say you have a nice working intranet / workspace, and you want to make a new
workspace that a couple of customers can access through a separate non-SPS
portal that's on the DMZ.

so,

Setup:
----------

Internet <-> firewall <-> DMZ <-> firewall <-> inside network

Sharepoint is on inside network, portal server (Edge's Enportal) is on DMZ,
customer is on Internet.

Question:
--------------

Will running the extranet configuration tool ruin our working intranet?

Follow-on Question:
---------------------------

I can access the workspace from the portal server DMZ machine itself with
http://fqdn/workspace <http://fqdn/workspace> , but putting into a frame
inside the portal server gives a 404 error. Are the proxy settings on
sharepoint global, or per-workspace? Or in other words, can I have an
intranet-enabled workspace without proxy and an extranet-enabled workspace
with proxy (separate portal server)?

Thanx much, and let me know if I'm not wording my question right.

Question about the extranet config tool --

We're up and running [and happy] with our sharepoint  for intranet usage. We
use http://server/wksp <http://server/wksp> all day long and other than
having to restart services every once in a while, everyone logs in with NTLM
authentication and access documents and dashboards just fine.

Now we have a need to allow a couple of non-employees to access a restricted
portion of the portal - specifically, one dashboard and a document folder
from the document library.

Will running the config tool *break* an existing working intranet-enabled
NTLM NetBIOS-accessed workspace?