All TCPIP Connections No Longer Connect
- From: "Ross Culver" <rculver@xxxxxxxxxxxxxxx>
- Date: Thu, 27 Mar 2008 08:16:43 -0500
There are a lot of variables in this mess, so it may not be that easy to
explain.
Basically, all my ODBC connections to SQL2K5 which have been in place and
working for more than a year suddenly no longer work. If I switch the local
machines' connections to Named Pipes, they work. My remote machines which
exist on a different IP base (10.0.1.x versus home = 10.0.0.x) won't connect
anymore using either TCPIP or Named Pipes (sometimes, I still have a couple
of machines that continue to be exceptions).
Setting the remote machines aside for now, what would prevent an ODBC
connection from connecting via TCPIP and not Named Pipes? Local & Remote
connections are set to use both in the Surface Area Manager configurations.
Thanks,
Ross
.
- Prev by Date: Re: Progress ODBC Connection Problem
- Next by Date: Re: Calling an AS400 program using OPENQUERY on SQL Server 2000
- Previous by thread: ODBC DSN created via script is not visible in "ODBC Datasource Administrator"
- Next by thread: Re: Calling an AS400 program using OPENQUERY on SQL Server 2000
- Index(es):
Relevant Pages
|
Loading
