Forum Discussion

NBU_nbu's avatar
NBU_nbu
Level 4
12 years ago
Solved

Telnet to bpcd issue

quick question:-

Will Packet loss prevents telnet to bpcd port become failure??

error

telnet: Unable to connect to remote host: Connection refused
 
  • You have selected 7.5 as your product version in your opening post.

    NBU 6.0 and above connects to vnetd (13724). Nothing else is needed - just 13724 in both directions.

    The bptestbpcd method was introduced in NBU 6.0.

7 Replies

  • Connection refused

    it is something like, destination has recived the request but it rejected..

    may be name resoution issue.

    may be port over flow 

    etc

    post us the bpcd log of the destination to see if it is looking anything.. 

  • No it shouldn't prevent connection. Check the end server doesn't have a firewall enabled. Also enable the bpcd log to see if it is connecting then dropping. Packet loss will cause backup failure though!
  • For NBU 7.5 you should connect to pbx (1556) or vnetd (13724).

    Check that the client's OS firewall is turned off and that NBU services are up and running on client.

    Use bptestbpcd to test connectivity - it tests port connectivity, hostname lookup as well as connect-back.

    Create bpcd log folder on client, then test as follows from master and/or media server:

    bptestbpcd -client <client-name> -verbose -debug

    check command output as well as client's bpcd log file.

  • Thanks For your reply.

    This is 6.5.x FYI. we have been facing this issue with number of servers (windows and unix) seems there might be a Network related issue. working with network team now... will let everyone know what things went wrong.

    please share any related to network.

  • You have selected 7.5 as your product version in your opening post.

    NBU 6.0 and above connects to vnetd (13724). Nothing else is needed - just 13724 in both directions.

    The bptestbpcd method was introduced in NBU 6.0.

  • FYI....Source (master server) ->Switch->firewall->destination server.....

    Firewall not able to see any flow of packets. 

    and from swtich they were not able to telnet to 13724.

    had to set 13724 in bi-directions.