Hi Prabhu,
Well, you're making progress. The new exception indicates that you're making a "primary" connection, and failing on the "secondary" connection. The details don't matter, but the bisocket transport will connect from the client to two different ServerSockets on the server, and you're failing to connection to the secondary ServerSocket.
And I think the error which I reported earlier may be due to a firewall between my Bangalore box and UK box
In fact, the attribute I suggested taking out, "secondaryConnectPort," is relevant to connection in the presence of a firewall. if the firewall is doing address (and, in particular, port) translation. I would check that out next. It could be that you need to connect to a port different from the one the secondary ServerSocket is bound to.
-Ron