Last post Nov 07, 2006 04:10 PM by joeywaters
Nov 01, 2006 01:20 PM|joeywaters|LINK
When I Installed the issue tracker on my web server I am able to browse to it via the LocalHost URL but I am not able to view it from the internet and remote PCs.
It looks like it is setup in IIS correctly but I am not an IIS expert.
Has anyone had this problem and does anyone know how to make the Issue Tracker viewable from the Internet and not just the local server?
Any info would be greatly appreciated.
Thanks in advance.
Nov 05, 2006 05:32 PM|irasmith|LINK
If you mean by remote PCs machines that are on the same network as the server Issue Tracker is installed on, when on the remote PCs are you using
http://name of machine issuetracke rinstalled on/virtual path name of issuetracker? From a remote PC you can't use
http://localhost/virtualpathofissuetracker because that would try to access the machine you are working from which does not have it installed.
When trying to access it from the Internet, do you have your web server it is installed on set up to be accessiable from the Internet?
Hope this helps.
Nov 06, 2006 12:32 PM|joeywaters|LINK
Yes it is on our web server under our defaullt website.
I uninstalled it and put it on our new web server that is going into production in a couple of weeks and it doesnt work from the localhost url.
The SQL DB is setup and the virtual dirs are under the default site.
I am stumped.
It was at least working from the localhost URLl on the old server and now on the new it doesn’t show at all.
I set it up exactly like the old when I set it up on the new.
I get a "Server Error in '/' Application" and "The resource cannot be found." error when browsing from the LocalHost URL.
Any insight would be a big help.
Nov 06, 2006 09:55 PM|irasmith|LINK
Are you installing this on a Windows 2003 Server under IIS 6? Is both .NET 1.x and .NET 2.x loaded on the system? If you open up the IIS 6 management console and right click on the virtual directory for the Issue Tracker web site and selecte the properties
tab, look at what application pool it is set to use. Then within the IIS 6 management console check in the Application Pool folder to make sure that pool does exist and see what version of .NET it is set to use.
Hope this helps.
Nov 07, 2006 04:10 PM|joeywaters|LINK
Yes I did verify that IIS 6 and .net1.1 and 2.0 are installed and working correctly.
I just had to use the IP address of the server instead of localhost and it finally came up.
I am not sure why it gave me so much trouble but it is working now.
Thanks very much for your replies.