Hi all,

Having spent many hours trying I have installed DNN 5.01.04 on one of our servers (Win 2003). It looks like it's installed OK as on the server I can add a portal and can get to it to login. When I do this the address changes to http://localhost/dotnetnuke and it goes in OK. I added this portal as a parent, though this may be a problem. At this point I get lost and hit the low wall of my knowledge. We have an existing website, let's call it www.domain.com which we host on this server. I don't want this website to disappear but I want to try to "convert" it into DNN so non tech users can make content changes. I have opened up port 81 on the firewall for this website, but it doesn't work.

To access this test portal from outside the local network, I try to enter www.domain.com:81 but this just gives an error. Using the IP address 123.123.123.123:81 also returns an error, but this time a standard HTTP 404 error page. On Firefox this shows the URL has been changed to http://localhost/dotnetnuke. If I try to access a page directly I get different results, using the domain name http://www.domain.com:81/john.htm I get the same error page however 123.123.123.123:81/john.htm returns the page.

My question is how do I get the website displayed rather than it redirecting to localhost? I have been trying all sorts of things in the portal alias fields but nothing is making any difference. Even if I understood it I think this would be difficult, as it is I am finding it impossible.

John

Hi Robert

Many thanks for your prompt reply!

Here's what happened when I tried your suggestions:

1. We have no MS firewall running on the server

2. TCP Port 81 is selected on the website properties page (IIS 6). The internal IP address is specified here; the firewall passes the (IP):81 address to an internal address of 192.168.168.16.

3. I added www.domain.com:81 and http://www.domain.com:81 as portal alias but no difference. I also tried internal and external IP addresses in here (ie 192.168.168.16:81 and 62.8.97.245:81 both with and without leading http:// but sadly no success.

On Firefox each time I try the www.domain.com:81 I get the error page, when I try 62.8.97.245:81 I see the URL changing to http://localhost/dotnetnuke as before.

Regards, John

Hi Robert

I've tried your suggestions, and can report the following:

1) OK

2) I replaced localhost/dotnetnuke in the PortalAlias table with www.domain.com:81

3) I didn't restart IIS as I didn't want to stop other websites but I added a blank line to the start of web.config and saved it which I hope does the same thing?

I'm sorry to report there is no difference from outside the firewall, I'm seeing a "Failed to connect" page in Firefox "The connection was refused when attempting to contact www.marketingunity.com:81."

My previous attempts were with a new portal that I'd added, I'd left the first/default portal alone. This time I removed all portal aliases from the 2nd portal and changed the localhost/.. as recommended, not only does that not work externally but now on the server I am getting "Server Error in '/dotnetnuke' Application." and "

Object reference not set to an instance of an object. "

I think I'll have to go back to localhost/dotnetnuke in the portalalias table to get into dnn on the server again?

Many thanks for bearing with me, I'm sure it's my lack of understanding that has made my do something wrong during setup, or something.

John