Vida ~

It's been a while since I looked at this particular behavior... so i may be off base.  But is there an entry in your portal alias for the IP (or name) you are using to access the site from the remote machine?  If I recall correctly, the front page of the host site will show but not work if you're addressing it incorrectly.  That is to say that if someone is able to reach your installation (even incorrectly) we default to a valid page rather than throwing an ASP.Net or other error.  At least, I recall this being true in the past.

Tell us how you are addressing the site ( the url in your browser ) and what is in your PortalAlias settings for the site.

Cheers

Scott Willhite, Co-Founder DNN

leupold,

In light of my last post there, do you still think cookies are the problem?

What settings should I have for cookies? Bearing in mind that I regularly log into dotnetnuke.com ..... would I be able to do that if the cookie settings were wrong?

Thanks

Vida

Those aliases look right.  But Sebastian may also be onto something.  Quite honestly, I don't work much in the virtual directory environment... I work mostly in a server environment so all my sites are real and use FQDNs ( e.g www.site.com ).

An interesting trick you might like to know about is how to fake that behavior for development purposes.  You can actually override settings on your machine so that FQDN's will go where you want them to.  If you take a look at the following file: c:\windows\system32\drivers\etc\hosts (note, no file extenstion... its a text file).  You'll see that localhost is defined for the IP address 127.0.0.1 (an internal address that just circles back to the local machine).  You could add www.microsoft.com and point it at 127.0.0.1 also... and then use that for your local testing ( if you also put it in the portalalias field).

Cheers

Scott Willhite, Co-Founder DNN