具有内部IP的DNN门户别名 [英] DNN portal alias with internal IP
问题描述
我无法弄清楚是否可以/如何使用内部网络服务器设置来使用多个DNN门户进行测试。我是DotNetNuke的新手，所以我不确定我想做的事是否可行。
我的服务器的IP地址为192.168.15.16。我已经用该IP的门户别名设置了主要门户。该站点工作正常。但是然后我还有其他几个站点（分别称为A和B）进行配置。
我想导航到192.168.15.16/A和192.168.15.16 / B查看这些站点。这些的门户别名似乎并没有减少。我收到404错误，我相信这是因为IIS在物理路径上添加了A或B（不存在）。
是否可以进行设置？也许我需要在IIS中进行更改？也许我会以错误的方式进行操作？谢谢！
1）在需要访问测试站点的任何计算机上，编辑C：\Windows\System32 驱动程序等主机包括：
192.168.15.16 A
192.168.15.16 B
2）将站点A的门户网站别名设置为 A
3）设置网站B的门户别名为 B
5）通过 http：// B /
6）编辑IIS站点的绑定，以包括 B和 A主机头
注意
- 如果您有本地域控制器，则可以告诉它将 A和 B解析为正确的IP。
- 我在我们的开发机上使用了相同的方法，但是我尚未在同一DNN安装中包括多个门户。我认为这会起作用。
I'm having trouble figuring out if/how I can an internal webserver setup for testing with mutliple DNN portals. I'm pretty new to DotNetNuke, so I'm not sure if what I want to do is even possible.
My server is at an IP of 192.168.15.16. I have the main portal set up with a portal alias of this IP. That site works fine. But then I have a couple other sites (lets call them A and B) to configure.
I'd like to navigate to 192.168.15.16/A and 192.168.15.16/B to view these sites. Portal aliases to these don't seem to cut it. I get a 404 error and I believe it's because IIS adds A or B to the physical path, which doesn't exist.
Is there a way to set this up? Maybe something I need to change in IIS? Maybe I'm going about it the wrong way? Thanks!
1) On any machine that you need to access the test sites, Edit C:\Windows\System32\drivers\etc\hosts to include:
192.168.15.16 A
192.168.15.16 B
2) Set the portal alias of site A to "A"
3) Set the portal alias of site B to "B"
4) Access site A via http://A/
5) Access site B via http://B/
6) Edit the bindings of your IIS Site to include "B" and "A" host headers
Notes
- If you have a local domain controller, you can probably tell it to resolve "A" and "B" to the proper IP.
- I use this same method on our dev machines, but I've yet to include multiple portals on the same DNN installation. I am assuming this will work.
这篇关于具有内部IP的DNN门户别名的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
