On Sep 17, 2013, at 11:32 AM, Nicholas Violi <nvi...@globalgiving.org> wrote:
> On Tue, Sep 17, 2013 at 11:25 AM, Daniel Mikusa <dmik...@gopivotal.com>wrote: > >> >> Please don't top post. Either reply at the bottom or reply inline. That >> is the convention we try to follow on this list. >> > > Sorry & thanks. > > Can your run netstat and see if anything is listening on those ports? >> "netstat -tln" should work on Linux or "netstat -an | grep LISTEN" on Mac. >> Sorry I'm not sure about the command on Windows. >> > > Yep, I see them: > tcp4 0 0 192.168.1.243.4000 *.* LISTEN > > tcp4 0 0 192.168.1.243.4001 *.* LISTEN Good! Since Tomcat is listening on the ports, you just need to figure out why you can't connect to them. You should be able to telnet to the ports. Try: telnet 192.168.1.243 4000 and telnet 192.168.1.243 4001. Are you sure you don't have a firewall? Dan > > > If it matters, the apache and tomcat ports are running with a wildcard IP: > tcp46 0 0 *.8082 *.* LISTEN > > tcp46 0 0 *.8080 *.* LISTEN > > tcp46 0 0 *.8081 *.* LISTEN > > tcp46 0 0 *.8083 *.* LISTEN > > > Thanks, > Nick --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
