ODBC to SQL Server through DSN fails once in a while

Xref: TK2MSFTNGP08.phx.gbl microsoft.public.sqlserver.odbc:43808
Hello:
I have multiple ODBC connections to our SQL Server, and they are mostly
working well.
I have an issue once in a while with the connection when the DSN is not the
DSN used to create the linked table. For example, If the DSN is named the
same, but is connecting through IP address vs. Computer Name, the connection
will fail.
I just thought I'd post this to see if there are other similar situations,
maybe some ways around it?
Thanks,
Kyle
"Kyle McAdam" <kyle.mcadam@.sympatico.ca> wrote in message
news:Tw%dd.56921$JG5.927915@.news20.bellglobal.com. ..
> Hello:
> I have multiple ODBC connections to our SQL Server, and they are mostly
> working well.
> I have an issue once in a while with the connection when the DSN is not
the
> DSN used to create the linked table. For example, If the DSN is named the
> same, but is connecting through IP address vs. Computer Name, the
connection
> will fail.
> I just thought I'd post this to see if there are other similar situations,
> maybe some ways around it?
> Thanks,
> Kyle
In the DSN configuration, click Client Configuration and make sure TCP/IP is
checked as a protocol. You can also Alias a server name in this screen. I've
found that to work well.

ODBC to SQL Server through DSN fails once in a while

Xref: TK2MSFTNGP08.phx.gbl microsoft.public.sqlserver.odbc:43808
Hello:
I have multiple ODBC connections to our SQL Server, and they are mostly
working well.
I have an issue once in a while with the connection when the DSN is not the
DSN used to create the linked table. For example, If the DSN is named the
same, but is connecting through IP address vs. Computer Name, the connection
will fail.
I just thought I'd post this to see if there are other similar situations,
maybe some ways around it?
Thanks,
Kyle"Kyle McAdam" <kyle.mcadam@.sympatico.ca> wrote in message
news:Tw%dd.56921$JG5.927915@.news20.bellglobal.com...
> Hello:
> I have multiple ODBC connections to our SQL Server, and they are mostly
> working well.
> I have an issue once in a while with the connection when the DSN is not
the
> DSN used to create the linked table. For example, If the DSN is named the
> same, but is connecting through IP address vs. Computer Name, the
connection
> will fail.
> I just thought I'd post this to see if there are other similar situations,
> maybe some ways around it?
> Thanks,
> Kyle
In the DSN configuration, click Client Configuration and make sure TCP/IP is
checked as a protocol. You can also Alias a server name in this screen. I've
found that to work well.

odbc sql server does not exist or access denied

I just installed SQL 2005 on a backup/test server. When I connected with ODBC to the new server I lost all of my ODBC connections, even to the working server (SQL 2000). I did a full repair on XP and got the ODBC to connect. Why would connecting to SQL 2005 cause my ODBC to crash ?. I tried using SQL Native as well, with no joy to either server. My ODBC isn't working again. The problem began as being intermittent, i.e. connected one minute, lost connection the next. Now it's permanently disconnected and I'm not even sure the reinstall was a solution.

Take a look at - http://support.microsoft.com/kb/328306

Hope this helps

|||Also got the error from another machine "does not allow remote connections" when connecting to ODBC.

The fix was to ensure that SQL Server Surface Area Configuration (via Start / etc) , Remote Connections set to "Using both TCP/IP and named pipes" (which was already default in my instance), and instead of using the name of the server in the ODBC drop-down list, use the servier IP, i.e. 10.0.0.XXX.|||

Is your issue resolved? If so, please mark your question anwserred.

If you are able to connect using IP address, but not with machine name, most likely you have a DNS problem on your network.

odbc over internet

We are running an sql server database on a Windows 2000 server, aproximately
15 clients on our lan use odbc connections to connect with acces 2002 front
end. No problem. Then i came up with the idea to connect a home-worker via
internet, using a vpn tunnel over isdn. Somehow this vpn-over-isdn
connection is unstable, as a matter of fact only few records can be entered
before the connection is lost. Is this a limitation of odbc connections or
just a miserable isdn solution wich need to be replaced?"b.binnenweg" <bobby01@.nospamxs4all.nl> wrote in message
news:402e0d12$0$557$e4fe514c@.news.xs4all.nl...
> We are running an sql server database on a Windows 2000 server,
aproximately
> 15 clients on our lan use odbc connections to connect with acces 2002
front
> end. No problem. Then i came up with the idea to connect a home-worker via
> internet, using a vpn tunnel over isdn. Somehow this vpn-over-isdn
> connection is unstable, as a matter of fact only few records can be
entered
> before the connection is lost. Is this a limitation of odbc connections or
> just a miserable isdn solution wich need to be replaced?
>
That sounds like a connection issue... are you experiencing high latency
from the client to the server? Also, linked Access tables are not that
efficient and not recommended for WAN access.
Steve