I had this problem while our Dspace was in the internal network.

It had an internal addr 10.x.x.x, and an external IP, that would be translated to it's internal IP, to all outside requests.

  What was the problem with the handle:

Since you have an external IP you have to configure that external IP in the handle.net, but you cannot start the deamon because the machine has an internal IP, and not the one you providade to handle.net

  To test the handle server i did a little workaround. Don't know if all the users agree with this situation, or if there's a better situation, but i did the following:

On the configuration wizard, i gave the external IP, and sent the zip file to handle.net Then, I've changed in config.dct the "bind_address" the external IP to the 10.x.x.x Then, started the handle and everything was working. The only problem i had: When you are on the internal network and you acess you Dspace by it's internal IP, when acessing via handle, will go to it's external IP. Altough it's untested, you can avoid this by using it's name, instead the IP.

  Hope this helps,

  Marcelo

   Citando "E. Stuart Hicks" <[EMAIL PROTECTED]>:

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

We have a rather unorthidox firewall setup and I'm having problems
getting the DSpace handle.net server to work through it.

Basically, the DSpace server doesn't actually know what its
world-accessable IP is - it's on a 10. IP and has its traffic
translated/routed by a firewall.  This appears to cause problems with
the handle.net service and I'm not even able to home it properly.  Has
anyone encountered this before and been able to come up with a viable
solution that didn't require overhauling the network configuration?

Frankly, we would prefer to put the handle service on an entirely
separate box because this will not be the only DSpace instance that
we'll be hosting; however, that doesn't appear to be an option right
now.  Does anyone know if 1.5 will support this?

Any help at all is appreciated.  We have an end-of-the-week deadline to
meet and this is the final hurdle to overcome.


- ----------------------
E. Stuart Hicks
Access Manager / Systems Engineer
OhioLINK
[EMAIL PROTECTED]
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFG8CidqmBbivzHElIRAjC/AJ4+lT9TvjZFR0Fbooc8xn6szgpN9ACfQOEW
j/TtfpIqsIEqfSf83tbEldE=
=nku1
-----END PGP SIGNATURE-----


-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
DSpace-tech mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-tech






-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
DSpace-tech mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-tech

Reply via email to