I am facing a problem in getting a few of the LAN clients to recognize in NBU console through 'CONFIGURE CLIENT' utility.While some on the network connect to the NBU console [after disabling the Windows firewall], others are not. Since there is no DNS here, all the name to IP conversion is done through the local hosts file. I have tried the following to identify the cause but have not been successful

1. telnet <client/server name> bpcd - works fine. blinking cursor at both ends
2. bptestbpcd -client <client name> -debug - results in the socket connection failure. Seems to be related to vnetd [vnet-vnetd.c.4181 failed to ....]
3. bptestbpcd -client <client-name> -verbose - pops up Error 57

While the server side logging points to socket connection failure, there is no logging on the client side. I guess the server process is unable to reach the vnetd/bpcd process on the client. However netstat -a, indicates the vnetd process to be in the LISTENING state.

Can someone help me with a few pointers to resolve the same ?

Also let me know what is the relation between vnetd and bpcd processes in a client. How does the client handshake take place in terms of processes.

Thanks
dp_nash