Greetings -- Been fighting this problem for two days and haven't found any solutions on any of the boards, just wondered if anyone has had problems running RMI application under Windows XP (home edition). I moved a working RMI application from Windows 98 (working fine) to a Windows XP Home Edition machine. The registry appears to start up fine. The server appears to bind to the registry just fine. The client appears to connect initially to the server (takes a while, though, strangely slow) by getting an instance of the server (as a remote object). But when the client actually tries to call one of the remote methods, the following error is issued after about 20 seconds or so: Connection refused to host nested exception is: java.net.ConnectException: Operation timed out: connect Just wondered if anyone has had issues similar to this with WinXP. Thanks
They both have IPs on the same logical subnet? The client side has a TCP/IP stack installed? I'd rule those two out as problems for starters, just to be sure.
Make visible what, without you, might perhaps never have been seen. - Robert Bresson
Joined: Feb 01, 2002
Thanks for the hint -- the WinXP default IP address was being used and it (the address) and sub mask were actually an illegal combination. I changed the IP and subnet to a logical combination and that cleared it right up. (Still can't figure out, though, why sockets worked.)