Flik, On 07/21/2010 06:18 AM, Flik Shen wrote: > Hi Felix, > > You're right. It is too chary that to mask the internal IP address. > > I am not sure about what kind Jmeter server listening ports you mentioned. > In my case, the listening port of Jmeter server is 4000 and RMI registry > server is 1099. > Do you mean I should pay more attention to additional high numbered ports > besides listening ports of Jmeter server and RMI registry server?
Ah, sorry, I missed the bit about you setting the server port manually. Good idea that. > I also find that with or without tunnel to port 4000, I both got same error > message "NoRouteToHostException". > So I guess, even though the client communicates RMI server via tunnel, it > will try to reach Jmeter server by host's IP address directly. That rings a bell. I remember a lot of fuss with wrong host name resolutions. Try adding aliases to 127.0.0.1 that correspond to the Jmeter Server on your Jmeter controlling host (the one initiating remote execution) to the /etc/hosts file (this assumes *nix, not sure how to do this in Windows). The remote host may or may not also be aware of the details of the peer. To clarify, the /etc/hosts file on your box host should probably look like 127.0.0.1 localhost jmeter1 192.168.0.1 desktop or somesuch, assuming your jmeter server knows itself as "jmeter1". HTH Felix --------------------------------------------------------------------- To unsubscribe, e-mail: jmeter-user-unsubscr...@jakarta.apache.org For additional commands, e-mail: jmeter-user-h...@jakarta.apache.org
