Installing to a  non-standard port requires that the portal alias be configured with that port.  HTTP runs by default on port 80.  Run it on any other port and the port must be specified in the URL.  If the URL includes it, the portal alias has to as well, otherwise it gets redirected to the default portal alias, without the port and IIS doesn't answer.

If you are having this problem and have not added the portal alias, stop posting until you've added it.  And no, it won't be corrected.  It's not an error.  It's you setting DNN up on a non-standard port.

Jeff

Jeff, I don't know if you've been reading the thread correctly.  I'm expierencing this problem as well.  Let me address my issues:

1) Why on a port other than 80?  Easy, development server technique.  It doesn't matter that it's a non-standar port for published sites.  I'm using it for lan development testing.  Switching to a different port is the easiest way to manage multiple test sites on one server.

2) Have we included the URL (including port) in the portal alias?  Yes - localhost:81 is one of my aliases.  It appears that others on this tread have also done so.

The issue does seem to be that the port is ignored in link building somewhere.  Maybe this could be solved in the core where link building happens, because we can get to the portal aliases manually.  And that's the issue and request from this thread, I believe.  So it is an error because we can't do something in DNN that we could do very simpily with a ground up site.

Ben

Hi Brandon, i tried turning it on but it breaks my site in a different way.

It did not used to be a problem, from the dnn source code:

            If ParsePortNumber Then
                If DomainName.ToString.IndexOf(":") <> -1 Then
                    Dim usePortNumber As Boolean = (Not Request.IsLocal)
                    If Not Utilities.Config.GetSetting("UsePortNumber") Is Nothing Then
                        usePortNumber = Boolean.Parse(Utilities.Config.GetSetting("UsePortNumber"))
                    End If
                    If usePortNumber = False Then
                        DomainName = DomainName.Replace(":" & Request.Url.Port.ToString(), "")
                    End If
                End If
            End If

If you connect to it from localhost, it automaticly is turned on.

But when using friendly url's it bugs in the following way

it adds an extra / behind the webrootpath.

http://localhost:2409/dnn494//testpagian.aspx

that url doesnt work, not even after i added

<RewriterRule>
      <LookFor>http://.*//(.*)</LookFor>
      <SendTo>~/$1</SendTo>
</RewriterRule>

this does not seem to fix the problem.