I agree, it all sounds a bit network related - although it's always good to blame those guys when something doesn't work ;-)
If you can't telnet to the server on the port on which the server is listening from a remote client then I lean towards it being network related. Obviously loop-back and localhost aren't hitting the network - unless you've configured things specific for other needs. On 17 December 2010 16:04, Chris Selwyn <[email protected]> wrote: > When you say "there it's no problem to connect to that one"... Do you > mean with a browser? > If that is so then I don't understand how you can connect to port 8080 > on the server from your client with a browser yet telnet cannot connect. > > Whatever is stopping the telnet connecting on port 8080 does not say > anything about what is stopping the access on port 9080. > > Chris > > On 17/12/2010 08:10, alim wrote: > > Hey Chris > > > > When doing the telnet from the client box i get: > > "telnet: Unable to connect to remote host: Connection refused" > > > > However, there's also another AS on that same server listening on port > 8080 > > and there it's no problem to connect to that one. > > > > Plus I also tried running JBoss on port 8080 (while having the other AS > shut > > down), and also there the same problem: > > Telnet local: "Trying 127.0.0.1... Connected to localhost." > > Telnet remote: "telnet: Unable to connect to remote host: Connection > > refused" > > > > Considering that, it couldn't be a firewall problem, could it? > > > > Thanks for the help! > > Audrey > > > > > > > > Chris Selwyn wrote: > >> Maybe a firewall(iptables) issue? > >> Can you do the telnet from your client box? > >> > >> Chris > >> > _______________________________________________ > rules-users mailing list > [email protected] > https://lists.jboss.org/mailman/listinfo/rules-users >
_______________________________________________ rules-users mailing list [email protected] https://lists.jboss.org/mailman/listinfo/rules-users
