Re: JXTA private net problems

Excellent.

I don't get the port forwarding either, although, again, I steer clear
of these things.

But I know someone who may know:  Steve Myers of TrustedPeer:  are you
out there?

Mark

On Tue, Dec 05, 2006 at 07:55:50PM +0100, [email protected] wrote:
> Sorry for the confusion ;)
> 10.1.14.132 is the IP of my PC and 192.168.13.6 is used in the DMZ and 
> 83.64.248.67 is the external IP. But I just took my server out of the 
> DMZ and directly connected it to the Internet and WOHOOOOO .... it 
> finally works ;) I was able to connect to my Rdv/Relay!
> 
> To sum up I had two problems:
> 1) Using hostnames as seeding URI did not work.
>    Only IPs are valid!
> 2) Running a Rdv/Relay behind a router with portforwarding does not work!
>    The server MUST have an Internet addressable IP for JXTA to work.
> 
> I didn't read anything like that yet about JXTA anywhere! It would be 
> great if some JXTA developers could verify this and if it is true put it 
> on the WIKI!
> 
> Thanks for all your support!
> Vince
> 
> 
> Mark S. Petrovic wrote:
> >On Tue, Dec 05, 2006 at 06:10:01PM +0100, [email protected] wrote:
> >  
> >>I managed to run my private net in a subnet already but I still try to 
> >>get my private net up and running in the Internet. I even put my server 
> >>to another ISP. It is now located in a DMZ at my company. Before it was 
> >>located behind a router with portforwarding which I guess is the problem 
> >>in both cases!
> >>    
> >
> >I'd try to help with this port-forwarding situation, but I have no
> >experience with these sorts of things.  I do have an internal bias
> >against trusting what I perceive to be consumer grade routers always
> >doing the right thing.
> >
> >  
> >>When I browse to http://83.64.248.67:9901/ where my Rdv is running on I 
> >>get the following message:
> >>JXTAHELLO tcp://10.1.14.132:60762 tcp://192.168.13.6:9901 
> >>urn:jxta:uuid-59616261646162614E504720503250330DC9C4666CFF461CAA6DF1F86AFAC32003 
> >>0 1.1
> >>
> >>tcp://10.1.14.132:60762 is the IP I am connecting from and 
> >>tcp://192.168.13.6:9901 is the local IP of the jxta server. Now could  
> >>the problem be that the server IP should actually be 
> >>tcp://83.64.248.67:9901/ and that this might confuses JXTA? What could I 
> >>do to solve this? Directly connecting the server to the Internet seems 
> >>to be the only solution!?
> >>    
> >
> >You lost me on this one.  Is the net-83 host the public interface on a
> >home lan, and the net-192 host is the forwarded-to host?
> >
> >
> >  
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]

-- 
Mark S. Petrovic
Pasadena, CA 
http://www.petrovic.org