I need some help here :(

I am having problems accessing the newly installed DotNetNuke ver 4.5.1 on the FQDN. On the local machine, whenever I typed the FQDN, the link will automatically linked to http://localhost.

On the LAN on a separate machine, using either the FQDN or short name will not work.  But using the alias to route to the portal I have created earlier, there is no problem.  E.g.

Not Working Link:
http://<FQDN hostname>/ssc/default.aspx
http://<Short hostname>/SSC/Default.aspx

Working Link:
http://<short Hostname>/SSC/Default.aspx?alias=<short Hostname>/ssc/portalA

Can anyone tell me what went wrong? I followed the procedures and on the local web server hosting this, there are no issues at all.  I can add, create, delete etc.  But when I tried to access via another machine it is not working. For testing, I created an index.html and using the FQDN, the page was shown successfully from a remote machine:-

http://<FQDN hostname>/ssc/index.html

Any tinkle?

 

I have the exact same problem.  It would seem I am missing something simple but I didn't have this problem with earlier DNN installs.   I wonder if it is because I didn't use \dotnetnuke as the install directory?

One thing that leads to questions is the following

Files within your portal are actually stored within the /Portals/0/ folder, where 0 is the id of your portal.  If you will be moving between servers you can use links like /Portals/0/yourfolder/yourfile to link to files and folders for the specific portal.

---

-Mitchel Sellers
Microsoft MVP, ASPInsider, DNN MVP
CEO/Director of Development - IowaComputerGurus Inc.


Visit mitchelsellers.com for my mostly DNN Blog and support forum.

Visit IowaComputerGurus.com for free DNN Modules, DNN Performance Tips, DNN Consulting Quotes, and DNN Technical Support Services