DotNetNuke works on localhost but cannot make available to publi

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

Home All Forums

Home

Using DNN Platf...

Administration ...

DotNetNuke works on localhost but cannot make available to public

7/27/2007 5:00 AM

Eleanor

Joined: 5/2/2007

Posts: 4

DotNetNuke works on localhost but cannot make available to public

Hello,

1st of all I am new to DNN but experienced with IIS. I tried to find a solution for my problem and only found 1 threat on a website with the same problem:

http://forums.asp.net/p/873640/884751.aspx

I also downloaded the documentation package but couldn't find this issue in it.

At this moment the DNN portal works on my local win2003 server. I can reach it by http://localhost:1276/website , (former it worked as http://localhost/website but since a short time I have to add the port?)

But from other PC's from my LAN I try to contact either http://10.105.0.9/website OR http://10.105.0.9:1276/website and it says "Website cannot be found"

So as the other threat says you have to add more portals to make it work. Now I added:

(router internal IP)   10.105.0.1:1276/website
(router internal IP)   10.105.0.1/website
(router external IP)   82.174.x.x.:1276/website
(router external IP)   82.174.x.x./website
(localhostname)        server01:1276/website
(localhostname)        server01/website

Either from LAN nor Public still don't work. Where do I go wrong?

7/27/2007 10:04 AM

Mitchel Sellers

www.mitchelsellers.com
Joined: 1/24/2007

Posts: 7846

Re: DotNetNuke works on localhost but cannot make available to public

You will need to have a portal alias for each url/ip that will be accessing the site.

Also, regarding the port number if you have the "use port number" option specified in your web.config then you will need the port number.

-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

7/31/2007 6:16 AM

Eleanor

Joined: 5/2/2007

Posts: 4

Re: DotNetNuke works on localhost but cannot make available to public

Thank you for your respons. I allready tried to make some alias but it didnt help. The alias that was allready in there by default is localhost/website

What do I need to add in this case as alias to acces it from my LAN? The IP of the server? Then it would be alias: 10.105.0.9/website, but that doesnt make it accesable from my other client. I also tried all other IP's I use but doesnt give any result.

7/31/2007 9:11 AM

sean theriot

MGMindustries.com
Joined: 3/14/2005

Posts: 11

Re: DotNetNuke works on localhost but cannot make available to public

x.x.x.x/folder should be set for the portal alias. You can do this in DotNetNuke itself if you already have access to the site or you can do this manually in the database by inserting a new row into your xxx_PortalAlias table. Here is an example of the sql used to do this. e.g. INSERT INTO xxx_PortalAlias VALUES ('0','10.105.0.9/website'). The xxx may be unique prefix that you may have chosen when you setup DotNetNuke. The '0' is The PortalID (Assuming that it is 0), The PortalAliasID is automatically generated for you, and of course you have your HTTPAlias ('10.105.0.9/website').
You can have multiple HTTPAlias for one PortalID. This means you can try multiple PortalAliases at the same time. If your port alias is set correctly then check your firewall settings. Also your IIS Permissions may be giving you a problem. Hope this is some help.

8/1/2007 8:22 AM

Eleanor

Joined: 5/2/2007

Posts: 4

Re: DotNetNuke works on localhost but cannot make available to public

Hello, thanks you for your respons. As stated before I tried to get the alias working. At the moment it looks like this:

http://img174.imageshack.us/my.php?image=alias1ru5.gif I think it's ok.

The IP adress is the IP of my webserver. I added the alias in the DNN interface since I have host acces. It is not working from other clients on my LAN so I dont even bother checking if the port forwarding is ok on my router (thats the next step).

I have adjusted the security settings on the website directory and added the ASP.NET and NETWORK SERVICE account with full control. So as written in the manual that should be ok.

When adding the site in IIS I also made sure that read/execute of scripts is turned on.

Greetings

Page 1 of 2

Home

Using DNN Platf...

Administration ...

DotNetNuke works on localhost but cannot make available to public

These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
No Flaming or Trolling.
No Profanity, Racism, or Prejudice.
Site Moderators have the final word on approving / removing a thread or post or comment.
English language posting only, please.

Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

DNN Corp. (DotNetNuke)