Hi,

Here is the output of the command [ netstat -an | find "8080" ] on different 
configurations:

- With Tomcat 5.5.29:

  TCP    [::]:8080              [::]:0                 LISTENING

- With Tomcat 5.5.29, after accessing it via IE8, with http://localhost:8080:

  TCP    [::]:8080              [::]:0                 LISTENING
  TCP    [::1]:8080             [::1]:61956            ESTABLISHED
  TCP    [::1]:8080             [::1]:61957            ESTABLISHED
  TCP    [::1]:61956            [::1]:8080             ESTABLISHED
  TCP    [::1]:61957            [::1]:8080             ESTABLISHED

- With Tomcat 5.5.17:

  TCP    0.0.0.0:8080           0.0.0.0:0              LISTENING
  TCP    [::]:8080              [::]:0                 LISTENING

- With Tomcat 5.5.17, after accessing it via IE8, with http://localhost:8080:

  TCP    0.0.0.0:8080           0.0.0.0:0              LISTENING
  TCP    [::]:8080              [::]:0                 LISTENING
  TCP    [::1]:8080             [::1]:62008            ESTABLISHED
  TCP    [::1]:8080             [::1]:62009            ESTABLISHED
  TCP    [::1]:62008            [::1]:8080             ESTABLISHED
  TCP    [::1]:62009            [::1]:8080             ESTABLISHED

As you can see, there is a difference: "  TCP    0.0.0.0:8080           
0.0.0.0:0              LISTENING" is present with Tomcat 5.5.17, but not with 
Tomcat 5.5.29.
Does it explain my problem ?







--------------------



Marc, if you start up a command prompt and run:

netstat -an | find "8080"

... what do you get?  In particular, I'm interested to know whether the port
that's listening is bound to "*:8080" or to something like "127.0.0.1:8080".

- Peter

On 7 May 2010 11:56, Eyrignoux Marc <eyrig...@yahoo.fr> wrote:

>
> Thank you for the answer, but I think it is not a network problem:
>
> "nslookup epigonesrv11" answers correctly on my computer:
> Nom :    epigonesrv11.epigonedom.dom
> Address:  192.168.0.6
>
>
> "ping epigonesrv11" answers also correctly (with some french in it):
> Envoi d'une requête 'ping' sur EPIGONESRV11.epigonedom.dom [192.168.0.6]
> avec 32 octets de données :
>
>
> Réponse de 192.168.0.6 : octets=32 temps<1ms TTL=128
> Réponse de 192.168.0.6 : octets=32 temps<1ms TTL=128
> Réponse de 192.168.0.6 : octets=32 temps=1 ms TTL=128
> Réponse de 192.168.0.6 : octets=32 temps<1ms TTL=128
>
> Statistiques Ping pour 192.168.0.6:
>    Paquets : envoyés = 4, reçus = 4, perdus = 0 (perte 0%),
> Durée approximative des boucles en millisecondes :
>    Minimum = 0ms, Maximum = 1ms, Moyenne = 0ms
>
>
>
> But "telnet epigonesrv11 8080" answers that connection on port 8080 is
> impossible:
> Connexion à epigonesrv11...Impossible d'ouvrir une connexion à l'hôte, sur
> le port 8080: Échec lors de la connexion
>
>
>
>
> As I explained anyway, all the firewalls are inactive, AND I can establish
> a connection with Tomcat 5.5.17 BUT not with Tomcat 5.5.29.
> All my installs are the simplest ever (always "next" in .exe installer;
> only unzip and launch startup.bat with zip distrib). I tried the windows
> .exe installers of Tomcat 5.5.17 and Tomcat 5.5.29, and the zip
> distributions of Tomcat 5.5.17 and Tomcat 5.5.29, and:
> - my computer contacts Tomcat 5.5.17 on port 8080 (either when installed by
> a zip or an exe)
> - my computer does not contact Tomcat 5.5.29 on port 8080
> - Tomcat 5.5.29 is running, since it is accessible from the local server (I
> log on the server, and call http://localhost:8080, and I get the admin
> console)
>
>
>
>
>
>
> ------------
>
>
> > Hi all,
> >
> > I have installed Tomcat 5.5.29 on Windows 2008 as a service.
> > It works fine on the computer where I installed it:
> http://localhost:8080/, http://localhost:8080/admin,
> http://localhost:8080/manager/html, http://localhost:8080/myWebApp answer
> well.
> >
> > But when I try to access it from any other computer of the local private
> network, I get a "Connection failed" error, ie. the URLs
> http://myServer:8080/, http://myServer:8080/admin, etc... do not respond.
> >
> > NB:
> > - the firewall is inactive on the server and on the clients
> > - my configuration is basic: no AJP, no proxy, no cluster, I call Tomcat
> directly on the default ports
>
> This :
> > - I tried a "telnet myServer 8080", which did not work
>
> That would tend to indicate that you have a problem which has nothing to do
> with Tomcat, but has to do with either
> - the DNS (name resolving of "myServer" does not give the IP address of
> your host)
> OR
> - something is blocking remote access to your host on port 8080
>
> and this :
> > - I tried to install Tomcat 5.5.17 instead of Tomcat 5.5.29, and it
> worked !! ie. the URLs http://myServer:8080/, http://myServer:8080/admin,
> etc... DO  respond !!
> >
> contradicts the above.
> There is a puzzle there..
>
> To find out if there is a problem with name resolution, do this :
> on the same workstation where you tried the telnet command, enter
> nslookup myServer
>
> it should tell you the IP address of that host.  If it does not, you have a
> DNS issue.
>
> To find out if there is a general network issue between the workstation and
> the server, do
> ping myServer
>
>
> In general however, instead of saying "it did not work", try to be a bit
> more specific.  What exactly happens when you do
> telnet myServer 8080
>
> Don't be afraid to paste the original error message here, we're polyglots.
>  We even have mind-readers, but they appear to be on vacation right now.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
> For additional commands, e-mail: users-h...@tomcat.apache.org
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
> For additional commands, e-mail: users-h...@tomcat.apache.org
>
>





---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Reply via email to