Search Mailing List Archives


Limit search to: Subject & Body Subject Author
Sort by: Reverse Sort
Limit to: All This Week Last Week This Month Last Month
Select Date Range     through    

[protege-owl] [protege-discussion] Access to Protégé's Server

Martin Malaquina martin.malaquina at active.com.uy
Mon Aug 10 07:33:59 PDT 2009


I attach a diagram that describes what is happening. I tried what you said to me, but I have not been successful. 
I think it can be a problem with the configuration of the router. Do you have any idea that problems can be what are causing this?.


-----Mensaje original-----
De: protege-owl-bounces at lists.stanford.edu [mailto:protege-owl-bounces at lists.stanford.edu] En nombre de Timothy Redmond
Enviado el: jueves, 06 de agosto de 2009 06:35 p.m.
Para: User support for the Protege-OWL editor
Asunto: Re: [protege-owl] [protege-discussion] Access to Protégé's Server


> Then configure the NAT to access ports 5200 and 5100. 

If you are in the NAT situation then this is a relatively advanced
technique requiring a good understanding of networks.  I would recommend
you try a server on a public ip address.

> > 
> > Then I try to connecting through a machine with public ip and can't do this. (the logs I have attached, to this mail).

The logs are telling a very simple story - the client could not connect
to the rmiregistry.  The most obvious possibility is that the
rmiregistry program is not running.  You need to have the command 

	rmiregistry 5200

(if I understand your port opts) running.  If the rmiregistry is not
running you will probably also be seeing errors on the server console.

If the rmiregistry is running (in particular the server is successfully
connecting to the rmiregistry without errors) then something on your
network is either blocking the connection  or is not correctly
forwarding the connection.  If  you can you should first check that you
can access the rmiregistry on the LAN with telnet.  That is, on some
machine on the lan but other than the protege server machine, you should
run the command (see [1])

	telnet [server ip address] 5200

and see if it connects.  If it does not connect then the problem might
be a firewall on the protege server  machine.

If you can connect on the LAN and you are using NAT then it is quite
possible that the problem is that the router is misconfigured.  But it
is also possible that there is some other firewall between the protege
server and the protege client  that is blocking the connection.  In any
case, at this point we are talking about a network configuration
problem.

There are a large number of variables to consider in this discussion. If
you are still having trouble you might want to consider sending a
diagram such as [2] and describing what you thing is happening in that
context.

-Timothy



[1]
http://protegewiki.stanford.edu/index.php/Protege_Client-Server_Tutorial#Troubleshooting
[2] http://protegewiki.stanford.edu/images/7/7c/RMIProtocol04.png

On Thu, 2009-08-06 at 16:31 -0300, Martin Malaquina wrote:
> In a machine with private ip , run the Protégé's server 
> 
> "PORTOPTS =- Dprotege.rmi.server.port = 5100 = 5200-Dprotege.rmi.registry.port. 
>   HOSTNAME =- Djava.rmi.server.hostname = 200.40.69.126 
> 
> Then configure the NAT to access ports 5200 and 5100. 
> 
> Then I try to connecting through a machine with public ip and can't do this. (the logs I have attached, to this mail). 
> 
> Any help to solve this problem, it would be very helpful. 
> 
> Greetings, 
> 
> Martín
> 
> -----Mensaje original-----
> De: protege-owl-bounces at lists.stanford.edu [mailto:protege-owl-bounces at lists.stanford.edu] En nombre de Timothy Redmond
> Enviado el: martes, 04 de agosto de 2009 03:17 p.m.
> Para: User support for Core Protege and the Protege-Frames editor
> CC: 'User support for the Protege-OWL editor'
> Asunto: Re: [protege-owl] [protege-discussion] Access to Protégé's Server
> 
> 
> Are you  sure that  the rmiregistry process is  running and on the right
> port?  We need more information like how  you started the server and the
> logs on both the client and the server.
> 
> I added a page for  troubleshooting problems with the client-server [1].
> It is very incomplete and currently  is just  a hodge-podge of things
> that  we have seen happen.
> 
> -Timothy
> 
> [1]
> http://protegewiki.stanford.edu/index.php/Troubleshooting_Client_Server_Connections
> 
> On Tue, 2009-08-04 at 11:39 -0300, Martin Malaquina wrote:
> > Hello everybody, 
> > 
> > I have a big problem. I can not connect through a Protégé's client to
> > Protégé's server ,the messsage  tells me "Unable to Connect to Server". 
> > 
> > To access the server, I use NAT, following the steps listed in the following
> > link http://protegewiki.stanford.edu/index.php/Protege_Client_Server_RMI,
> > but just keep happening the same problem. 
> > 
> > I Change the router configuration page as indicated. 
> > 
> > I Need help to solve this. Some help . . .
> > 
> > I am using Windows, Protege_3.4 build 537. 
> > 
> > Greetings.
> > 
> > _______________________________________________
> > protege-discussion mailing list
> > protege-discussion at lists.stanford.edu
> > https://mailman.stanford.edu/mailman/listinfo/protege-discussion
> > 
> > Instructions for unsubscribing: http://protege.stanford.edu/doc/faq.html#01a.03
> 
> _______________________________________________
> protege-owl mailing list
> protege-owl at lists.stanford.edu
> https://mailman.stanford.edu/mailman/listinfo/protege-owl
> 
> Instructions for unsubscribing: http://protege.stanford.edu/doc/faq.html#01a.03
> _______________________________________________
> protege-owl mailing list
> protege-owl at lists.stanford.edu
> https://mailman.stanford.edu/mailman/listinfo/protege-owl
> 
> Instructions for unsubscribing: http://protege.stanford.edu/doc/faq.html#01a.03

_______________________________________________
protege-owl mailing list
protege-owl at lists.stanford.edu
https://mailman.stanford.edu/mailman/listinfo/protege-owl

Instructions for unsubscribing: http://protege.stanford.edu/doc/faq.html#01a.03
-------------- next part --------------
A non-text attachment was scrubbed...
Name: RMIProtocol04.png
Type: image/png
Size: 66140 bytes
Desc: not available
URL: <http://mailman.stanford.edu/pipermail/protege-owl/attachments/20090810/e3c2bf13/attachment.png>


More information about the protege-owl mailing list