I set up a virtual application in IIS so that I can access my DNN sites through localhost/DNNSite, no problem there. The problem is when I try and access the site from another computer in the network. I should be able to access the site through the web browser by typing in //DNNServer/DNNSite, where dnnserver is the pc with IIS installed and the site on it, and dnnsite is the site name, but I keep getting a page not found error when I try and do this.
I set up several other test sites with seperate IIS applications(same settings) to troubleshoot this issue. As an FYI when I say "installed/configured" I am refferring to the proccess where you select "automatic" from the dot net nuke insallation wizard the first time you open the site up. Anyway, the first test site is another DNN site that has been installed/configured but is a blank site and I am not able to access that from within the network, only the local pc it is on. The second test site is a DNN site that has not been installed/configured and I am able to access that from within the network. The third test site is just an HTML site and I can access it from within the network.
I changed the physical location of the virtual application in IIS that was working to my site to see if it was the settings in IIS, and my site was still not able to be accessed from within the network. Since this did not work and other sites do work, like the html site and the dnn site that has not been configured, I am assuming that there are settings in DNN that I am unaware of that need to be changed.
Are there any settings in DNN that I am overlooking that would prevent me from viewing the site from within the network or could it be something else altogether?
Thank you in advance.
-Austin