Hi Mat, << The key bit here is the ip. That's not a real ip, the server is behind NAT. It is however the dirty-net of the firewall so a request to the IP will work.
However I need to get rugby to report some other IP to connect to rather than the bogus real/local IP which it has sent to my client. >> I had this same problem when importing stubs with Rugby. My solution, for the time being, is to use rexec directly, which works fine because you're specifying the IP yourself. I'm not sure how much Rugby is at the mercy of the underlying system in this regard, or if it's something that can be addressed in Rugby itself. --Gregg -- To unsubscribe from this list, please send an email to [EMAIL PROTECTED] with "unsubscribe" in the subject, without the quotes.
