As we have our main web page running off of our main web server, if we develop any DNN portals locally we will have to move them for other users to be able to use them. We have two portals which are the basis of a new intranet and will be developed further, we have saved both portals as templates and planned to create new portals using both templates on our web server version of DNN.

Having logged into the webserver DNN which runs our company website, we went into HOST>Portals and then Add New Portals and used the Templates we created. Where we may be going wrong (apart from is this the right way to do this in the first place?) is with the Alias and Home Directory. We set up two new Virtual Directories both pointing to the same Folder as our original website and let DNN select the home folder by defaut.

We then get an error relating to SMTP and our email but confirms the website is created. When we try to access it it says the website requires a login and it simply does not connect at all.

Are we going about this the right way and if so where are we going wrong? All we want to do is to develop the Portals locally and then move them up on to the DNN Folder on our web server so that they can come part of the DNN environment for everyone to use.

Thanks for your reply John. I have set up a new website alias for my parent portal on the web server. DNN have acknowledged that the portal has been created with Verification Code: 3-1641. However, the website comes up unavailable with the standard IE reasons for it being so, ie: DNS not available etc.. What am I missing as I really need to make this new portal available today.