OK,

In my case I'm setting up a "forums.mydomain.com" format.  I've been working directly on the server (which I physically control). 

So, I set up an FTP login to the IP.  Next I tried doing a remote setup and choosing the FTP option -- but it kept dying with various cryptic errors.  Then I thought, well, I suppose I could remote desktop to the server, and run the install locally -- and FTP instead of picking local file.  Seemed silly to FTP to the same machine I was working on, but, hey....

It worked.   No localhost problem.

I strongly suggest adding something about this in the installation instructions.

-pfs

hi there!

Unfortunately, I'm not very savvy on all this...but I will try to help if i can!
First off...when I perfomed my 4.4.1 install, I followed not only the DNN Install guide..but also this post
http://forums.asp.net/1123229/ShowPost.aspx (which was EXTREMELY helpful!! )

Now, you noted your live server is running IIS5/Win 2k, from reading all the install notes, I think you
want to grant the ASPNET account full control, NOT the Network Service acct...
Now, my ASPNET acct didn't show when I clicked the security tab of the
IIS DotNetNuke4 folder.  I had to click the add button on the security tab,
and find the ASPNET acct....and add it that way...not sure if that's your prob too.

Now, according to the referenced forum link above...

If you named your install folder soemthing other than DotNetNuke_2 then you will
want to change the reference to the folder name in the DotNetNuke.sln file, this file
is located in your DNN folder you created on your server.
In your case, Im not sure if you also will need the full path to your DNN folder if it
resides on a different drive..(d)

Then it seems you need to rebuild your source...so run the sln file
Or, if your using Visual Studio...there is a build option (again refer to referenced post link above)

give that a whirl...good luck.

J-

You can remove the DotNetNuke portion of the URL by using the HostHeader application setting (Web.confg under AppSettings)

As for testing purposes, if you are worried about testing locally using your URL, you could modify your hosts file to have you local machine direct www.mytestdnn.com to localhost, keeping in mind that you wouldn't be able to access the actual site with the value specified in your hosts file.

 

---

-Mitchel Sellers
Microsoft MVP, ASPInsider, DNN MVP
CEO/Director of Development - IowaComputerGurus Inc.


Visit mitchelsellers.com for my mostly DNN Blog and support forum.

Visit IowaComputerGurus.com for free DNN Modules, DNN Performance Tips, DNN Consulting Quotes, and DNN Technical Support Services