Neeeevermind. I got it. Somehow, I had some strange data in my PortalAliases table that was redirecting me all over the place. I deleted the database and reinstalled, and now things seem to be working fine.

D'oh!

-John

Ok, If this is the wrong place, I apologize in advance. 

I've been working with DNN for about 18 hrs now.  I think I'm still a newbie .  I am having the same problem.  NukeAlexS's solution works fine when you're using the local IIS server.  My problem and I suspect the original author's problem is that I created the DNN 4.3.3 website as a file system.  I used the Startup kit with VS 2005-Pro.  When I built and ran the website for the first time (installation), DNN installed itself at localhost:1269\foobar.  Once you close the project or restart VS and try to run the website again, VS randomly picks a different port to use.  The alias now points to a server port that doesn't exist anymore.  I don't know if I should be tweaking a setting in DNN to tell it not to redirect or if there is a what to tell VS 2005-pro to use the same port over and over.

I've never cared about what port my site was running off of before so this is completely new to me for DNN.   Does anyone know how I should handle this when I prepare for production deployment?

I'm trying to write a few new modules and this problem has me stuck.

Thanks