Exactly. On Sat, Aug 20, 2011 at 10:55 AM, Katherine Moss <[email protected]>wrote:
> Oh. Because CCNet is ASP.net for the dashboard, right?**** > > ** ** > > *From:* [email protected] [mailto:[email protected]] *On > Behalf Of *Michael Powell > *Sent:* Saturday, August 20, 2011 12:53 PM > > *To:* [email protected] > *Subject:* Re: [ccnet-user] Re: CC.NET 1.6 install on Windows 7 Pro / IIS > 7.5**** > > ** ** > > It requires the aspdotnet_module, but yes, it's doable as far as I can > determine.**** > > On Sat, Aug 20, 2011 at 10:49 AM, Katherine Moss < > [email protected]> wrote:**** > > Can you set up CCNet via apache? I didn’t know that. **** > > **** > > *From:* [email protected] [mailto:[email protected]] *On > Behalf Of *Michael Powell > *Sent:* Saturday, August 20, 2011 10:14 AM**** > > > *To:* [email protected]**** > > *Subject:* Re: [ccnet-user] Re: CC.NET 1.6 install on Windows 7 Pro / IIS > 7.5**** > > **** > > I will look into this. > > Actually, I did a little digging and I think I may just set it up through > our Apache server and call it done. That seems to work just fine and we'll > only need to maintain one web server instead of two.**** > > On Fri, Aug 19, 2011 at 9:13 PM, HowitZer <[email protected]> wrote:*** > * > > Open up inbound port 80 tcp on the IIS machine.**** > > > On Aug 19, 7:19 pm, Michael Powell <[email protected]> wrote: > > The closest I can come up with at this point is that Apache is not > > forwarding ports to IIS, even though I've configured Apache and the other > > web service to route through ports other than the one IIS is expecting. > >**** > > > On Fri, Aug 19, 2011 at 1:05 PM, Michael Powell <[email protected] > >wrote:**** > > > > > > > > > > > > > > > > > > See my other reply. > > > > > Okay, not quite out of the woods yet. > >**** > > > > I am able to visithttp://localhost/and see my dashboard just fine.**** > > > > Projects refresh okay, I can browse around no problem. > > > > > However, other computers on our network cannot see the same machine > when we**** > > > > browse tohttp://machinename/.**** > > > > > > I don't know why, perhaps a port blocking issue somewhere in the > network? > > > I've opened port 21234 on the local box which I believe is the default. > > > > > The funny part is that other web-based applications can see things just > > > fine running through our Apache server hosted on the same machine. For > > > instance,http://machinename:1234/. > > > > > Any thoughts? Perhaps there is another router in the network I don't > know > > > about that is otherwise blocking the same port 21234? > >**** > > > > On Fri, Aug 19, 2011 at 11:36 AM, Michael Powell <[email protected] > >wrote:**** > > > > > >> Okay, webdashboard did NOT install in Windows 7 Pro under IIS 7.5. > > > > >> Is there a process for install this manually that will work? > >**** > > > >> On Fri, Aug 19, 2011 at 11:28 AM, Michael Powell < > [email protected]>wrote:**** > > > > > >>> I installed CC.NET on a Windows 7 Pro machine running IIS 7.5 > (although > > >>> we had to install IIS afterwards, which may be part of the problem). > > > > >>> I am having trouble setting up CC.NET webdashboard through a manual > IIS > > >>> Admin process in this configuration. > > > > >>> I think what I'll do is first uninstall CC.NET and reinstall. Make > sure > > >>> to backup the impacted configs such as ccnet.config. > > > > >>> After that may need some instruction what to watch out for.**** > > **** > > ** ** >
