This is very confusing from your subscription but my guess is that your forwardign is not actually forwarding the information you think you are. If you log in on the first server how is that information passed to the second server?

You can't use cookies for this and you'll use a session, so really the only way this works is by POSTing to the new domain or passing some sort of information to the second domain so it can verify the user and attach the profile (or wahtever you are tracking on login).

+++ Rick ---

>I have a client that has web site; let's call it alpha.com. Alpha.com is an active site and is the company's main site. The client also has another site registered; let's call it beta.com. When a user goes to beta.com they are forwarded to alpha.com/beta/beta.html, the url is masked so that they don't see the real address. When a user gets to beta.com there is a link to login. When the login is successful they can go to other pages related to beta.com. Here's the problem: Even though the login is successful, the user cannot access the pages because they appear to NOT be logged in. However, if the url used to get to the login page is alpha.com/beta/beta.html everything works correctly. Since the only difference between "it don't work" and "everything is cool" is the forwarding and masking, am I going to be able to do this? If so, how?