cant connect to SQL2K running on W2K3SVR but can connect to SQL2K running W2KSVR with same

Hi,
I can't connect using an OLE DB connection string to SQL2K Server (SP3)
running on a Windows2003 Server, but using the same connection string (with
the address changed of course), I can connect to SQL2K Server (SP3) running
on Windows2000 Server.
I figure it must be a security issue on the W2K3 box. The logins and users
were created correctly with the correct passwords as I can connect to the
W2K3 box via Enterprise Manager just fine. The connection is set to TCP/IP
on port 1433 (default).
an example of my connection string (it is in a web application running on a
different server):
Application("dbconnstring") ="Provider=sqloledb;Data
Source=10.10.10.1;Network Library=DBMSSOCN;Initial Catalog=mydatabase;User
ID=mylogin;Password=mypassword;"
The only thing that changed is the IP address of the Win2003 server. I can
ping the server from either direction. I can scan port 1433 just fine with
a port scanner.
I am new to 2003 server, so I figure there must be a security setting
somewhere, but I haven't a clue where to look!
Any help would be appreciated!
TIA
Dave
.Hi Dave
> I can't connect using an OLE DB connection string to SQL2K Server (SP3)
> running on a Windows2003 Server, but using the same connection string
(with
> the address changed of course), I can connect to SQL2K Server (SP3)
running
> on Windows2000 Server.
> I figure it must be a security issue on the W2K3 box. The logins and
users
> were created correctly with the correct passwords as I can connect to the
> W2K3 box via Enterprise Manager just fine. The connection is set to
TCP/IP
> on port 1433 (default).
> an example of my connection string (it is in a web application running on
a
> different server):
> Application("dbconnstring") ="Provider=sqloledb;Data
> Source=10.10.10.1;Network Library=DBMSSOCN;Initial Catalog=mydatabase;User
> ID=mylogin;Password=mypassword;"
> The only thing that changed is the IP address of the Win2003 server. I
can
> ping the server from either direction. I can scan port 1433 just fine
with
> a port scanner.
> I am new to 2003 server, so I figure there must be a security setting
> somewhere, but I haven't a clue where to look!
>
Are you sure EM is connecting using TCP?
Can you connect locally using isql or isqlw to 127.0.0.1 ? (check that the
SQL Server client network utility on the server has TCP/IP as an enabled
protocol).
By port scanner, what do you mean? Are you scanning it on the server or from
outside the machine? Can you show that the server is listening on port 1433?
Check the SQL Server server network utility is listening on port 1433. Use
"netstat -a -n" (or "netsh interface ip show tcpconn") to look for an entry
like...
TCP 0.0.0.0:1433 0.0.0.0:0 LISTENING
Try telnetting to the port, eg "telnet 127.0.0.1 1433". If it's listening on
port 1433 you should get a blank telnet screen. If it's not you'll get an
error like "Connecting To 127.0.0.1...Could not open a connection to host on
port 1434 : Connect failed"
Try the above from a remote machine to see if there's an issue with
connecting remotely.
Run the SQL Server Profiler and check the Security Audit->Audit Login, Audit
Login Failed, Audit Logout events.
Kind Regards, Howard|||Hi again,
I tried telnetting both on the server and remotely and I get the blank
screen. The problem is OLE-DB does not work on Win2003. I can connect my
.Net apps just fine though through the SQL connector and Enterprise Manager.
I enabled DTC on the Win2003 box to see if that would help (but it did not
help, as I figured) and rebooted.
Somehow, OLE-DB requests are being blocked by a security setting deep within
the bowels of Windows 2003.
I must not be alone on this problem as a staff of MCSEs & MCDBAs are
scratching their heads at the hosting company (name withheld)!
Whilest I wait for them to figure it out, where in SQL profiler is the
"security audit"?
Dave
"dammit Jim, I'm just a country programmer!"
--
"Howard Long" <howard@.howardlongxxx.com> wrote in message
news:camggl$gqh$1@.sparta.btinternet.com...
> Hi Dave
> > I can't connect using an OLE DB connection string to SQL2K Server (SP3)
> > running on a Windows2003 Server, but using the same connection string
> (with
> > the address changed of course), I can connect to SQL2K Server (SP3)
> running
> > on Windows2000 Server.
> >
> > I figure it must be a security issue on the W2K3 box. The logins and
> users
> > were created correctly with the correct passwords as I can connect to
the
> > W2K3 box via Enterprise Manager just fine. The connection is set to
> TCP/IP
> > on port 1433 (default).
> >
> > an example of my connection string (it is in a web application running
on
> a
> > different server):
> >
> > Application("dbconnstring") ="Provider=sqloledb;Data
> > Source=10.10.10.1;Network Library=DBMSSOCN;Initial
Catalog=mydatabase;User
> > ID=mylogin;Password=mypassword;"
> >
> > The only thing that changed is the IP address of the Win2003 server. I
> can
> > ping the server from either direction. I can scan port 1433 just fine
> with
> > a port scanner.
> > I am new to 2003 server, so I figure there must be a security setting
> > somewhere, but I haven't a clue where to look!
> >
> Are you sure EM is connecting using TCP?
> Can you connect locally using isql or isqlw to 127.0.0.1 ? (check that the
> SQL Server client network utility on the server has TCP/IP as an enabled
> protocol).
> By port scanner, what do you mean? Are you scanning it on the server or
from
> outside the machine? Can you show that the server is listening on port
1433?
> Check the SQL Server server network utility is listening on port 1433. Use
> "netstat -a -n" (or "netsh interface ip show tcpconn") to look for an
entry
> like...
> TCP 0.0.0.0:1433 0.0.0.0:0 LISTENING
> Try telnetting to the port, eg "telnet 127.0.0.1 1433". If it's listening
on
> port 1433 you should get a blank telnet screen. If it's not you'll get an
> error like "Connecting To 127.0.0.1...Could not open a connection to host
on
> port 1434 : Connect failed"
> Try the above from a remote machine to see if there's an issue with
> connecting remotely.
> Run the SQL Server Profiler and check the Security Audit->Audit Login,
Audit
> Login Failed, Audit Logout events.
> Kind Regards, Howard
>|||"Dave" <dave(delete_this)@.miraclecatDELETETHISTOO.com> wrote in message
news:%23NhiEGuUEHA.2356@.TK2MSFTNGP10.phx.gbl...
> Hi again,
> I tried telnetting both on the server and remotely and I get the blank
> screen. The problem is OLE-DB does not work on Win2003. I can connect my
> .Net apps just fine though through the SQL connector and Enterprise
Manager.
> I enabled DTC on the Win2003 box to see if that would help (but it did not
> help, as I figured) and rebooted.
> Somehow, OLE-DB requests are being blocked by a security setting deep
within
> the bowels of Windows 2003.
> I must not be alone on this problem as a staff of MCSEs & MCDBAs are
> scratching their heads at the hosting company (name withheld)!
> Whilest I wait for them to figure it out, where in SQL profiler is the
> "security audit"?
When Profiler has opened, File->New->Trace, enter your details. In the
Events tab, add the Security Audit /Audit Login & Audit Login failed. The
trace will help you identify the fault.
I was wondering if it is trying to use integrated security to connect. Try
setting up an AD account mylogin/mypassword on the W2K3 server and retrying.
Alternatively it could be the other way around, and you are using SQL Server
authentication, in which case you should check that the login exists in SQL
Server.
Any error messages?
Regards, Howard