-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Dave,
On 11/27/13, 12:39 PM, Dave Pawson wrote: > On 27 November 2013 17:10, Christopher Schultz >> You mean when you try to reach Tomcat's HTTP port from a machine >> hard-wired on the network using the local IP, it works fine? > > No, sorry , I lie Oops, Google chrom could not connect to > 192.168.65:8081 You mean 192.168.1.65:8081 right? >> To summarize, you can ping from anywhere but HTTP only works when >> you use a hard-wired client? Odd. > > ping works from both wired/wireless to the 'main' wired machine > containing the tomcat server > >> >> What if you hard-wire the Windows box? > > I have both... neither works (sorry) Okay, that suggests that the problem is on the Windows box. You said that "wires access to tomcat from a.n.other no problem". What other client did you use and what was its setup? >>> I've got Zone alarm on the windows box. >> >> Does it have any rules concerning outbound traffic? It might be >> blocking lots of stuff to the local network. > > Outbound? I presumed the block (if there was one) was inbound, > http from 'trusted zone' Your Windows box can be configured to refuse to transmit traffic out to certain places. It seems that is the likely problem, here. Check both firewalls for any such rules. >>> I think I have set it to pass through for 'trusted' zone on my >>> local net. >> >> Okay, maybe not. >> >> Some routers have AP-isolation features where the WiFi clients >> can only get to the "outside" of the network, and can't contact >> local machines. But since you can ping the local machine that >> seems to rule that out. > > IMHO I can ping it... does that necessarily mean I can get http > connections? No. ping sends ICMP packets which are in a special category and do not use a port number. They can be allowed or rejected by firewalls. HTTP is TCP/IP and uses whatever port number you want (8081 in your case). >>> Can anyone think of more 'blocks' to seeing the server please? >> >> As far as the Linux machine is concerned, there is no difference >> between a WiFi and hard-wired client, as long as they are in the >> same IP range. I'm not sure you could configure iptables to >> restrict based upon that criteria alone. Is iptables running? >> What rules does it have? > > Sorry.. excuse my ignorance, but how to check? As root, type "iptables -L" and it will list all the firewall rules on the server. I suspect the server is not a problem, though. >> Windows has a built-in firewall, but I believe it's configured >> out of the box to allow anything to call-out to port 80. I'm not >> sure about 8080. If you have ZoneAlarm, does that mean you have 2 >> software firewalls in the mix on that machine? You may want to >> check *both* their settings. > > I believe I have switched off the M$ firewall, since I have > zonealarm running? Only you can answer that. >> Finally, the router can do weird things, too. Check your settings >> for anything "restriction-related". > > It's a BT (our national phone company) router+wifi I haven't found > anything strictly ip to ip mapping related. > > That is one of the potential blockers. That the Windows machine cannot connect regardless of WiFi-versus-Ethernet suggests that the problem is with the Windows box, not the network. - -chris -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.15 (Darwin) Comment: GPGTools - http://gpgtools.org Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIcBAEBCAAGBQJSljjuAAoJEBzwKT+lPKRYXhYP/1Cz5cV1snXcxcH2QzKYGnXw G1s+++EiuEdoCB8cJpTBJhzPzZhlcfoKeTIJv7aHLpQ1zg0aD21Oj52TFok6pRTS HYa4AIossZ87Oh2ePZHpYXzxMbSFgERtMHNNttbd24bcEsimpWZ8RF0NHnQZa0nG 7xfkoQDtMjXsvGQHuoEwLmV96WclOarFyvVO9ZKVRvCNeybI+5Sr0C/zZdCSWBoo t+4vDg2gPfHmwWAbYpsLA1L2PC7oAzhvEtrepilm12GXYWLcM228is9au2RDQgEB YbSEkyzFLx+xv1fF8M2+/YysmhDYt/jYJq+jE8xr52f6JRNbshAt3cnJIKFI2nsu HsfwrfWFbOz6cwxb1oO5UnzBh/VjhpIMOUVQz6G1vpsIb8DZKct+lttYv1vGDnBj DbTBkiVkXSa2J4jfW0dlP6ausrmrYbWRXH2hS7QGR5acXN8alyXw5aGtJ7KJ+Sy9 RVNtdiP2KvH9wLI0CH7oNJn/3C0p7ZyEc/7fqxp0r/oWHB94eqv0Jf5pfxQhMxKP 9d31Z2tHwYgIX90ntuteg62aT742Q8GYRiA1GH71r1rOmYz0OP9j3psHbLLDMOm6 q8Ldx0FmMC37UeKPZNyZTdRu5+L8s33/5r3fq0JCdcvNucrnaV7jQH0G86DQFmpc 3ES9nIoA1/rde+IrnCYu =PeJI -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
