Thanks Seeflat.
SPServer1 is going to stay on as our Internal-access server, while SPServer2 is going to be the external access server.
Beyond instructing internal users to hit http://spserver1.company.c
Main Topics
Browse All TopicsIn our original MOSS 2007 farm (SPServer1 and SQLServer), used http://www.codeproject.com
In the second part of our test, we installed MOSS 2007 to a new server (SPServer2) that'll serve as our new test of external Forms Auth. We connected it to the original Farm.
All IIS and file data appear to have been copied over, minus our customizations (from the codeproject article) to the web.configs. We readded the codeproject customizations. When we log in to http://SPserver2/login.asp
Another weird thing is that when we log out of the network and try to hit the SPServer2 site we're prompted for an AD login, even though we have the forms authorization set up.
Sorry the question is kind of sprawling. If there's a good article that describes a similar process (moving an external Forms Auth site to a new server on the Farm) I'd be willing to read and award.
Thanks.
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
Thanks Seeflat.
SPServer1 is going to stay on as our Internal-access server, while SPServer2 is going to be the external access server.
Beyond instructing internal users to hit http://spserver1.company.c
You are right with respect to aliases... However it seems to me that is the problem you are having... http://spserver2 is redirecting to http://spserver1. This tells me an AAM needs to be added, because as far as SharePoint is concerned, it only answers to http://spserver1.
Try adding spserver2 to the AAMs and see if that doesn't help.
That was it. I was having a conceptual problem with the farm that was tripping me up.
I think the first thing I had to realize is that the SP farm means that the site exists on multiple servers, but the DNS can be set to point to the site on one server.
Step 1: configure your dns to point to the 80 site on each server with a specific name, eg: SPSERVER1's 80 site is internal,company.com, SPSERVER2's 80 site is external.company.com.
2: In IIS, I modified the ports and host headers on each server, so SPSERVER1's IIS site's port and host header points to the 80 site and internal.company.com, and the SPSERVER2's IIS 44444 site is set up in IIS as a port 80 site with a host header of external.company.com.
3. Set up the AAM and I was good to go.
It's kinda tricky. I still feel like I only 90% get it, but it works.
Business Accounts
Answer for Membership
by: seeflatPosted on 2008-07-31 at 17:17:00ID: 22134611
So is SPServer1 removed from the mix completely? Or do you expect some users to hit SPServer1 and some users to hit SPServer2?
How do external users get routed to the portal? How do external users get routed to SPServer2 instead of SPServer2? Are you using ISA or anything?