Forum Discussion

Thosch's avatar
Thosch
Level 3
8 years ago
Solved

How to change random port range of pbx_exchange process

Hello.
I would like to change the port range of VRTSpbx / Symantec Private Branch Exchange service.

I found this article but it does not work for me.
https://www.veritas.com/support/en_US/article.000011102

How can i set a custom port range for pbx_exchange.exe?

kindly regards
Thorsten

8 Replies

    • Thosch's avatar
      Thosch
      Level 3

      I tested it with a very few number of ports and it worked.

      Thank you!

  • PBX uses port 1556 - this port is assigned by IANA so nobody else uses it.

    I recommend you don't change the default port as you will have to change the port on all other Netbackup client and servers. 

    Please explain why you want to change the pbx port - has a oracle listener taken the port on a client ?

    Best Regards

    Nicolai

     

    • Thosch's avatar
      Thosch
      Level 3

      additional to port 1556 the service is using some random high ports

      I don't want to change port 1556.

      I want to restrict the upper port range.

      See nbtstat -b:

      Aktive Verbindungen

      Proto Lokale Adresse Remoteadresse Status
      TCP 127.0.0.1:6848 hostname:6849 HERGESTELLT
      [pbx_exchange.exe]
      TCP 127.0.0.1:6849 hostname:6848 HERGESTELLT
      [pbx_exchange.exe]
      TCP 127.0.0.1:6851 hostname:6858 HERGESTELLT
      [pbx_exchange.exe]
      TCP 127.0.0.1:6851 hostname:6864 HERGESTELLT
      [pbx_exchange.exe]
      TCP 127.0.0.1:6851 hostname:6869 HERGESTELLT
      [pbx_exchange.exe]
      TCP 127.0.0.1:6854 hostname:6855 HERGESTELLT

      • Nicolai's avatar
        Nicolai
        Moderator

        I think what you are seeing is normal/expected

        When making a network connection you have source and destination port. The destination port is what matters (e.g. port 80 www or 1556) - the source port or change of it is negotiated between the two hosts and can be any unassigned port - usually in the high range. Firewall are also aware of this - this is called stateful inspections.

        Here is a example for browser connections made with SSL - port 443.

        netstat -a -n | findstr 443
        TCP x.x.x.x:50913 x.x.x.x:443 ESTABLISHED
        TCP x.x.x.x:61069 x.x.x.x:443 ESTABLISHED