Announcement

Collapse
No announcement yet.

Port not visible on LAN - Help to locate problem

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • Port not visible on LAN - Help to locate problem

    Hi, Folks.

    I have an application that needs to be accessed over the LAN on tcp port 8080.

    If I open a browser on http://127.0.0.1:8080, i see it fine.

    If I use http://192.168.0.2:8080, which is the IP address of THIS server, then it's page cannot be displayed. It's not an Internet explorer issue as there is a monotoring utility that shows the same result.

    Netstat -o shows:

    TCP xyzserver:8080 xyzserver.xyz.local:1838 TIME_WAIT
    0
    TCP xyzserver:8080 xyzserver.xyz.local:1844 TIME_WAIT
    0
    TCP xyzserver:8080 xyzserver.xyz.local:1886 TIME_WAIT
    0
    TCP xyzserver:8080 xyzserver.xyz.local:1912 TIME_WAIT
    0
    TCP xyzserver:8080 xyzserver.xyz.local:1919 TIME_WAIT
    0
    TCP xyzserver:8080 xyzserver.xyz.local:1951 TIME_WAIT
    0

    Can anyone give me any guidance ?

    Many thanks,

    Neil
    Last edited by neilmac; 4th February 2007, 21:27.
    Neil Mac

  • #2
    Re: Port not visible on LAN - Help to locate problem

    Hi, Neil.
    I understand you are doing all the tests from the same server where the application is installed, aren't you ?
    If so, please check the firewall on the server, that allows connections to port 8080.
    What is the output of netstat -a command? Do you see LISTENING on port 8080?

    Sorin Solomon


    In order to succeed, your desire for success should be greater than your fear of failure.
    -

    Comment


    • #3
      Re: Port not visible on LAN - Help to locate problem

      Thanks, Sorin.

      Absolutely NO firewall on that server.

      Netstat -a shows:

      TCP xyzserver:8080 xyzserver.xyz.local:0 LISTENING
      TCP xyzserver:8080 xyzserver.xyz.local:1561 TIME_WAIT
      TCP xyzserver:8080 xyzserver.xyz.local:1597 TIME_WAIT
      TCP xyzserver:8080 xyzserver.xyz.local:1606 TIME_WAIT
      TCP xyzserver:8080 xyzserver.xyz.local:1610 TIME_WAIT
      TCP xyzserver:8080 xyzserver.xyz.local:1616 TIME_WAIT
      TCP xyzserver:8080 xyzserver.xyz.local:1621 TIME_WAIT
      TCP xyzserver:8080 xyzserver.xyz.local:1626 TIME_WAIT
      TCP xyzserver:8080 xyzserver.xyz.local:1630 TIME_WAIT
      TCP xyzserver:8080 xyzserver.xyz.local:1637 TIME_WAIT
      TCP xyzserver:8080 xyzserver.xyz.local:1646 TIME_WAIT
      TCP xyzserver:8080 xyzserver.xyz.local:1656 TIME_WAIT
      TCP xyzserver:8080 xyzserver.xyz.local:1666 TIME_WAIT
      TCP xyzserver:8080 xyzserver.xyz.local:1672 TIME_WAIT
      TCP xyzserver:8080 xyzserver.xyz.local:1676 TIME_WAIT
      TCP xyzserver:8080 xyzserver.xyz.local:1682 TIME_WAIT
      TCP xyzserver:8080 xyzserver.xyz.local:1686 TIME_WAIT
      TCP xyzserver:8080 xyzserver.xyz.local:1689 TIME_WAIT
      TCP xyzserver:8080 xyzserver.xyz.local:1696 TIME_WAIT
      TCP xyzserver:8080 xyzserver.xyz.local:1705 TIME_WAIT
      TCP xyzserver:8080 xyzserver.xyz.local:1708 TIME_WAIT
      TCP xyzserver:8080 xyzserver.xyz.localptp TIME_WAIT
      TCP xyzserver:8080 xyzserver.xyz.local:1733 TIME_WAIT
      TCP xyzserver:8080 xyzserver.xyz.local:1736 TIME_WAIT
      TCP xyzserver:8080 xyzserver.xyz.local:1743 TIME_WAIT
      TCP xyzserver:8080 xyzserver.xyz.local:1748 TIME_WAIT
      TCP xyzserver:8080 xyzserver.xyz.local:1749 TIME_WAIT
      TCP xyzserver:8080 xyzserver.xyz.local:1752 TIME_WAIT
      TCP xyzserver:8080 xyzserver.xyz.local:1757 TIME_WAIT
      TCP xyzserver:8080 xyzserver.xyz.local:1764 TIME_WAIT
      TCP xyzserver:8080 xyzserver.xyz.local:1774 TIME_WAIT
      TCP xyzserver:8080 xyzserver.xyz.local:1784 TIME_WAIT
      TCP xyzserver:8080 xyzserver.xyz.local:1787 TIME_WAIT
      TCP xyzserver:8080 xyzserver.xyz.local:1796 TIME_WAIT
      TCP xyzserver:8080 xyzserver.xyz.local:1800 TIME_WAIT
      TCP xyzserver:8080 xyzserver.xyz.local:1805 TIME_WAIT
      TCP xyzserver:8080 xyzserver.xyz.local:1809 TIME_WAIT
      TCP xyzserver:8080 xyzserver.xyz.local:1816 TIME_WAIT
      TCP xyzserver:8080 xyzserver.xyz.local:1824 TIME_WAIT
      TCP xyzserver:8080 xyzserver.xyz.local:1833 TIME_WAIT
      Neil Mac

      Comment


      • #4
        Re: Port not visible on LAN - Help to locate problem

        Couple of questions for ya as I have my SharePoint site running on 8080 on W2K3 STD and I tried what you tried FROM THE SERVER and it worked as expected.

        Note I DO have the Windows Firewall running w/ an exception on TCP 8080

        What OS are you running?

        In IIS Manager on that web site running on 8080, is the IP address set to "(All Unassigned)"?

        My netstat -a shows TCP myserver:8080 myserver:0 LISTENING
        My netstat -o shows nothing re: 8080
        Cheers,

        Rick

        ** Remember to give credit where credit is due and leave reputation points sigpic where appropriate **

        2006-2099 R Valstar. This post is offered "as is" for discussion purposes only with no express or implied warranty of any kind including, but not limited to, correctness or fitness for use. Nothing herein shall be construed as advice. Attempting any activity based on information in this post is done at your own risk.

        Comment


        • #5
          Re: Port not visible on LAN - Help to locate problem

          It's a straight windows 2003 R2 Server.

          No firewall, no IIS, nothing.

          The same application also uses port 80 and 8081, both of which are available over the LAN.


          Just 8080 that's missing...
          Neil Mac

          Comment


          • #6
            Re: Port not visible on LAN - Help to locate problem

            So this is an application, not IIS? What application?
            Cheers,

            Rick

            ** Remember to give credit where credit is due and leave reputation points sigpic where appropriate **

            2006-2099 R Valstar. This post is offered "as is" for discussion purposes only with no express or implied warranty of any kind including, but not limited to, correctness or fitness for use. Nothing herein shall be construed as advice. Attempting any activity based on information in this post is done at your own risk.

            Comment


            • #7
              Re: Port not visible on LAN - Help to locate problem

              F Secure Policy Manager.
              Neil Mac

              Comment


              • #8
                Re: Port not visible on LAN - Help to locate problem

                So put a website on 8080 and see if it works. Then we'll know the problem is with "F Secure Policy Manager"
                Cheers,

                Rick

                ** Remember to give credit where credit is due and leave reputation points sigpic where appropriate **

                2006-2099 R Valstar. This post is offered "as is" for discussion purposes only with no express or implied warranty of any kind including, but not limited to, correctness or fitness for use. Nothing herein shall be construed as advice. Attempting any activity based on information in this post is done at your own risk.

                Comment


                • #9
                  Re: Port not visible on LAN - Help to locate problem

                  well, locally, http://localhost:8080 gives an FSecure page telling me that the admin module is installed correctly.

                  However, http://192.168.0.2:8080 is page cannot be displayed.
                  Neil Mac

                  Comment


                  • #10
                    Re: Port not visible on LAN - Help to locate problem

                    Originally posted by neilmac View Post
                    well, locally, http://localhost:8080 gives an FSecure page telling me that the admin module is installed correctly.

                    However, http://192.168.0.2:8080 is page cannot be displayed.
                    Obviously you can set the ports on which this app listens, no? Remove 8080 for the moment, set a website to 8080 and see if you can get the "construction" page. I'm 99.44% sure the issue is either a conflict with another app or a configuration issue with the F... (not a curse word here) app itself.

                    So does that make me 49.72% sure? It's late give me leeway for the bad joke.
                    Cheers,

                    Rick

                    ** Remember to give credit where credit is due and leave reputation points sigpic where appropriate **

                    2006-2099 R Valstar. This post is offered "as is" for discussion purposes only with no express or implied warranty of any kind including, but not limited to, correctness or fitness for use. Nothing herein shall be construed as advice. Attempting any activity based on information in this post is done at your own risk.

                    Comment


                    • #11
                      Re: Port not visible on LAN - Help to locate problem

                      Any chance you have proxy that listens on port 8080 configured in your browser ?
                      Does telneting to 192.168.0.2 on port 8080 gives any response ?
                      Guy Teverovsky
                      "Smith & Wesson - the original point and click interface"

                      Comment


                      • #12
                        Re: Port not visible on LAN - Help to locate problem

                        IIS isn't installed, so no web site blocking 8080.

                        FTP responds locally but not over the network, so I am sure it's FSecure that is responding.

                        (There is no logon, but the connection is established - the updates to the workstations is done on a port 8080 connection, so I imagine it's that)
                        Neil Mac

                        Comment


                        • #13
                          Re: Port not visible on LAN - Help to locate problem

                          Thanks to everyone for the help.

                          I solved it - during the install, the software gives you the option to listen on all ports or just the local machine. Even though all ports was selected, the config file fo the software wrote:

                          listen 127.0.0.1 8080

                          I changed it to:

                          listen 8080

                          It now works....

                          Odd, I found it by replicating the install on another machine that went the same way. So, it was definitely the app...

                          Thanks guys, you may not have come up with the full answer, but you certainly helped me pinpoint where to look.

                          -Neil
                          Neil Mac

                          Comment

                          Working...
                          X