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 ...dotnetnuke only run in localhostdotnetnuke only run in localhost
Previous
 
Next
New Post
6/15/2007 6:28 AM
 
can anybody help and assist me, i've already install dotnetnuke, but it only run as a standalone computer (localhost), other computer that connect in network cannot access the portal.
the error message...
quote :

Server Error in '/dotnet' Application.
Runtime Error
Description: An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed remotely (for security reasons). It could, however, be viewed by browsers running on the local server machine.

Details: To enable the details of this specific error message to be viewable on remote machines, please create a tag within a "web.config" configuration file located in the root directory of the current web application. This tag should then have its "mode" attribute set to "Off".










Notes: The current error page you are seeing can be replaced by a custom error page by modifying the "defaultRedirect" attribute of the application's configuration tag to point to a custom error page URL.









thank you for the help.....
 
New Post
6/15/2007 12:10 PM
 

First, I would suggest following the error messages suggestion, and turning customErrors mode to "Off," so that you can see the actual error message.

Without knowing the actual error, the only thought that springs to my head is that you may not have set up a portal alias for [computername]/dotnet, only localhost/dotnet.  You'll need a portal alias for each URL that you want to use to get to the site.  You can add portal aliases by editing a portal in the Host menu under Portals.

Hope it helps,


Brian Dukes
Engage Software
St. Louis, MO
866-907-4002
DNN partner specializing in custom, enterprise DNN development.
 
New Post
6/15/2007 1:17 PM
 

You'll also need to set up your DNS settings to point to the computer that DNN is running on in order for other machines on your network to access the portal.

Paul

 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...dotnetnuke only run in localhostdotnetnuke only run in localhost


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