The automatically generated stubs contain the ip number of the server. But... they are just automatically generated wrappers around rexec or sexec.
The simplest way would be for you to create your own stub functions set using rexec or sexec using the correct ip addresses. HTH, Maarten > Guys, > > Thought I'd take a look at Rugby to find out what the fuss is about. > It looks quite cool and I can think of some applications. > > However I have a showstopping problem. > > >> test "remote function ahoy!" > ** Access Error: Cannot connect to 192.168.0.2 > ** Where: rexec > ** Near: open/no-wait/direct dest > write-msg msg dest > > 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. > > Is this something where I'm going to have to get my hands dirty with > Rugby itself? > > Regards, > > Mat Bettinson > Codeplay > > Tel: +44 (0)20 7482 3382 > 140-142 Kentish Town Rd, London, NW1 9QB > http://www.codeplay.com > > -- > To unsubscribe from this list, please send an email to > [EMAIL PROTECTED] with "unsubscribe" in the > subject, without the quotes. > -- To unsubscribe from this list, please send an email to [EMAIL PROTECTED] with "unsubscribe" in the subject, without the quotes.
