Trouble to get connected...

[Bernie]

I've run into trouble to get connected to a SQL-server on some machines at
a clients site. All machines are W2k+SP3 and have their OS and programfiles
installed from the same image(!).

What happens is that neither ADO nor ODBC connects using SQL-server verification.
With NT authentication it's possible to connect though. Unfortunatly the
client's software needs SQL-server verification...

When trying to set up an ODBC-DSN I get an error saying

SQL State 08004
Error 4062

I've looked up these in BOL but they don't give much.

SQL-server works as it should (most of the client machines run it flawlessly)
so I've excluded any settings there. Since the machines are setup from the
same image and hardware are identical as well and most of them work I'm beginning
to think of some hardware failures.

Some times ago I had a similar problem on a few machines. The refused to
connect no matter if the server name or IP-address was used. Then the problem
was solved if a DSN was setup with port 1433 explicitly stated.
The DSN could then be removed(!) ADO still connected willingly, but not before
a DNS had existed.

This seem more than strange to me. I mean, there are never any problem to
access a SQL-server as soon as you know it's IP-address and have a valid
username and password to it (with SQL-server verification enabled).

Anyone out there who can give me a hint on what to do next??? Some sequrity
issues on NT or....

Bernie

[Another Dude]

I am not sure if these machines that are having problems are user machines
but if they are you might want to check to make sure they are not changing
their computer names. I know it's not much help but it is a thought.

"Bernie" <magnus.bernroth@rejlers.se> wrote:
>
>I've run into trouble to get connected to a SQL-server on some machines
at
>a clients site. All machines are W2k+SP3 and have their OS and programfiles
>installed from the same image(!).
>
>What happens is that neither ADO nor ODBC connects using SQL-server verification.
>With NT authentication it's possible to connect though. Unfortunatly the
>client's software needs SQL-server verification...
>
>When trying to set up an ODBC-DSN I get an error saying
>
>SQL State 08004
>Error 4062
>
>I've looked up these in BOL but they don't give much.
>
>SQL-server works as it should (most of the client machines run it flawlessly)
>so I've excluded any settings there. Since the machines are setup from the
>same image and hardware are identical as well and most of them work I'm
beginning
>to think of some hardware failures.
>
>Some times ago I had a similar problem on a few machines. The refused to
>connect no matter if the server name or IP-address was used. Then the problem
>was solved if a DSN was setup with port 1433 explicitly stated.
>The DSN could then be removed(!) ADO still connected willingly, but not
before
>a DNS had existed.
>
>This seem more than strange to me. I mean, there are never any problem to
>access a SQL-server as soon as you know it's IP-address and have a valid
>username and password to it (with SQL-server verification enabled).
>
>Anyone out there who can give me a hint on what to do next??? Some sequrity
>issues on NT or....
>
>Bernie
>