Based in the telnet response, host 192.168.1.82 does have port 1099 open and it is accessible. And the response looks like what is expected (this is a JNDI port, after all, so the response will be in binary). The important part is the hostname that appears on the next-to-the-last last line:
Now the question is, does the hostname 'win2003' map to the IP address 192.168.1.82? If not, you need to edit the hosts file and add that mapping. I recommend adding it to both 192.168.1.82 and to the client machine.
Thanks Peter,I have tried to map hostname with IP both in host and client in 'host file'.
The problem is solved as soon as I re-start service ,and I can call remote ejb successful!!
subsequently,I tried to modify the 'host file', I found it must be mapped "192.168.1.84 win2003" in client machine,but the Host side is not necessary !
Then I checked my studio machines 's 'host file' there is not 'IP hostname' mapping for host either in client or host, but it still can call remote ejb successfully?
Is it related Router config?
Somebody somewhere has to map the host name to the IP address. For example, at my work, all hostnames are registered and in the corporate DNS, so there I never have an issue and I never have to update my hosts file (unless I want to communicate with a Linux machine - they never end up in the DNS). At home, however, my router does not always manage host names properly so there I have to put all of the host names and IP addresses into the hosts files. You are probably experiencing similar things.