Funny thing is I've done this before... I've got a fresh, clean install of Windows 2003 Server, SQL 2005 Standard, DotNetNuke 4.9.2 running on said machine.

Created a Host (A) record in DNS on the LAN, added the alias to the newly installed DNN portal, but now I'm getting Under Construction page when I try to hit the portal from another machine on the LAN.  Everything is fine running locally on the new web server, but can't seem to remember where to go from here.  Ugh!  I don't do this enough!

IIS Settings??

TIA,
Chad

---

Chad Voller -- MCP, DNN Aficionado
Leapwise Media
View my

Well, its not too hard i think.

1. Craete a blank database on the sql server of your server
2. Create a new dotnetnuke website using a starter kit
3. Create a Virtual directory in IIS folder and point it to new site you just created using starter kit
4. Close visual studio and open it again
5. go to File- Open-Open website - Open from iis
6. open the virtual directory of your dotnetnuke site
7. change connection string at 2 places (in connection string section and app setting section)
8. Run your project
9. Once you are done with this, everybody in the lan can accesss this site using yourcompname/dnnsitename easily

---

Find out code snippets, tutorials and How Tos' about dotnetnuke at lakhlaniprashant.blogspot.com Umlimited wedding planning tips, free wedding websites and more at http://www.FirstPhera.com an indian dotnetnuke portal dedicated to wedding planning!

BarryS:

if i do a tracert efoidev1.fiberstars.com

I get: 1 <1 ms   <1 ms    <1 ms   web01.fiberstars.com [192.168.1.2]

web01 is the hostname of the server

---

Chad Voller -- MCP, DNN Aficionado
Leapwise Media
View my