Find the answer to your Linux question:
Page 2 of 3 FirstFirst 1 2 3 LastLast
Results 11 to 20 of 21
Like Tree1Likes
yes i can connect to port 80. my iptables says which is same as other servers. # sbin/iptables --list Chain INPUT (policy ACCEPT) target prot opt source destination Chain FORWARD ...
Enjoy an ad free experience by logging in. Not a member yet? Register.
  1. #11
    Just Joined!
    Join Date
    Apr 2014
    Posts
    11

    yes i can connect to port 80.

    my iptables says which is same as other servers.

    # sbin/iptables --list
    Chain INPUT (policy ACCEPT)
    target prot opt source destination

    Chain FORWARD (policy ACCEPT)
    target prot opt source destination

    Chain OUTPUT (policy ACCEPT)
    target prot opt source destination


    is there any where else i need to look?

  2. #12
    Just Joined!
    Join Date
    Apr 2014
    Posts
    11
    yes port 80 is working.

    iptable list same for all servers

    ]# sbin/iptables --list
    Chain INPUT (policy ACCEPT)
    target prot opt source destination

    Chain FORWARD (policy ACCEPT)
    target prot opt source destination

    Chain OUTPUT (policy ACCEPT)
    target prot opt source destination


    Even though iptables list same for all the servers.i don't see a file /sbin/sysconfig/iptables on all the servers except on a server which is not working.is it something to take for consideration? should i delete that file and restart iptables?

    $ cat /etc/sysconfig/iptables
    # Generated by iptables-save v1.2.11 on Fri Apr 4 15:10:35 2014
    *nat
    :PREROUTING ACCEPT [17893:1268670]
    :POSTROUTING ACCEPT [7488:497956]
    :OUTPUT ACCEPT [7488:497956]
    COMMIT
    # Completed on Fri Apr 4 15:10:35 2014
    # Generated by iptables-save v1.2.11 on Fri Apr 4 15:10:35 2014
    *filter
    :INPUT ACCEPT [25515368:125844118699]
    :FORWARD ACCEPT [0:0]
    :OUTPUT ACCEPT [25569236:125941672456]
    COMMIT
    # Completed on Fri Apr 4 15:10:35 2014

  3. #13
    Linux Engineer
    Join Date
    Dec 2013
    Posts
    1,078
    I don't think it could hurt - you don't appear to be using iptables.

    The only other thing I can think of: do you have a gateway that is filtering your traffic?

  4. #14
    Just Joined!
    Join Date
    Apr 2014
    Posts
    11
    i just tried that and it look like no effect after deleting a file.

    yes i do have a gateway.i see that under /etc/sysconfig/network-scripts/ifcfg-eth0 file.but this gateway IP same for all servers.

    where can i check about filtering out traffic from a gateway?

  5. #15
    Linux Engineer
    Join Date
    Dec 2013
    Posts
    1,078
    Do you have access to it? It could be as simple as checking the iptables rules on the machine.

  6. #16
    Just Joined!
    Join Date
    Apr 2014
    Posts
    11
    Unfortunately i don't have access to that machine.

    i asked network guy to give me a access then i will check.I will let you know as soon as i get access to it.

    thank you so much for your help.

  7. #17
    Linux Engineer docbop's Avatar
    Join Date
    Nov 2009
    Location
    Woodshed, CA
    Posts
    905
    have you tried connecting with other tools (telnet or netcat) to see if you can get some more info.
    A lion does not lose sleep, over the opinion of sheep.

  8. #18
    Just Joined!
    Join Date
    Apr 2014
    Posts
    11
    Hello ,

    our network guy have solved issue for port 8080 and removed a iptables rule on port 8080 on gateway. I can connect now externally using port 8080.Thanks for pointing out about gateway.

    eg:
    $ nc -vz portquiz.net 8080
    portquiz.net [178.33.250.62] 8080 (webcache) open

    but our jboss website still give error and not working
    2014-04-24 07:57:14,274 INFO [STDOUT] java.net.ConnectException: Connection refused
    2014-04-24 07:57:14,275 INFO [STDOUT] at java.net.PlainSocketImpl.socketConnect(Native Method)

    we are trying to connect from our website port 8080 to external website port 8081.and 8081 is still closed.

    $ nc -vz portquiz.net 8081
    portquiz.net [178.33.250.62] 8081 (tproxy) : Connection refused

    If we open our outgoing port 8081.will it work?

    thank you for your help

  9. #19
    Linux Engineer
    Join Date
    Dec 2013
    Posts
    1,078
    If it isn't opened it will need to be.

    I don't think you are really connecting from port 8080 to 8081? That doesn't actually make sense.

    I'm going to guess that what you mean is you are listening on port 8080. When you get a connection you open a client that connects to a listening (server) socket on an external site on port 8081? The socket will be identified by 8081 at both ends though you may choose to use two sockets for some reason and have a connection at 8080 as well. The gateway will need to pass through traffic on 8081.
    kkhamar likes this.

  10. #20
    Linux Newbie
    Join Date
    Jun 2012
    Location
    SF Bay area
    Posts
    151
    Quote Originally Posted by gregm View Post
    You can connect to portquiz.net:80 but not portquiz.net:8080? Are you filtering outgoing ports? i.e. iptables?
    This... And if the server isn't using any host based ACL rules, the network devices might be. For instance, it could easily be a firewall rule that only allows specific IP's to initiate connections to external servers on port 8080. The IP of the one server that's failing might not be on the list.

Page 2 of 3 FirstFirst 1 2 3 LastLast

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •