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 ...Remote Access to DOTNETNUKERemote Access to DOTNETNUKE
Previous
 
Next
New Post
7/20/2006 3:51 PM
 

I have DOTNETNUKE running perfect.

Problem is that I cannot access remotely from Web Browser. I have IIS6 running also which runs fine. Appears the default DotNetnuke install uses port 4685 and I had my network group allow this port but still cannot access. For example http://localhost:4685/dotnetnuke works fine on local box. However, http:/nybcsnmsrpts1/dotnetnuke fails or any combination of adding the port numebr 465 to the URL. Please advise what I am doing wrong!

Thx

 
New Post
7/20/2006 5:30 PM
 

The fact that it is using that port tells me that you installed dotnetnuke in the file system (the default for Visual Studio), and not as an http site. You should install dotnetnuke INSIDE inetpub/wwwroot/dotnetnukefolder, with a virtual directory in IIS pointing to that folder, and when you open a new project to create your dotnetnuke project, it should look something like this:


 
New Post
7/21/2006 3:27 PM
 
Yes, I did try that as well but kept failing. Anyway now I have matched up the IIS6 website Name with DOTNETNUKE and made sure all web.config file matches and built a new web site. At first it did not work (page error). However after about 10 minutes it worked. Assume this was related to Caching problems. I guess I expected it too fast.
 
New Post
7/21/2006 4:22 PM
 
Also my experience (& understanding from some KB articles at WebSecureStores) is that you want to put your site as the main IIS site, not a virtual subdirectory. If you do the latter, I've found you will have to code in the extra directory name when you build a skin (say) and then remove them when publishing your site to the public server.
 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...Remote Access to DOTNETNUKERemote Access to DOTNETNUKE


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