PE not reporting listening port?

Discussion in 'Port Explorer' started by BlueStar50, Jul 28, 2004.

Thread Status:
Not open for further replies.
  1. BlueStar50

    BlueStar50 Registered Member

    Joined:
    Jul 16, 2004
    Posts:
    15
    After disconnecting from the net TCPView & Netstat Viewer both show:
    Protocol Local Remote Status
    TCP 0.0.0.0:1452 0.0.0.0:0 LISTENING
    I cannot close the connection in TCPView.
    CAD does not show any programs open that should have any port left open like IE.
    PE does not show any ports listening.

    TDS-3's local port scanner did not detect this tcp port as being in use.
    Why is PE missing this tcp port that is listening?
     
  2. Jooske

    Jooske Registered Member

    Joined:
    Feb 12, 2002
    Posts:
    9,713
    Location:
    Netherlands, EU near the sea
    Why should Port Explorer show a local internal port communication on your local host (0.0.0.0 is your local host anyway) in use if you're not connected to the net at all?
     
  3. BlueStar50

    BlueStar50 Registered Member

    Joined:
    Jul 16, 2004
    Posts:
    15
    It wasn't showing it when I was connected or after I disconnected.
    Today port 1349 is doing the same thing right now as I am connected.
    I remembered to uncheck Hide Netstat Sockets and port 1349 is now showing as a System process being behind it. There is no option to kill the socket or program.

    Is this kind of stuff only happening to me? What can cause a socket like that to be left listening for no reason even if it is only a local internal port communication? And last of all why can't such connections be killed or closed?
     
  4. Rasheed187

    Rasheed187 Registered Member

    Joined:
    Jul 10, 2004
    Posts:
    8,046
    Location:
    The Netherlands
  5. Jooske

    Jooske Registered Member

    Joined:
    Feb 12, 2002
    Posts:
    9,713
    Location:
    Netherlands, EU near the sea
    I don't happen to see any problem with this?
    I see a local host port 137 to localhost port 0 listening etc etc and i don't have any problem with that, so on many other port numbers, so if anybody can explain why this should be wrong while this is normal behavior.
    I have TDS configured to have sockets listening on several default ports which is shown perfectly, including the UDP "twin" for the TCP ports, as netstat sockets etc.
    loopback combinations like
    0.0.0.0 port 1025 listening on 0.0.0.0 port 0
    0.0.0.0 port 0 listening om 0.0.0.0 port 1025

    I have lots of port 0 no problem with that, Jason explained time ago what that indicates.
     
Thread Status:
Not open for further replies.