resolution to the client correctly set up. If not I get the following
error:
SQLState: 08S01
SQLError: 0
Message: hostname : hostname
Where "hostname" is the client host name. It doesn't seem to matter if
I
use an IP address or hostname in my connection URL. When searching the
net,
I have seen a similar error, but not exactly the same, where the
message is
"Hostname: hostname not found" (once again, here "hostname" is the
client
machine) where they suggested the issue was the DNS name conflict.
I found the error goes away if the client machine's hostname match the
DNS
name used for the same IP addess that the DB server is using. One
work-around is to set hostname on the client to the IP address being
used.
I know the right thing to do is set the hostname and the DNS name
lookup the
same, but I have a customer who doesn't want to do this. They didn't
have to
for 2003, and they don't want to for 2005. Sigh. Is there a way to
disable
this feature?Hi Mark
It is not clear what exactly the problem is here. Is the problem that you
have renamed the server without changing the instance name? In which case
you need to drop the server and re-create it as described in
http://msdn.microsoft.com/library/d...nstall_5r8f.asp
John
"Mark Delaney" <drsparc@.gmail.comwrote in message
news:1167352406.739648.91440@.s34g2000cwa.googlegro ups.com...
Quote:
Originally Posted by
When using the MS SQL 2005 JDBC driver, I now need to have the DNS name
resolution to the client correctly set up. If not I get the following
error:
>
SQLState: 08S01
SQLError: 0
Message: hostname : hostname
>
Where "hostname" is the client host name. It doesn't seem to matter if
I
use an IP address or hostname in my connection URL. When searching the
net,
I have seen a similar error, but not exactly the same, where the
message is
"Hostname: hostname not found" (once again, here "hostname" is the
client
machine) where they suggested the issue was the DNS name conflict.
>
I found the error goes away if the client machine's hostname match the
DNS
name used for the same IP addess that the DB server is using. One
work-around is to set hostname on the client to the IP address being
used.
>
I know the right thing to do is set the hostname and the DNS name
lookup the
same, but I have a customer who doesn't want to do this. They didn't
have to
for 2003, and they don't want to for 2005. Sigh. Is there a way to
disable
this feature?
>
It isn't the database server name that is in question. The hostname of
the machine where the client is running is the issue. If I try and
make a JDBC connection from a machine where the hostname doesn't match
what the DB server's DNS lists it as, then the connection is rejected.
This didn't happen with the 2003 JDBC driver, so it looks like a new
security feature. But I would like to disable it.
- Mark
John Bell wrote:
Quote:
Originally Posted by
Hi Mark
>
It is not clear what exactly the problem is here. Is the problem that you
have renamed the server without changing the instance name? In which case
you need to drop the server and re-create it as described in
http://msdn.microsoft.com/library/d...nstall_5r8f.asp
>
John
>
"Mark Delaney" <drsparc@.gmail.comwrote in message
news:1167352406.739648.91440@.s34g2000cwa.googlegro ups.com...
Quote:
Originally Posted by
When using the MS SQL 2005 JDBC driver, I now need to have the DNS name
resolution to the client correctly set up. If not I get the following
error:
SQLState: 08S01
SQLError: 0
Message: hostname : hostname
Where "hostname" is the client host name. It doesn't seem to matter if
I
use an IP address or hostname in my connection URL. When searching the
net,
I have seen a similar error, but not exactly the same, where the
message is
"Hostname: hostname not found" (once again, here "hostname" is the
client
machine) where they suggested the issue was the DNS name conflict.
I found the error goes away if the client machine's hostname match the
DNS
name used for the same IP addess that the DB server is using. One
work-around is to set hostname on the client to the IP address being
used.
I know the right thing to do is set the hostname and the DNS name
lookup the
same, but I have a customer who doesn't want to do this. They didn't
have to
for 2003, and they don't want to for 2005. Sigh. Is there a way to
disable
this feature?
"Mark Delaney" <drsparc@.gmail.comwrote in message
news:1167431063.785847.116630@.48g2000cwx.googlegro ups.com...
Quote:
Originally Posted by
Hey,
>
It isn't the database server name that is in question. The hostname of
the machine where the client is running is the issue. If I try and
make a JDBC connection from a machine where the hostname doesn't match
what the DB server's DNS lists it as, then the connection is rejected.
This didn't happen with the 2003 JDBC driver, so it looks like a new
security feature. But I would like to disable it.
>
>
- Mark
I am not sure why this would cause a problem when connecting to the server,
there must be some conversation being carried out! I would expect it to
cause problems for other applications as well, therefore you may want to
resolve the issue for those. I assume you can't change the hosts file on the
server? Your post in microsoft.public.sqlserver.jdbcdriver has had no
replies yet!
John
1) [Thread[pool-2-thread-1,5,main],