Re: ODBC failing to connect
- From: "Michael Mastro" <MikeRM2XXX@xxxxxxxxxxxxxxxx>
- Date: Fri, 26 Jan 2007 10:18:06 -0500
Well looking at the Firewall logs I can see the it is opening the port then
2 seconds later terminating with a 0x80074E21. Still unable to figure a way
around this one.
Michael R. Mastro II
"Sue Hoegemeier" <Sue_H@xxxxxxxxxxxxx> wrote in message
news:0e3jr2dffad96n056htlmnpkrubqdvr49s@xxxxxxxxxx
Well at least it's narrowed down. Check the logs on your ISA
server. It looks like it's still being blocked there.
-Sue
On Thu, 25 Jan 2007 10:35:04 -0500, "Michael Mastro"
<MikeRM2XXX@xxxxxxxxxxxxxxxx> wrote:
I tried the following with still no luck.
First off I went into the SQL Server logs and found out that it is
listening
in on TCP port 2440, it also mentioned 2441.
I then went to the ISA server and created protocol that allows inbound and
outbound connections on 1433, 2440, and 2441. I created an access rule
that
allows any of the protected networks and the local host to access the new
protocol I created with the SQL server.
I went back to the SQL server machine, and started up the profiler to run
a
trace.
Back to the ISA machine, and opened up telnet and tried to connect to SQL
server machine via 1433, then 2440, then 2441. Each time connect failed.
I
also tried a static IP on the ODBC set for 2440. And each time as the
same
before.
I looked over the SQL Profiler trace and it does not even show any
connection attempts from the ISA machine.
Pinging and PathPinging show good connections. Plus a looking over the
ports on the SQL server machine show that it is listening on those ports.
Still scratching my head.
Michael R. Mastro II
"Sue Hoegemeier" <Sue_H@xxxxxxxxxxxxx> wrote in message
news:iejdr215njd7fp0taafif3lcsdb508i420@xxxxxxxxxx
It can be a lot of different things. Enable login auditing
or run profiler to see if it's actually connecting on the
SQL Server end. It just makes troubleshooting easier.
If it's a named instance, make sure you are specifying the
instance name.
You'd also want to check your ports and protocols - one way
to check is look in the SQL Server error log from when it
started up to determine what ports and protocols SQL Server
is listening on.
From the ISA server, try to telnet to the port SQL Server is
listening on. Make sure the client end (ISA) is using the
same port.
Make sure SQL Server is listening on the correct protocols
as well. Make sure you have TCP/IP enabled.
And then run through the following article:
Potential causes of the "SQL Server does not exist or access
denied" error message
http://support.microsoft.com/?id=328306
-Sue
On Tue, 23 Jan 2007 10:03:10 -0500, "Michael Mastro"
<MikeRM2XXX@xxxxxxxxxxxxxxxx> wrote:
Ok here is the problem. I am trying to set up logging on SQL 2005. Now
I
am trying to setup the OBDC on the ISA server and it is failing each
time.
It cannot reach the server. Every other computer in the domain can
access
the SQL server via OBDC. So what am I missing to do that on the ISA
server.
I am running ISA 2006 Enterprise, and have set the system policy to use
SQL
for logging. Plus I have a access rule that allows SQL through ISA.
Anyone
know what I missed?
TCP/IP is set up as dynamic, and I can ping the SQL Server.
The following is the failure I get from ODBC:
Connection failed:
SQLState: '01000'
SQL Server Error: 10065
[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]ConnectionOpen
(Connect()).
Connection Failed:
SQLState: '08001'
SQL Server Error: 17
[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]SQL Server does not
exist
or access denied.
Thanks,
Michael R. Mastro II
.
- References:
- Re: ODBC failing to connect
- From: Sue Hoegemeier
- Re: ODBC failing to connect
- From: Michael Mastro
- Re: ODBC failing to connect
- From: Sue Hoegemeier
- Re: ODBC failing to connect
- Prev by Date: Re: ODBC failing to connect
- Next by Date: Re: Connection issue across network
- Previous by thread: Re: ODBC failing to connect
- Next by thread: How to connect second instance if server has two instance?
- Index(es):
Relevant Pages
|
