You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomcat.apache.org by Sebastian Kerekes <se...@gmx.net> on 2004/09/21 17:50:30 UTC

once again: can't send request over my network ip

Once again, to avoid confusion.

I'm using Tomcat 5.0.27. I can access it from my computer via 
127.0.0.1:8080, but not via 192.168.1.172:8080. But I can reach Tomcat 
from another computer in the network via 192.168.1.172:8080. I didn't 
change any Tomcat settings. I'm using WinXP Professional and no firewall 
is running.

Any idea what the problem could be?

Thanks for your help,

Sebastian

---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-user-help@jakarta.apache.org


Re: AW: once again: can't send request over my network ip

Posted by Sebastian Kerekes <se...@gmx.net>.
Steffen Heil wrote:

> Hi
> 
> 
>>I'm using Tomcat 5.0.27. I can access it from my computer via
> 
> 127.0.0.1:8080, but not via 192.168.1.172:8080. But I can reach Tomcat from
> another computer in the network via 192.168.1.172:8080. I didn't change any
> Tomcat settings. I'm using WinXP Professional and no firewall is running.
> 
> Maybe it is simply a proxy setting? Are you sure there is no proxy set in
> your browser?
> 
> Regards,
>   Steffen

No, no proxy. Very strange problem ;).

---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-user-help@jakarta.apache.org


AW: once again: can't send request over my network ip

Posted by Steffen Heil <li...@steffen-heil.de>.
Hi

> I'm using Tomcat 5.0.27. I can access it from my computer via
127.0.0.1:8080, but not via 192.168.1.172:8080. But I can reach Tomcat from
another computer in the network via 192.168.1.172:8080. I didn't change any
Tomcat settings. I'm using WinXP Professional and no firewall is running.

Maybe it is simply a proxy setting? Are you sure there is no proxy set in
your browser?

Regards,
  Steffen