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

HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Remote access to DotNetNuke websiteRemote access to DotNetNuke website
Previous
 
Next
New Post
7/28/2006 3:15 PM
 

Kevin - can you give me a little more help?  I think I have the same problem, but can't seem to get the permissions right. 

I have a virtual directory set up under the default web site and pointing to a physical directory on the server.  Under the file permissions, The domain administrators, domain users, and network service all have full control. 

I did not understand the http alias comments.  Add them where?

Thanks in advance.

 
New Post
7/31/2006 8:43 PM
 

Hi aepayne,

If you can run the dot net nuke website locally i.e. http://localhost/<dotNetNuke_website_virtual_directory_name> then it may be a permissions thing.

The http alias can be set in the website settings - log on to the dot net nuke website as admin (that is provided you can access the dot net nuke website locally).  Under the menu item Admin -> Site Settings you will find the section at the very bottom - Http Alias.

For the Http Alias for an intranet environment, that is other computers to see your dot net nuke website on the local network, you will have to add the following http aliases

http://<webserver name where dot net nuke website is hosted>/<dotNetNuke_website_virtual_directory_name>

e.g. http://webserver1/dotnetnuke

http://<webserver ip address where dot net nuke website is hosted>/<dotNetNuke_website_virtual_directory_name>

e.g.http://192.168.0.1/dotnetnuke

I hope this gives you some direction.

 
New Post
8/2/2006 3:34 PM
 

This post has helped and got me a little closer to where I'm trying to go.  I just need a bit more.  It may be a DNS issue at this point.

My DNN setup is probably pretty standard, especially for those hosting their site inhouse.  I'm running DNN 4.3.3.  Hosting it on a IIS 6 server under the Default Web Site.  There are a few other "websites" hosted on this machine (mostly network administration kind of things).  Let's call my website MJDNN.  The MJDNN directory local path is \MJDNN.  The Default Web Site is using all Unassigned IP addresses and the Home Directory of C:\Inetpub\wwwroot

In dotnetnuke admin under Portal Aliases I have localhost/MJDNN, severname/MJDNN, MJDNN.domainname.org, and serverIP/MJDNN

I can browse to it using http://servername/MJDNN and http://serverIP/MJDNN .  I've tried creating a new Host record on my DNS sever for "MJDNN" to point to my server's IP which might work if I could specify a sub-directory. 

What I am looking for is a simpler address http://MJDNN for all my users.  Could someone help me w/ this.  I think this is either a IIS or DNS thing, neither of which I'm an expert w/.

 
New Post
8/2/2006 8:53 PM
 

Im no expert on DNS or IIS, however my understanding is that you will need a computer identifier whether it be an ip address (static or dynamic / internal or external) or a computer name or a human readable url for the user to be directed to a resource on another computer; in this case the dot net nuke website sitting on your web server.

Hence the need for "localhost" when trying to access the web site on the server.  Or in the case where you are not on the server, a client computer on the network (LAN or WAN) you will have to use the web server's computer name or ip address.  Therefore I do not believe there is any way of getting around this.

You may ask when browsing the internet, you can have a domain name http://www.MJDNN.com.  The short answer is that the url is broken down into sub location components used by DNS servers around the world in order to direct your request to the right computer.  Without going into more detail I should probably direct you to a more indepth article I found at http://computer.howstuffworks.com/dns.htm.

The short answer in my opinion is that you will not be able to achieve what you want because you need to direct users to a computer in order to access a resource (the dot net nuke website on the web server).

For any experts out there, I am happy if you are able to prove me wrong; I will have learnt something new.

I hope this helps.

Cheers

 
New Post
8/3/2006 8:53 AM
 

Thanks for the info Kevin.  That does make sense to me.  And, I may very well end up going w/ that (either http://serverIP/MJDNN or http://severname/MJDNN).  I have one more quesiton, for you or any IIS admin out there;

Why, when changing the Local Path of the Default Web Site from C:\Inetpub\wwwroot\ to C:\Inetpub\wwwroot\MJDNN, does my MJDNN virtual directory disapear (in IIS)?  And, when I try and browse to http://serverIP, after changing the default web site's local path to my dnn site, I get a 403 (Forbidden) "you are not authorized to view this page" in IE, and a "Directory Listing Denied" error in FF.  Our general Users group has read and execute permissions on \Inetpub and \wwwroot folders on the web server.

 

 

 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Remote access to DotNetNuke websiteRemote access to DotNetNuke website


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