You will probably have to also kill the java web start cache.  If you
don't have other web start apps installed just remove ~/.java.

If that doesn't work you always could bind the ip to a local interface.

Happy Hacking!

7-11

On Fri, 2007-03-16 at 07:49 +0100, Tim Verbois wrote:
> I tried that, but the java admin keeps connecting to the original ip 
> address.  Even when I change all the entries in de gconsole.j... file, 
> even then he keeps looking for the original ip. 
> 
> Tim
> 
> Yaron Zabary wrote:
> > Tim Verbois wrote:
> >> Hello,
> >>
> >> 90% of our team is located behind firewalls.  The only way to reach 
> >> servers is through ssh ports (2 hops).
> >> This implies that it is impossible to run the java tool on their pc.  
> >> I made a script that starts te tool on the backupserver in an ssh 
> >> session.  That way, it is possible to run it through an ssh X session 
> >> to a pc somewhere.  This works, but very very slow.
> >> Are there other possibilities?  I suppose a lot of organisations have 
> >> there backupserver behind firewalls?
> >>
> >
> >   Haven't tried that, but you could try and forward the application's 
> > port via ssh (or putty) and try to point the browser at localhost. 
> > Look at appendix B of the Admin guide. Table 119 lists ports 9000, 
> > 9001 and 2638 for console access. For a Unix desktop, that should be 
> > 'ssh -L9000:nsrhost:9000 -L9001:nsrhost:9001 -L2638:nsrhost:2638 
> > root@nsrhost'.
> >
> 

To sign off this list, send email to listserv AT listserv.temple DOT edu and 
type "signoff networker" in the body of the email. Please write to 
networker-request AT listserv.temple DOT edu if you have any problems with this 
list. You can access the archives at 
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER