Products

Evoq Content Overview Content Creation Workflow Asset Management Mobile Responsive Personalization Content Analytics SEO Integrations Security Website PerformanceEvoq Engage Overview Community Management  Dashboard  Analytics  Member Profile Gamification Advocate Marketing Community Engagement  Ideas  Answers  Discussions  Groups  Wikis  Events Mobile ReadyDNN Support PackagesEvoq: CMS FeaturesEvoq OnDemandCompare DNN's CMS Products

Solutions

Content Management SystemMulti-Channel PublishingDigital MarketingOnline Community ManagementIntranet Software SolutionOur CustomersPrime

Resources

Test DrivesSchedule A DemoDocumentation CenterWebinarsWhite PapersProduct ManualsRequest PricingData SheetsCase StudiesEvoq Preferred Products Content Management Ecommerce Forms Identity Management and Authentication Site Management Social Themes

Partners

DNN Partners Partner Directory Become a DNN Partner Partner Program Overview  Hosting  Implementation  ISV  Training  Competencies

Community

Participate Ask a Question Forums Community Showcase DNN MVP  Program Overview  Lifetime MVPs  Honorary MVPs Subscribe to DNN Digest Advisory Groups  Awareness Advisory Group  Developer Advisory Group  Partner Advisory Group  Technology Advisory GroupLearn Documentation Wiki Community Blog Video Library Project History Development RoadmapDownload DNN Store Language Packs Manuals Nightly BuildsSecurity Policies Security Center

Blog

About

News Press Releases News Coverage Press KitCareersContact DNN

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
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Bug in 4.3.6 for sites with custom portBug in 4.3.6 for sites with custom port
Previous
 
Next
New Post
11/27/2006 9:49 AM
 
behnam

Joined: 11/22/2006
Posts: 15

Hi

I have had the above issue and I couldn't bring the page by http://10.0.0.20:8055/DotNetNuke which was a local IP address to our devsrv, Once I put the UsePortNumber key in web config it started to work,

The issue I have now which I am hoping someone can help me here is we can not get the website by the external access through a domain name which is looking at our devserver, I am using   http://test.mydomain.com:8055/DotNetNuke

I have added a new record in PortalAlias with the portalID as Zero and test.mydomain.com:8055/DotNameNuke Alias name with no luck.

Can you please let me know what should I do to make the external link works??

Regards

Behnam

 
 
New Post
11/29/2006 11:49 AM
 
Dan Goldstein

Joined: 4/26/2006
Posts: 6
How did you get it working on Vista RTM?
 
New Post
11/29/2006 12:19 PM
 
behnam

Joined: 11/22/2006
Posts: 15

can someone please help me on this,

Initially the website I installed on port number didn't work. When I added UsePortNumber key in config file the website in local network started to work. but I can not see it externally and I get "Cannot display web page" error message.

DotNetNuke 4.3.6 works with using PotNumber on the local netwrok like http://10.0.0.20:8066/DotNetNuke

but it doesn't work when I use external domain name looking at the same server. like http://www.mydomain.com:8066/DotNetNuke

We do have other websites which we have access externally without any problem.

I have tried to put the domain name into PortalAlias with all different type of combination without any luck

Please help me on this,

Regards

Ben
 
New Post
12/5/2006 12:43 PM
 
behnam

Joined: 11/22/2006
Posts: 15
 

can someone please help me on this,

Initially the website I installed on a port number didn't work. someone kindly helped me and mentioned that I need to add <add key="UsePortNumber" value="True" /> in appsetting of config file.

When I add UsePortNumber key in config file the website in local network started to work. but I can not see it externally and I get Cannot display web page error message.

DotNetNuke 4.3.6 works with using PotNumber on the local netwrok like http://10.0.0.20:8066/DotNetNuke

but it doesn't work when I use expernal domain name looking at the same server. like http://www.mydomain.com:8066/DotNetNuke

We do have other websites which we have access externally with no problem what so ever.

I have tried to put the domain name into PortalAlias table with all different type of combination without any luck.  

Please help me on this,

Regards

Ben
 
New Post
12/5/2006 1:40 PM
 
Geoff Van Brunt

www.dstgroup.com
Joined: 8/23/2004
Posts: 23
If it works internally, but not externally it is most likely a problem with a firewall, dns, or IIS settings.
 
 Page 3 of 5
Previous12345Next 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Bug in 4.3.6 for sites with custom portBug in 4.3.6 for sites with custom port


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