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

HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...403 Forbidden!403 Forbidden!
Previous
 
Next
New Post
5/13/2008 11:25 PM
 

Ok, I have added a the portal alias to my site as follows: mydomain.com. No www. or any other character, but when i go to a browser and type mydomain.com i get this:

The page cannot be displayed

Explanation: There is a problem with the page you are trying to reach and it cannot be displayed.

Try the following:

  • Refresh page: Search for the page again by clicking the Refresh button. The timeout may have occurred due to Internet congestion.
  • Check spelling: Check that you typed the Web page address correctly. The address may have been mistyped.
  • Access from a link: If there is a link to the page you are looking for, try accessing the page from that link.

Technical Information (for support personnel)

  • Error Code: 403 Forbidden. The server denied the specified Uniform Resource Locator (URL). Contact the server administrator. (12202)

If i use the www.mydomain.com the site works fine? Any ideas? Any help would be much appreciated.

 
New Post
5/14/2008 3:04 AM
 

make sure, ASP.Net 2.0 or later is installed and default.aspx is configured as standard document in IIS web site configuration.


Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
5/14/2008 8:16 AM
 

Assuming that the DNS is in place for both www.domain.com and domain.com, make sure IIS is configured for both as well.


Tom Kraak
SEO Analyst
R2integrated
 
New Post
5/14/2008 9:30 AM
Accepted Answer 

First guess is that the DNS for domain.com doesn't point to the same IP as www.domain.com and you're hitting another server.  Check the IIS logs for the connection attempt.

Jeff

 
New Post
5/19/2008 12:42 PM
 

turns our this was the issue. Somehow the DNS had been changed to a wrong address. Thanks all for the replies.

 
Previous
 
Next
HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...403 Forbidden!403 Forbidden!


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