I've asked this question on the Microsoft DNN forum and have gotten no response, so I thought here might work better...

I have a brand new installation of 4.3.1 (the problem exists with 4.0.x as well).  I have two portal aliases, one for localhost\mysite and one for servername\mysite (this is an intranet site).  If I go to the localhost version, I can log in fine.  If I go to the servername instance, I can put in my username and password (for host, or any account) and after clicking login, it re-directs back to the home page and does not log me in.

If I deploy this EXACT website to a public www address, it works fine.  Anyone got any clues why it would work on an Internet site, but not an Intranet site?

Kevon

Thank you for your quick reply, but I don't think I quite understand.

If I walk over to the server that the site is installed on, and I put http://localhost/portal in the browser, it works.

If I go to any other machine on the network and type in http://servername/portal it does not work (IE, the site comes up, displays, navigates, but does not allow any user to become authenticated)

How is that an IIS issue?  How can I resolve it if it is?

Kevon

Going on the assumption that it is an IIS issue, I re-installed IIS.  I re-installed DNN.  Still the same issue.  I then installed DNN as the default web so it works as either http://localhost or http://servername.  Same issue. 

Really need input..

Kevon