Sorry it took me so long to get back. A bit of training for the staff seemed necessary to my boss. After a lot of tinkering in apache, I got it to work. Part of my problem with the tinkering was only setting up rudimentary virtual hosts in the past with apache. Once I dug my mind into the docs I have, everything was fine.

If you don't want to use the frame reference (which I'd recommend because it's actually much simpler, and who knows just what problems this could cause since I'm working in an office between two machines and not in a production environment), you can try it this way. I just wouldn't recommend it in a production environment.

Okay, first of all, handle all redirection with IP adresses. This will usually counter any problems with hitting the DNS server first and having it get confused between the real server (A) and the one masquerading as the real server (B).

If both servers were running apache, this wouldn't be an issue since you could just use Alias rather than Redirect, but unfortunately, that's not the case.

Once you have the virtual host setup in Apache's httpd.conf, and restart the server, test the simple redirection on IIS to the ip. It should do it correctly and still have the correct information in the location bar. If the user clicks reload, though, it will return them to the original server and then process the redirection again.

If you want to maintain the /webapps directory structure in the web code, make sure that you create the webapps directory under the home. Then you can redirect any access to the home directory back to the IIS server (using IP addresses to avoid the DNS database confusion).

Like I said, though. You should really go the frames direction because then you can redirect frames to whatever server migration may come along in the future. Jumping through these hoops may only lead to future dilemmas.

I must say, though, it was a fun problem for me to play with, though.