db-derby-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Matt Sanford <mzsanf...@aol.com>
Subject Re: Derby cannot be bind to the IP address of the host in which Derby resides.
Date Tue, 13 Sep 2005 23:59:27 GMT

    I have seen similar issues on Linux hosts with overly-broad 
/etc/hosts files. I know on WinXP there is a similar file named 
C:\Windows\SYSTEM32\DRIVERS\ETC\HOSTS but I am not sure about Windows 
2000. The problem is when an /etc/hosts entry is matching the ip address 
and correcting your getByName. I do not know if this effects Windows the 
same but it is worth a check.

  -- Matt Sanford

wolfgang127us@yahoo.co.jp wrote:

>Hi there,
>I specified the host name by using the following code instead of
>NetworkServerControl server = new
>Then, error messages in derby.log were gone but I got two lines of 
>"Server is ready to accept connections on port 1527."
>and unfortunately, I still cannot access the Derby instance from remote.
>I tested whether the port is opened or not using telnet.
>>>From the same host, it's opened.
>>>From a remote host, it's NOT opened.
> Take an action against poverty
> http://pr.mail.yahoo.co.jp/whiteband/

When the going gets tough, the weird turn pro.
  -- Hunter S. Thompson

View raw message