I just downloaded the latest version of Rugby, which fixes the problem. The only problem I have now is that in the old version of Rugby I could issue a statement like "useport: server/__rugby-server-address/port-id" that would return the local port that the server is using. When trying to issue this statement in the new version (4.3) I get an error that says "Invalid path value: __rugby-server-address" Is there anyway to issue a similar statement in the new version?
Thanks, Matt --------------------------------------- The latest version on http://www.koopgoedkoop.net/rugby.zip uses for sure the address used by the client when doing get-rugby-service. Are you using that one? --maarten >-----Original Message----- >From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of >Matt MacDonald >Sent: dinsdag 28 oktober 2003 21:06 >To: [EMAIL PROTECTED] >Subject: [REBOL] Re: Rugby Question > > >They do database reads mostly. The firewall is set up to allow incoming >and >outgoing connections on the ports I need. For instance "r: open >tcp://ip-address:8001" works. But if I do this: > >server: context get-rugby-service tcp://ip-address:8001 > >and then try something like t: server/probe-messages userid, then i get an >error on the client machine (outside of the firewall) that says that it >cannot connect to 10.10.1.14 which is the internal IP address of the >server. > But it shouldn't be trying to connect to that IP address at all, it >should >be trying to connect to port 8000 on the firewall's external IP which then >routs it internally to the server. > >I'm not super knowledgable when it comes to networks, but I'm not seeing >why >it should be trying to access that internal IP in the first place. > >Thanks for any help, >Matt > > >------------------------------------ >Matt, > >What do your server functions do? It sounds like your firewall prevents >accessing the business logic here, i.e. this is a network problem. > >You can have a Rugby server running on one ip address when it's a dual >network-card server, that's what most people would do. Then allow >incoming calls only on one card, and sandwich the box between two >routers and two firewalls. If you get the router and firewall configs >right there should be no problem. > >--Maarten > > >-----Original Message----- > >From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf >Of > >Matt MacDonald > >Sent: dinsdag 28 oktober 2003 16:33 > >To: [EMAIL PROTECTED] > >Subject: [REBOL] Rugby Question > > > > > >If I'm using rugby to serve functions outside of a firewall, so that >the > >client will not be able to see the internal IPs of the server, do I >need > >to > >use rexec and sexec to remotely execute all of the functions? Or is >there > >a > >way to use the standard import method. Basically what is happening is > >that > >I keep getting errors on the server that says that it can't connect to >the > >servers internal IP. > > > >Matt > > _________________________________________________________________ Never get a busy signal because you are always connected with high-speed Internet access. Click here to comparison-shop providers. https://broadband.msn.com -- To unsubscribe from this list, just send an email to [EMAIL PROTECTED] with unsubscribe as the subject.
