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 ...Cannot access DNN from another computer with IP/computername. Always resolved to localhost. Cannot access DNN from another computer with IP/computername. Always resolved to localhost.
Previous
 
Next
New Post
2/25/2009 5:58 AM
 

I installed a DotNetNuke 5 on an IIS 6 development server using a remote desktop. On the remote machine I can browse the website, but as the IP adress or computername is always resolved to 'localhost' i can ONLY browse the website on the virtual machine, but everywhere else in the network an error is produced (of course, as on the other computers there is no localhost running).

But I found that both on the remote machine and any other client computer only http://ip-adress/ will result in an "under construction" page, but the IP adress ist not resolved to localhost. Furthermore, trying http://ip-adresss/DotNetNuke/admin will also not resolve to localhost but simply show a "Directory Listing not allowed".
So could it be the configuration of the /DotNetNuke?

Ping to the IP works fine.

On the remote machine:
- http://localhost/DotNetNuke --> works fine
- http://ip-adress/DotNetNuke --> http://localhost/DotNetNuke --> works fine
- http://ip-adress/ --> under construction page
- http://localhost/ --> under construction page
- http://ip-adresss/DotNetNuke/admin --> Directory Listing denied

On any other computer:
- http://ip-adress/DotNetNuke --> http://localhost/DotNetNuke --> cannot work as there is not server running on localhost
- http://ip-adress/ --> under construction page
- http://ip-adresss/DotNetNuke/admin --> Directory Listing denied

 
New Post
2/25/2009 7:17 AM
 

If I understand your question correctly: check your portal alias. This may be the issue.

If you are browsing to an IP address you may also need a port number assigned in IIS.

e.g.:  192.168.0.150:8090

this would then be your portal alias.

 


 
New Post
2/25/2009 8:21 AM
 

First of all: Thanks you so much, that was the solution for my problem :-) At least now we can access the site from other computers. Anyways, now a new issue appeared: on every computer we now get a prompt for username and password. Although I can simply use the login which I also use to access the remote desktop to my development server, then these user details will be used for DotNetNuke too (as we are using AD). So this is not a good way to test how AD works with our other users. Before we go live we of course have to test if every user can access our site from his computer with his AD details (and if the roles etc. are correct).

 
New Post
2/25/2009 10:57 AM
 

Is Windows authentication enabled in IIS?  Is this site in your intranet zone so the browser will pass credentials?

Jeff

 
New Post
3/1/2009 9:16 PM
 

Hi Jeff, regarding the Windows authentication I attached a screen from our IIS configuration. The "Integrated Windows authentication" is what we you mean, right?

After putting the site in the intranet zone now I can access without being prompted for a login, but it does not seem that user credentials are passed as I cannot see my AD user in the user account list of DNN. Furthermore I would like to know if there isn't a more convenient (automatic, central) solution, or do we really have to manually add the domain to the intranet zone on every employee computer (which would be 300+ computers to do)...

 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Cannot access DNN from another computer with IP/computername. Always resolved to localhost. Cannot access DNN from another computer with IP/computername. Always resolved to 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.

Copyright 2014 by DNN Corp | Terms of Use | Privacy | Design by Parker Moore Design