On 27/01/2011 17:23, Pete Helgren wrote: > I can't quite figure out what the issue is here but perhaps someone who > is running Tomcat 5.5 on Windows server 2008 can weigh in. I have > installed Tomcat 5.5 on a Windows Server 2008 64 bit OS. Everything > seemed to install correctly. I was able to bring up the site on > localhost:8080 and on ServerName:8080 but, curiously, couldn't bring it > up on the IP Address of the server itself 192.168.1.200:8080 > > I didn't think much of it and told the customer that they should be able > to access the site with either the internal IP or the internal DNS name > (the site in an Intranet site). Turns out that the site CANNOT be > accessed from anywhere BUT the server itself. The firewall is NOT > running and IIS is running. Tomcat is not running behind IIS. > > Shouldn't I be able to access Tomcat running on the server from anywhere > on the internal network? The tech I have been working with swears that > there is no firewall running anywhere. This is a new installation. I > have had no issues on Windows 2003 so I suspect this is unique to 2008 > but for all my searching of the Internet, I haven't found a solution. > Anyone seen this before? I *suspect* that IIS is somehow controlling > all http traffic, regardless of port but I can't seem to find any hard > evidence of this. > > Suggestions? I am at a loss.
netstat Find out what processes are listening on what addresses & ports. It might be an ipv4/ipv6 issues. If it is, try setting the address to "0.0.0.0" in the connector. Mark --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org