<br><font size=2 face="sans-serif">I tried to set the variable with the
bash command but no luck, I got again the same behaviour... In fact I forgot
to tell you a thing: we also have an AG 3.0 venueserver/client with the
same subnet/configuration: the 2.4 server has ip xxx.xxx.xxx.50, the 3.0
server xxx.xxx.xxx.51, but with the AG 3.0 venueserver all seems working
well... Which could be the problem with the 2.4? Some authentication problem?
(I tried with both Identity and Service certificates, but no luck.</font>
<br><font size=2 face="sans-serif">I also tried to use in my client the
same certificate that I use for the server, but again i wasn't able to
connect to venue lobby).</font>
<br><font size=2 face="sans-serif">I have no clue at this time....</font>
<br>
<br>
<br><font size=2><tt>"Thomas D. Uram" <turam@mcs.anl.gov>
scritti il 08/05/2006 19.05.53<br>
<br>
> You can also use the IP address. How you set it depends on the
shell <br>
> you use:<br>
> <br>
> For bash:<br>
> export GLOBUS_HOSTNAME=140.10.10.10<br>
> <br>
> For csh:<br>
> set GLOBUS_HOSTNAME 140.10.10.10<br>
> <br>
> Tom<br>
> <br>
> <br>
> Fabrizio.Berdondini@prototipo.it wrote:<br>
> ><br>
> > Thank you Thomas, just 2 questions: our server machine as far
as now <br>
> > doesn't have a public hostname, just a public IP. Could this
be a <br>
> > problem? Second: how can I set the globus_hostname variable for
a SUSE <br>
> > 10 machine?<br>
> > Thank you as always for your help.<br>
> > Bye,<br>
> > Faber B.<br>
> ><br>
> > "Thomas D. Uram" <turam@mcs.anl.gov> scritti
il 08/05/2006 18.50.55<br>
> ><br>
> > ><br>
> > > Entering a venue requires a SOAP call and an event client
<br>
> > connection. I<br>
> > > expect that the<br>
> > > SOAP call is being made to the public hsotname, but the
event client<br>
> > > connection is<br>
> > > being attempted on the internal hostname. You can
force the use of a<br>
> > > particular hostname<br>
> > > by setting the GLOBUS_HOSTNAME environment variable before
running the<br>
> > > VenueServer. In your case, I would set it to the public
hostname.<br>
> > ><br>
> > > If problems persist, let us know.<br>
> > ><br>
> > > Tom<br>
> > ><br>
> > ><br>
> > > Fabrizio.Berdondini@prototipo.it wrote:<br>
> > > ><br>
> > > > Hello all,<br>
> > > > i'm having some problems with permissions (i guess
so) while <br>
> > trying to<br>
> > > > enter the venues on a AG 2.4 VenueServer. I'm going
to explain better<br>
> > > > what's happening. We had first configurated the venue
server/clients<br>
> > > > inside our LAN and tested it for quite two months.
After that we put<br>
> > > > our server onto a public IP (without changing anything
in the server<br>
> > > > configuration). From this moment onwards we are no
more able to reach<br>
> > > > the venues: on the client we receive a message saying
that we are not<br>
> > > > able to connect to the lobby venue. We tried to launch
a venue client<br>
> > > > onto the same machine running the venueserver and we
successfully<br>
> > > > connected it to the lobby venue on the server. After
this we tried<br>
> > > > again to connect the other clients to the lobby on
the venue server:<br>
> > > > we received the same error, but looking inside the
venue with the <br>
> > only<br>
> > > > venueclient connected to it (the one running on the
same machine that<br>
> > > > runs the venueserver) we saw as many instances of the
client as the<br>
> > > > number of trials we did to log to that venue.<br>
> > > > How could we solve this problem?<br>
> > > > Thank you in advance,<br>
> > > > Faber B.<br>
</tt></font>