We've struggled through alternate access mappings (AAM) once before on a single server farm but we should take a look at the multi-server farm approach.  I'm not sure I have a complete grip on the topic but I've gotten some sense that I'm getting it correct.

You'll recall we have a total of four web apps:

Central Admin runs on MyWFEServer:63999
Portal runs on MyWFEServer and MySSPServer using a host header Portal.
SSP runs on MyWFEServer and MySSPServer using a host header SSP.
MySite runs on MyWFEServer and MySSPServer using a host header MySite.

The two servers and the DB server run in a domain called MyDomain.Local.  The MyDomain.Local DNS server includes A records that point all three, Portal, SSP and MySite, to the IP address of my WFE server.  MyDomain.Local is piped to the internet using the MyDomain.MyCompany.net URL.

So, there's a fourth computer in the domain that I can log onto and open a browser and point to http://Portal and, since I built the portal using the Enterprise Collaboration template, I see the dorks.  I can also point to http://MySite and I'll get my site except that my administrator has not yet allowed self-service site creation. 

http://SSP still has me a bit confused because I get a 404 unless I browse to http://SSP/SSP/Admin.

Still, all three work. 

So I go to Central Admin and click on Alternate Access Mappings and then Edit Public URLs.  Here, I select my MySite mapping collection and I enter the following:

Default: http://MySite
Intranet: http://MySite.MyDomain.Local
Internet: http://MySite.MyDomain.MyCompany.net

This is where it's cool to have not stolen your IIS default web site for your portal app.  When I created my web apps for my SSP, MySite and Portal, I did not use the Default Web site.  That site still runs and still displays the Under Construction page when you browse to the server.  I have to have either hosts file or DNS support for my host headers and those host headers have to included on the dialog box you get when you click on the Advanced button on the Web Site tab of the web site's Properies in IIS. 

So, in DNS, MySite is the same as MySite.MyDomain.Local and it points to my WFE server's IP address.  The Host Header on my MySite web site in IIS tells my WFE server: "When you get a requrest on Port 80 and the host header is MySite send it to the MySite web site."

Now, when I browse to http://MySite, I get MySite but when I browse to http://MySite.MyDomain.Local, I get Under Construction.  Perfect.  What's happening is the DNS is sending me to the correct IP address but IIS fumbles the host header.  So I add the MySite.MyDomain.Local as a host header using the advanced button on the web site tab of the MySite web site properties.  I reset IIS and try again and...

I get the error that says "Your administrator has not allowed for self-sevice site creation"  Which is both perfect and perfectly unacceptable.

All I have left is the internet settings and this is a DNS issue for the DNS server that supports MyDomain.MyCompany.net.  Those are other cats and they need a help ticket so I'll have to wait for that.  But I"ll also have to add the new host header to the web sites.

This will leave me with just four issues:

1. The http://ssp/ssp/admin thing is silly.  I should just be able to browse to http://ssp and land on http://ssp/admin.
2. When I add the host headers, I have to do it individually to each of my WFE servers.
3. I'll have to get on that Admin guy about the self service site creation.
4. The dorks, I really need to figure out how to get them off my portal BEFORE I install it.

Thanks for reading along.

-robot

ps. you know Microsoft has a friend of mine pimping for Server 2008.  I'll have to get that ad and show you.