Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

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

HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...Trouble with HTTP AliasTrouble with HTTP Alias
Previous
 
Next
New Post
9/7/2006 4:49 PM
 
Hello everyone,

I'm running DNN 4.3.4 on Windows 2003 Server with IIS 6 and SQLExpress.

I've sucessfully installed the site on port 81 and can browse it on the web server, now I'm trying to get a registered domain to call up the site.  I am using DynDNS to keep pack525.org pointed to the dynamic IP of my cable modem, and a WebHop entry to redirect it to http://pack525.org:81.  I have my DLINK router forwarding port 81 to 192.168.1.253 (the web server). 

As the host user, I have added these HTTP Alias to my portal:

localhost/pack525
pack525.org
192.168.1.253:81
192.168.1.253/pack525
68.201.229.160:81
pack525.org/
pack525.org:81/

My Problem

1. From my laptop connected to the same LAN as the web server, http://192.168.1.253:81 successfully brings up my portal.

2. From my laptop connected to the same LAN as the web server, http://68.201.229.160:81 successfully brings up my portal (68.201.229.160 is the current dynamic IP of my cable modem).

3. From my laptop connected to the same LAN as the web server, http://pack525.org results in an error:
     Unable to connect - Firefox can't establish a connection to the server at pack525.org:81.

Is there something I am missing here to successfully get the domain URL to connect to the portal?

Best Regards,
Tracy



 
New Post
9/8/2006 10:55 AM
 

 

Try removing those ending slashes on the pack525.org aliases.


DotNetNuke Modules from Snapsis.com
 
New Post
9/8/2006 12:57 PM
 

Thanks John!  That did the trick! You rock.

My alias list now looks like this:

pack525.org:81
www.pack525.org
 
New Post
9/9/2006 11:59 AM
 

 

Excellent, glad I could help.


DotNetNuke Modules from Snapsis.com
 
New Post
9/25/2006 2:58 PM
 
I'm now putting up another DNN site, and it seems I haven't learned HTTP alias as well as I thought.  At least, I think my trouble is HTTP alias again. Same environment as before (I'm running DNN 4.3.4 on Windows 2003 Server with IIS 6 and SQLExpress.) but this web site is on port 82.

  1. The site runs properly on the host when I go to http://localhost:82
  2. I configured DynDNS (dynamic DNS) just as before, here is the summary:[HOSTS]
    wilcrestarearunners.org   63.208.196.110   (Webhop, the port redirect server)
    www2.wilcrestarearunners.org   68.201.219.130   (my cable modem public IP)

    [CNAMES]
    www.wilcrestarearunners.org (aliased to) wilcrestarearunners.org

    [WEBHOPS (redirects)]
    wilcrestarearunners.org   (aliased to) http://www2.wilcrestarearunners.org:82/
  3. It seems that this DNS configuration is working properly, because I can use Ethereal to see traffic coming into the server on my LAN on port 82.
  4. HOWEVER, the DNN site does not come up, even though I know it is running on port 82!
How do I know what value to use for an HTTP alias? As you can see by the redirect, I would think www2.wilcrestarearunners.org is the right value. But, I've tried every combination I can think of.  Is there a log somewhere that says "a request was made for the default page of this DNN site on port 82, but I rejected it because the alias xyz.com is not defined...".

Best Regards,
Tracy

 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...Trouble with HTTP AliasTrouble with HTTP Alias


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:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. 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.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out