08-27-2013 08:51 AM
quick question:-
Will Packet loss prevents telnet to bpcd port become failure??
error
Solved! Go to Solution.
08-28-2013 04:51 AM
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.
08-27-2013 09:00 AM
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..
08-27-2013 09:03 AM
08-27-2013 12:20 PM
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.
08-28-2013 02:56 AM
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.
08-28-2013 03:54 AM
The only thing to share is that your clients, media server and master server need to be able to resolve each other to their respective IP addresses. Also if you have firewalls ensure that 13782 and 13724 are open.
This document describes which ports you need open (details PBX for 7.x too)
http://www.symantec.com/business/support/index?page=content&id=TECH136090
08-28-2013 04:51 AM
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.
08-30-2013 08:26 AM
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.