Two Listeners for port 31538

Vinodanand · Post by **Vinodanand** » Thu Jan 03, 2008 11:21 am

Hi ,
We connect to Data Stage through tunnel using port 31538 and F-secure client or directly by specifying the host name.

This was the same way we used to connect with server.After upgrading to parallel we are facing issues where all of a sudden we see two listeners for the same port 31538 as shown below.

Any help on why we are having this issue would be appreciated.

Code: Select all

tcp        0      0  10.128.189.11.31538    10.191.42.187.3084      CLOSE_WAIT
tcp        0    172  127.0.0.1.52511        127.0.0.1.31538         ESTABLISHED
tcp        0      0  10.128.189.11.31538    10.191.47.114.4901      CLOSE_WAIT
tcp      172      0  127.0.0.1.31538        127.0.0.1.52510         ESTABLISHED
tcp        0      0  10.128.189.11.31538    10.191.34.140.3937      CLOSE_WAIT
tcp      172      0  127.0.0.1.31538        127.0.0.1.52511         ESTABLISHED
tcp        0      0  127.0.0.1.31538        127.0.0.1.53391         CLOSE_WAIT
tcp        0      0  127.0.0.1.31538        *.*                     LISTEN
tcp        0      0  10.128.189.11.31538    10.191.42.187.3106      CLOSE_WAIT
tcp      172      0  127.0.0.1.31538        127.0.0.1.52513         ESTABLISHED
tcp        0      0  10.128.189.11.31538    10.191.35.108.1038      CLOSE_WAIT
tcp        0      0  127.0.0.1.52516        127.0.0.1.31538         ESTABLISHED
tcp        0      0  *.31538                *.*                     LISTEN

Thanks,
Vinod

ray.wurlod · Post by **ray.wurlod** » Thu Jan 03, 2008 3:33 pm

Has someone specifically started an instance of dsrpcd intended to listen only to localhost (127.0.0.1)? If so, why?

Or it may have something to do with your specific tunnelling protocol - you'd have to ask your support provider about that.

Vinodanand · Post by **Vinodanand** » Thu Jan 03, 2008 10:30 pm

ray.wurlod wrote:Has someone specifically started an instance of dsrpcd intended to listen only to localhost (127.0.0.1)? If so, why?

Or it may have something to do with your specific tunnelling protocol - you'd have to ask your support provider about that.

Thanks ray. I will check that but i am skeptical as the dsrpc can only be started by admin or root .

Vinodanand · Post by **Vinodanand** » Sun Jan 20, 2008 9:38 am

This issue has been resolved. One of our shell clients F-Secure had remote forwrding set instead of local forwarding which started the second rogue listener process.