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 ...Deploy DotNetNuke to a Server (not localhost)Deploy DotNetNuke to a Server (not localhost)
Previous
 
Next
New Post
11/30/2008 9:52 PM
 

 I would like some help (Please).

I want to deploy the DotNetNuke site that I have built on my PC to the Windows web server on my PC (running Windows XP Pro).

Everything works well at 'http://localhost/dotnetnuke/Home/tabid/36/Default.aspx'

I cannot connect to DotNetNuke from another PC on the LAN using 'http://192.168.0.106/dotnetnuke/Default.aspx'.

I keep getting the Error Message 'Cannot open the page "http://192.168.0.106/dotnetnuke/Default.aspx" because it could not connect to the server "192.168.0.106"

Why can't it connect to the server???

HOWEVER - I can connect to 'http://192.168.0.106' and any HTML files in the server directory (Directory is C:Inetpub/wwwroot) but not in C:Inetpub/wwwroot/DotNetNuke, in particular the "Default.aspx file".

If I introduce an error into the code of 'config.web' I DO get an error message from both the local and networked PC. In other words I can connect to the Windows server. Why not to DotNetNuke????

Thanks in advance

PM

 

 
New Post
11/30/2008 10:58 PM
 

When you set DNN up on the new server, did you add the PortalAlias for 192.168.0.106/dotnetnuke to the PortalAlias table? If not what is likely occuring is that you're hitting the site, but it is redirecting to whatever is in the portal alias table, probably localhost/dotnetnuke.


Chris Hammond
Former DNN Corp Employee, MVP, Core Team Member, Trustee
Christoc.com Software Solutions DotNetNuke Module Development, Upgrades and consulting.
dnnCHAT.com a chat room for DotNetNuke discussions
 
New Post
12/2/2008 1:03 AM
 

What I find interesting is that I am able to access the 'Default.aspx' file in C:\Inetpub\wwwroot\DotNetNuke by duplicating the the line of code in 'web.config' that contains the '<customErrors mode="RemoteOnly" />' thereby creating an error that IS detected and displayed (on the PC trying to connect from the LAN using "http://192.268.0.106/fab_alpa/Default.aspx").

"fab_alpa" is a Virtual Directory that points to "DotNetNuke" as shown above (and it works).

When the error is removed I keep getting the Error Message 'Cannot open the page "http://192.168.0.106/dotnetnuke/Default.aspx" because it could not connect to the server "192.168.0.106". 

Settings in DotNetNuke are: ASP.NET Identy: BOOTCAMP\ASPNET, Host Name: bootcamp, Relative Path: /fab_alpa, Physical Path: C:\Inetpub\wwwroot\DotNetNuke

Where do I edit the "portal alias"?

As you probably realize, this is very frustrating.

Thanks

 
New Post
12/2/2008 1:10 AM
 

In the database there is a portal alias table, add an entry in there for your new alias.


Chris Hammond
Former DNN Corp Employee, MVP, Core Team Member, Trustee
Christoc.com Software Solutions DotNetNuke Module Development, Upgrades and consulting.
dnnCHAT.com a chat room for DotNetNuke discussions
 
New Post
12/2/2008 3:35 AM
 

OK. I'm in business.
I had to create a new Virtual Directory 'fab' as the database would not accept 'fab_alpa'. It doesn't like the underscore between the 'fab' and 'alpa'. I then created a second portal (192.168.0.106/fab) by logging in as 'host' and selecting 'Portals' under the 'Host Tab'.

Thanks for your help Chris. This has been a great learning experience and now I can get some sleep.

Peter

 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Deploy DotNetNuke to a Server (not localhost)Deploy DotNetNuke to a Server (not 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