You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Wei Jiang (JIRA)" <de...@db.apache.org> on 2005/08/06 17:53:35 UTC
[jira] Created: (DERBY-497) derby sees LOCALHOST and real hostname different
derby sees LOCALHOST and real hostname different
------------------------------------------------
Key: DERBY-497
URL: http://issues.apache.org/jira/browse/DERBY-497
Project: Derby
Type: Bug
Components: JDBC
Versions: 10.1.1.0
Environment: Windows xp
Reporter: Wei Jiang
Priority: Minor
If you start derby using the default script (default as localhost), then try to connect the database, the connection url must be localhost (literally), can not be the real name of the computer.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Commented: (DERBY-497) derby sees LOCALHOST and real hostname different
Posted by "Kathey Marsden (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-497?page=comments#action_12317854 ]
Kathey Marsden commented on DERBY-497:
--------------------------------------
This is not a bug. Network Server starts up listenning on the loopback address only so that remote unsecure accesss is not granted by default on start up.
> derby sees LOCALHOST and real hostname different
> ------------------------------------------------
>
> Key: DERBY-497
> URL: http://issues.apache.org/jira/browse/DERBY-497
> Project: Derby
> Type: Bug
> Components: JDBC
> Versions: 10.1.1.0
> Environment: Windows xp
> Reporter: Wei Jiang
> Priority: Minor
>
> If you start derby using the default script (default as localhost), then try to connect the database, the connection url must be localhost (literally), can not be the real name of the computer.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Closed: (DERBY-497) derby sees LOCALHOST and real hostname different
Posted by "Jeremy Boynes (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-497?page=all ]
Jeremy Boynes closed DERBY-497:
-------------------------------
Resolution: Invalid
By default Derby binds just to the localhost address (127.0.0.1) rather than IN_ANY (0.0.0.0) to restrict access to just being from the local machine. This is intentional. Additional interfaces can be specified during startup to allow remote access.
> derby sees LOCALHOST and real hostname different
> ------------------------------------------------
>
> Key: DERBY-497
> URL: http://issues.apache.org/jira/browse/DERBY-497
> Project: Derby
> Type: Bug
> Components: JDBC
> Versions: 10.1.1.0
> Environment: Windows xp
> Reporter: Wei Jiang
> Priority: Minor
>
> If you start derby using the default script (default as localhost), then try to connect the database, the connection url must be localhost (literally), can not be the real name of the computer.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira