I'm trying to determine if this error
(http://support.microsoft.com/kb/811274/en-us) has been fixed in SQL2000 SP4
or the SP4 cumulative hotfix. I can't find it listed on MSDN, but it's
rather difficult to scroll through the dozens of numbers looking for one
specific fix. Note to Microsoft: Why don't you make the fixed KB numbers
searchable?Hi Ron
I think this was fixed in build 990 which is included in SP4
http://support.microsoft.com/kb/890200/EN-US/
John
"Ron Hinds" wrote:
> I'm trying to determine if this error
> (http://support.microsoft.com/kb/811274/en-us) has been fixed in SQL2000 SP4
> or the SP4 cumulative hotfix. I can't find it listed on MSDN, but it's
> rather difficult to scroll through the dozens of numbers looking for one
> specific fix. Note to Microsoft: Why don't you make the fixed KB numbers
> searchable?
>
>
Showing posts with label sp4. Show all posts
Showing posts with label sp4. Show all posts
Thursday, March 8, 2012
connection failed - ODBC from remote SQL SERVER
hello,
im trying to create an ODBC data source from a SQL SERVER 2005 database located in a remoted pc.
Client---->PC1 : win 2000 sp4, not sql server
Remote server-->PC2 : win 2000 sp4, sql server 2005 express
From the Command Prompt, im typing "ping PC2" successfully.
After, in the ODBC datasource administrator-->System DNS tab, i choose "sql server" as a new data source , and in the server box , i'm typing PC2/SQLEXPRESS.
In the next steps, im typing the user-passwords.
The error :
connection failed
...
[microsoft][odbc sql server driver][named pipes]ConnectionOpen(CreateFile()).
Connection failed:
SQLState: '08001'
..
Client unable to establish connection
What goes wrong?
I follow the same steps locally, and everything is OK.
Sorry for my bad english:cool:Here's an article (http://blogs.msdn.com/sql_protocols/archive/2006/03/23/558651.aspx) on troubleshooting connectivity issues on SQL Server Express.|||SQL 2005 does not support the Named Pipes protocol by default. I would choose a different protocol, preferably TCP/IP. You can set the protocol using the Client Configuration button on the second screen of the DSN definition in the ODBC DSN applet.
-PatP
im trying to create an ODBC data source from a SQL SERVER 2005 database located in a remoted pc.
Client---->PC1 : win 2000 sp4, not sql server
Remote server-->PC2 : win 2000 sp4, sql server 2005 express
From the Command Prompt, im typing "ping PC2" successfully.
After, in the ODBC datasource administrator-->System DNS tab, i choose "sql server" as a new data source , and in the server box , i'm typing PC2/SQLEXPRESS.
In the next steps, im typing the user-passwords.
The error :
connection failed
...
[microsoft][odbc sql server driver][named pipes]ConnectionOpen(CreateFile()).
Connection failed:
SQLState: '08001'
..
Client unable to establish connection
What goes wrong?
I follow the same steps locally, and everything is OK.
Sorry for my bad english:cool:Here's an article (http://blogs.msdn.com/sql_protocols/archive/2006/03/23/558651.aspx) on troubleshooting connectivity issues on SQL Server Express.|||SQL 2005 does not support the Named Pipes protocol by default. I would choose a different protocol, preferably TCP/IP. You can set the protocol using the Client Configuration button on the second screen of the DSN definition in the ODBC DSN applet.
-PatP
Wednesday, March 7, 2012
Connection Failed
I have added a domain global group to the local administrators group on server running sql 2000 with sp3a. The os on the server is w2k with sp4. The builtin\administrators group has sa rights. Yet members of the domain global group, after they logon to the server through a remote desktop session cannot open sql enterprise manager & connect to the local sql server (default instance). They get a message "Cannot open user default database. Login failed.." The users of the domain global group can connect to 2 other instances of of sql on the same server. The default instance is 8.00.818. The other 2 instances are 8.00.760. Thanks in advance for any advice.
*****************************************
* This message was posted via http://www.sqlmonster.com
*
* Report spam or abuse by clicking the following URL:
* http://www.sqlmonster.com/Uwe/Abuse...7b2402cee65437e
*****************************************Mike Pavel via SQLMonster.com (forum@.SQLMonster.com) writes:
> I have added a domain global group to the local administrators group on
> server running sql 2000 with sp3a. The os on the server is w2k with sp4.
> The builtin\administrators group has sa rights. Yet members of the
> domain global group, after they logon to the server through a remote
> desktop session cannot open sql enterprise manager & connect to the
> local sql server (default instance). They get a message "Cannot open
> user default database. Login failed.." The users of the domain global
> group can connect to 2 other instances of of sql on the same server. The
> default instance is 8.00.818. The other 2 instances are 8.00.760. Thanks
> in advance for any advice.
Each login on an SQL Server has a default database. Now, if for some
reason they cannot access that database, login fails. This can be
because they don't have permission to the database or that database is
offline of non-existing.
You can use the stored procedure sp_defaultdb to change the default db
for a user. Please see Books Online for syntax.
--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp|||The domain global group is part of the nt local admins group on the server running sql which makes it part of the built\administrators group in sql which has dbo access to all the databases on the sql server. The default database does exist. Thanks for reponding to my question. Any more thoughts?
*****************************************
* A copy of the whole thread can be found at:
* http://www.sqlmonster.com/Uwe/Forum...sql-server/5079
*
* Report spam or abuse by clicking the following URL:
* http://www.sqlmonster.com/Uwe/Abuse...bfff59ba325a2b2
*****************************************|||Mike Pavel via SQLMonster.com (forum@.SQLMonster.com) writes:
> The domain global group is part of the nt local admins group on the
> server running sql which makes it part of the built\administrators group
> in sql which has dbo access to all the databases on the sql server. The
> default database does exist. Thanks for reponding to my question. Any
> more thoughts?
Well, the error message you get, usually means that the default database
is not accessible. This can be because of several reasons:
o The database does not exist.
o The user does not have permission to the database.
o The database is offline or in single-user mode.
Can they log in through Query Analyzer or OSQL? In such case, change the
registration properties in Enterprise Manager.
--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp
Saturday, February 25, 2012
connection error
Hello,
We just add a new SQL2000 server (SQL-3, 192.168.100.3) w/SP4 installed.
We have old SQL-1(192.168.100.1) and SQL-2(192.168.100.2) servers.
All 3 servers are in same location.
SQL-1 and SQL-2 are in same domain, i.e. domain-a.
SQL-3 is another domain, i.e. domain-b.
SQL-3 can add SQL-1 and SQL-2 from 'New SQL Server Registration'.
(We did not add SQL-1 and SQL-2 on 'Client Network Utility')
But SQL-1 or SQL-2 can not add SQL-3 from 'New SQL Server Registration'.
We use 'Client Network Utility' add alias with TCP/IP 192.168.100.3 and port
1433.
Then we have the message 'SQL Server does not exist or access denied
connection open (Connect[])' during add SQL-3 from 'New SQL Server
Registration'.
SQL-3's 'Allow other SQL Server to connect remotelly to this SQL Server
using RPC' is checked.
Thanks
Hi
This could be a firewall issue or you may be using dynamic ports (if this is
a named instance for example). Have you checked which port SQL3 is listening
on? Can you telnet on the given port to SQL3 from the other servers? Have you
tried using IP addresses instead of DNS Names?
You may want to check out SQLPing at
http://www.sqlsecurity.com/Tools/FreeTools/tabid/65/Default.aspx
Also check the client protocols being used your service pack would indicate
TCP/IP should be first.
John
"Newbie" wrote:
> Hello,
> We just add a new SQL2000 server (SQL-3, 192.168.100.3) w/SP4 installed.
> We have old SQL-1(192.168.100.1) and SQL-2(192.168.100.2) servers.
> All 3 servers are in same location.
> SQL-1 and SQL-2 are in same domain, i.e. domain-a.
> SQL-3 is another domain, i.e. domain-b.
> SQL-3 can add SQL-1 and SQL-2 from 'New SQL Server Registration'.
> (We did not add SQL-1 and SQL-2 on 'Client Network Utility')
> But SQL-1 or SQL-2 can not add SQL-3 from 'New SQL Server Registration'.
> We use 'Client Network Utility' add alias with TCP/IP 192.168.100.3 and port
> 1433.
> Then we have the message 'SQL Server does not exist or access denied
> connection open (Connect[])' during add SQL-3 from 'New SQL Server
> Registration'.
> SQL-3's 'Allow other SQL Server to connect remotelly to this SQL Server
> using RPC' is checked.
> Thanks
We just add a new SQL2000 server (SQL-3, 192.168.100.3) w/SP4 installed.
We have old SQL-1(192.168.100.1) and SQL-2(192.168.100.2) servers.
All 3 servers are in same location.
SQL-1 and SQL-2 are in same domain, i.e. domain-a.
SQL-3 is another domain, i.e. domain-b.
SQL-3 can add SQL-1 and SQL-2 from 'New SQL Server Registration'.
(We did not add SQL-1 and SQL-2 on 'Client Network Utility')
But SQL-1 or SQL-2 can not add SQL-3 from 'New SQL Server Registration'.
We use 'Client Network Utility' add alias with TCP/IP 192.168.100.3 and port
1433.
Then we have the message 'SQL Server does not exist or access denied
connection open (Connect[])' during add SQL-3 from 'New SQL Server
Registration'.
SQL-3's 'Allow other SQL Server to connect remotelly to this SQL Server
using RPC' is checked.
Thanks
Hi
This could be a firewall issue or you may be using dynamic ports (if this is
a named instance for example). Have you checked which port SQL3 is listening
on? Can you telnet on the given port to SQL3 from the other servers? Have you
tried using IP addresses instead of DNS Names?
You may want to check out SQLPing at
http://www.sqlsecurity.com/Tools/FreeTools/tabid/65/Default.aspx
Also check the client protocols being used your service pack would indicate
TCP/IP should be first.
John
"Newbie" wrote:
> Hello,
> We just add a new SQL2000 server (SQL-3, 192.168.100.3) w/SP4 installed.
> We have old SQL-1(192.168.100.1) and SQL-2(192.168.100.2) servers.
> All 3 servers are in same location.
> SQL-1 and SQL-2 are in same domain, i.e. domain-a.
> SQL-3 is another domain, i.e. domain-b.
> SQL-3 can add SQL-1 and SQL-2 from 'New SQL Server Registration'.
> (We did not add SQL-1 and SQL-2 on 'Client Network Utility')
> But SQL-1 or SQL-2 can not add SQL-3 from 'New SQL Server Registration'.
> We use 'Client Network Utility' add alias with TCP/IP 192.168.100.3 and port
> 1433.
> Then we have the message 'SQL Server does not exist or access denied
> connection open (Connect[])' during add SQL-3 from 'New SQL Server
> Registration'.
> SQL-3's 'Allow other SQL Server to connect remotelly to this SQL Server
> using RPC' is checked.
> Thanks
connection error
Hello,
We just add a new SQL2000 server (SQL-3, 192.168.100.3) w/SP4 installed.
We have old SQL-1(192.168.100.1) and SQL-2(192.168.100.2) servers.
All 3 servers are in same location.
SQL-1 and SQL-2 are in same domain, i.e. domain-a.
SQL-3 is another domain, i.e. domain-b.
SQL-3 can add SQL-1 and SQL-2 from 'New SQL Server Registration'.
(We did not add SQL-1 and SQL-2 on 'Client Network Utility')
But SQL-1 or SQL-2 can not add SQL-3 from 'New SQL Server Registration'.
We use 'Client Network Utility' add alias with TCP/IP 192.168.100.3 and port
1433.
Then we have the message 'SQL Server does not exist or access denied
connection open (Connect[])' during add SQL-3 from 'New SQL Server
Registration'.
SQL-3's 'Allow other SQL Server to connect remotelly to this SQL Server
using RPC' is checked.
ThanksHi
This could be a firewall issue or you may be using dynamic ports (if this is
a named instance for example). Have you checked which port SQL3 is listening
on? Can you telnet on the given port to SQL3 from the other servers? Have yo
u
tried using IP addresses instead of DNS Names?
You may want to check out SQLPing at
http://www.sqlsecurity.com/Tools/Fr...65/Default.aspx
Also check the client protocols being used your service pack would indicate
TCP/IP should be first.
John
"Newbie" wrote:
> Hello,
> We just add a new SQL2000 server (SQL-3, 192.168.100.3) w/SP4 installed.
> We have old SQL-1(192.168.100.1) and SQL-2(192.168.100.2) servers.
> All 3 servers are in same location.
> SQL-1 and SQL-2 are in same domain, i.e. domain-a.
> SQL-3 is another domain, i.e. domain-b.
> SQL-3 can add SQL-1 and SQL-2 from 'New SQL Server Registration'.
> (We did not add SQL-1 and SQL-2 on 'Client Network Utility')
> But SQL-1 or SQL-2 can not add SQL-3 from 'New SQL Server Registration'.
> We use 'Client Network Utility' add alias with TCP/IP 192.168.100.3 and po
rt
> 1433.
> Then we have the message 'SQL Server does not exist or access denied
> connection open (Connect[])' during add SQL-3 from 'New SQL Server
> Registration'.
> SQL-3's 'Allow other SQL Server to connect remotelly to this SQL Server
> using RPC' is checked.
> Thanks
We just add a new SQL2000 server (SQL-3, 192.168.100.3) w/SP4 installed.
We have old SQL-1(192.168.100.1) and SQL-2(192.168.100.2) servers.
All 3 servers are in same location.
SQL-1 and SQL-2 are in same domain, i.e. domain-a.
SQL-3 is another domain, i.e. domain-b.
SQL-3 can add SQL-1 and SQL-2 from 'New SQL Server Registration'.
(We did not add SQL-1 and SQL-2 on 'Client Network Utility')
But SQL-1 or SQL-2 can not add SQL-3 from 'New SQL Server Registration'.
We use 'Client Network Utility' add alias with TCP/IP 192.168.100.3 and port
1433.
Then we have the message 'SQL Server does not exist or access denied
connection open (Connect[])' during add SQL-3 from 'New SQL Server
Registration'.
SQL-3's 'Allow other SQL Server to connect remotelly to this SQL Server
using RPC' is checked.
ThanksHi
This could be a firewall issue or you may be using dynamic ports (if this is
a named instance for example). Have you checked which port SQL3 is listening
on? Can you telnet on the given port to SQL3 from the other servers? Have yo
u
tried using IP addresses instead of DNS Names?
You may want to check out SQLPing at
http://www.sqlsecurity.com/Tools/Fr...65/Default.aspx
Also check the client protocols being used your service pack would indicate
TCP/IP should be first.
John
"Newbie" wrote:
> Hello,
> We just add a new SQL2000 server (SQL-3, 192.168.100.3) w/SP4 installed.
> We have old SQL-1(192.168.100.1) and SQL-2(192.168.100.2) servers.
> All 3 servers are in same location.
> SQL-1 and SQL-2 are in same domain, i.e. domain-a.
> SQL-3 is another domain, i.e. domain-b.
> SQL-3 can add SQL-1 and SQL-2 from 'New SQL Server Registration'.
> (We did not add SQL-1 and SQL-2 on 'Client Network Utility')
> But SQL-1 or SQL-2 can not add SQL-3 from 'New SQL Server Registration'.
> We use 'Client Network Utility' add alias with TCP/IP 192.168.100.3 and po
rt
> 1433.
> Then we have the message 'SQL Server does not exist or access denied
> connection open (Connect[])' during add SQL-3 from 'New SQL Server
> Registration'.
> SQL-3's 'Allow other SQL Server to connect remotelly to this SQL Server
> using RPC' is checked.
> Thanks
Friday, February 10, 2012
Connecting to SQL server 7 behind ISA server
Hi,
I recently upgrade a WinNT 4 SP6a Proxy server to Win2K SP4 with ISA SP2. I
have to allow remote users to connect to a SQL server 7 SP4 on Winnt 4 SP6a
behind ISA. The IP is static. It was working fine with Proxy but now I have
the following with clients on the Web:
[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets] Network error and if I
try SQL Query Analyzer I have
Unable to connect to server xxx.xxx.xxx.xxx
ODBC:Msg 0, Level 16, State 1
[Microsoft][ODBC SQL Server Driver] Time out error
I have the ISA port 1433 and 1344 (for the apps running with SQL) opened and
listenning . If I run netstat -na on both servers, both show ports as
listenning. I can telnet the ISA external IP on both ports. ISA client is
installed on the SQL server.
I ran thru a similar problem when I configured it for the proxy 2 years ago
and don't remember what was the problem exactly. With the proxy, I had to
add wspclnt.ini in the sql server binn folder to map the port 1433 to the
proxy server and added a connection in SQL server network utility which was
mapped to the external IP of the Proxy. I tried it with and without and
there is no difference. I also remember that I had to use credtool on the
SQL server. Do I have to do it with ISA?
I'm familiar with ISA and i often have to open ports for apps and it works
fine so what is diffenrent for SQL server?
Any help would be greatly appreciated.
Thanks in advance.
Steve Amirault
Take the firewall client off the SQL server and make sure the default
gateway of the SQL server is the ISA server, if that is the route to the
internet. Did you make the Server Publishing Rule for the machine?
Scott Harding
MCSE, MCSA, A+, Network+
Microsoft MVP - Windows NT Server
"Steve" <as@.joe.ca> wrote in message
news:uqKNAmSsEHA.2660@.TK2MSFTNGP12.phx.gbl...
> Hi,
> I recently upgrade a WinNT 4 SP6a Proxy server to Win2K SP4 with ISA SP2.
I
> have to allow remote users to connect to a SQL server 7 SP4 on Winnt 4
SP6a
> behind ISA. The IP is static. It was working fine with Proxy but now I
have
> the following with clients on the Web:
> [Microsoft][ODBC SQL Server Driver][TCP/IP Sockets] Network error and if I
> try SQL Query Analyzer I have
> Unable to connect to server xxx.xxx.xxx.xxx
> ODBC:Msg 0, Level 16, State 1
> [Microsoft][ODBC SQL Server Driver] Time out error
> I have the ISA port 1433 and 1344 (for the apps running with SQL) opened
and
> listenning . If I run netstat -na on both servers, both show ports as
> listenning. I can telnet the ISA external IP on both ports. ISA client is
> installed on the SQL server.
> I ran thru a similar problem when I configured it for the proxy 2 years
ago
> and don't remember what was the problem exactly. With the proxy, I had to
> add wspclnt.ini in the sql server binn folder to map the port 1433 to the
> proxy server and added a connection in SQL server network utility which
was
> mapped to the external IP of the Proxy. I tried it with and without and
> there is no difference. I also remember that I had to use credtool on the
> SQL server. Do I have to do it with ISA?
> I'm familiar with ISA and i often have to open ports for apps and it works
> fine so what is diffenrent for SQL server?
> Any help would be greatly appreciated.
> Thanks in advance.
> Steve Amirault
>
|||Yes there is a Server rule. Guess what, by doing it the same way I did it
with the former proxy, it works. I disabled the server publishing rule,
added the wspcfg.ini file in the mssql7\binn folder and it works? At the
setup time and according to the situations I had with the ISA, I first
thought that it wouldn't work using the same settings as it was with the
proxy server but it appears that is not the case.
Thanks anyway.
Steve
"Scott Harding - MS MVP" <scrockel@.**NO_SPAM**hotmail.com> a crit dans le
message de news:OJeoP1TsEHA.3200@.TK2MSFTNGP09.phx.gbl...[vbcol=seagreen]
> Take the firewall client off the SQL server and make sure the default
> gateway of the SQL server is the ISA server, if that is the route to the
> internet. Did you make the Server Publishing Rule for the machine?
> --
> Scott Harding
> MCSE, MCSA, A+, Network+
> Microsoft MVP - Windows NT Server
> "Steve" <as@.joe.ca> wrote in message
> news:uqKNAmSsEHA.2660@.TK2MSFTNGP12.phx.gbl...
SP2.[vbcol=seagreen]
> I
> SP6a
> have
I[vbcol=seagreen]
> and
is[vbcol=seagreen]
> ago
to[vbcol=seagreen]
the[vbcol=seagreen]
> was
the[vbcol=seagreen]
works
>
|||Interesting...you shouldn't have to do that but it depends I think if the
SQL server is a Secure NAT client or not.
Scott Harding
MCSE, MCSA, A+, Network+
Microsoft MVP - Windows NT Server
"Steve" <as@.joe.ca> wrote in message
news:uplh6uUsEHA.3412@.TK2MSFTNGP14.phx.gbl...[vbcol=seagreen]
> Yes there is a Server rule. Guess what, by doing it the same way I did it
> with the former proxy, it works. I disabled the server publishing rule,
> added the wspcfg.ini file in the mssql7\binn folder and it works? At the
> setup time and according to the situations I had with the ISA, I first
> thought that it wouldn't work using the same settings as it was with the
> proxy server but it appears that is not the case.
> Thanks anyway.
> Steve
>
> "Scott Harding - MS MVP" <scrockel@.**NO_SPAM**hotmail.com> a crit dans le
> message de news:OJeoP1TsEHA.3200@.TK2MSFTNGP09.phx.gbl...
> SP2.
4[vbcol=seagreen]
if[vbcol=seagreen]
> I
opened[vbcol=seagreen]
> is
years[vbcol=seagreen]
> to
> the
which[vbcol=seagreen]
and
> the
> works
>
I recently upgrade a WinNT 4 SP6a Proxy server to Win2K SP4 with ISA SP2. I
have to allow remote users to connect to a SQL server 7 SP4 on Winnt 4 SP6a
behind ISA. The IP is static. It was working fine with Proxy but now I have
the following with clients on the Web:
[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets] Network error and if I
try SQL Query Analyzer I have
Unable to connect to server xxx.xxx.xxx.xxx
ODBC:Msg 0, Level 16, State 1
[Microsoft][ODBC SQL Server Driver] Time out error
I have the ISA port 1433 and 1344 (for the apps running with SQL) opened and
listenning . If I run netstat -na on both servers, both show ports as
listenning. I can telnet the ISA external IP on both ports. ISA client is
installed on the SQL server.
I ran thru a similar problem when I configured it for the proxy 2 years ago
and don't remember what was the problem exactly. With the proxy, I had to
add wspclnt.ini in the sql server binn folder to map the port 1433 to the
proxy server and added a connection in SQL server network utility which was
mapped to the external IP of the Proxy. I tried it with and without and
there is no difference. I also remember that I had to use credtool on the
SQL server. Do I have to do it with ISA?
I'm familiar with ISA and i often have to open ports for apps and it works
fine so what is diffenrent for SQL server?
Any help would be greatly appreciated.
Thanks in advance.
Steve Amirault
Take the firewall client off the SQL server and make sure the default
gateway of the SQL server is the ISA server, if that is the route to the
internet. Did you make the Server Publishing Rule for the machine?
Scott Harding
MCSE, MCSA, A+, Network+
Microsoft MVP - Windows NT Server
"Steve" <as@.joe.ca> wrote in message
news:uqKNAmSsEHA.2660@.TK2MSFTNGP12.phx.gbl...
> Hi,
> I recently upgrade a WinNT 4 SP6a Proxy server to Win2K SP4 with ISA SP2.
I
> have to allow remote users to connect to a SQL server 7 SP4 on Winnt 4
SP6a
> behind ISA. The IP is static. It was working fine with Proxy but now I
have
> the following with clients on the Web:
> [Microsoft][ODBC SQL Server Driver][TCP/IP Sockets] Network error and if I
> try SQL Query Analyzer I have
> Unable to connect to server xxx.xxx.xxx.xxx
> ODBC:Msg 0, Level 16, State 1
> [Microsoft][ODBC SQL Server Driver] Time out error
> I have the ISA port 1433 and 1344 (for the apps running with SQL) opened
and
> listenning . If I run netstat -na on both servers, both show ports as
> listenning. I can telnet the ISA external IP on both ports. ISA client is
> installed on the SQL server.
> I ran thru a similar problem when I configured it for the proxy 2 years
ago
> and don't remember what was the problem exactly. With the proxy, I had to
> add wspclnt.ini in the sql server binn folder to map the port 1433 to the
> proxy server and added a connection in SQL server network utility which
was
> mapped to the external IP of the Proxy. I tried it with and without and
> there is no difference. I also remember that I had to use credtool on the
> SQL server. Do I have to do it with ISA?
> I'm familiar with ISA and i often have to open ports for apps and it works
> fine so what is diffenrent for SQL server?
> Any help would be greatly appreciated.
> Thanks in advance.
> Steve Amirault
>
|||Yes there is a Server rule. Guess what, by doing it the same way I did it
with the former proxy, it works. I disabled the server publishing rule,
added the wspcfg.ini file in the mssql7\binn folder and it works? At the
setup time and according to the situations I had with the ISA, I first
thought that it wouldn't work using the same settings as it was with the
proxy server but it appears that is not the case.
Thanks anyway.
Steve
"Scott Harding - MS MVP" <scrockel@.**NO_SPAM**hotmail.com> a crit dans le
message de news:OJeoP1TsEHA.3200@.TK2MSFTNGP09.phx.gbl...[vbcol=seagreen]
> Take the firewall client off the SQL server and make sure the default
> gateway of the SQL server is the ISA server, if that is the route to the
> internet. Did you make the Server Publishing Rule for the machine?
> --
> Scott Harding
> MCSE, MCSA, A+, Network+
> Microsoft MVP - Windows NT Server
> "Steve" <as@.joe.ca> wrote in message
> news:uqKNAmSsEHA.2660@.TK2MSFTNGP12.phx.gbl...
SP2.[vbcol=seagreen]
> I
> SP6a
> have
I[vbcol=seagreen]
> and
is[vbcol=seagreen]
> ago
to[vbcol=seagreen]
the[vbcol=seagreen]
> was
the[vbcol=seagreen]
works
>
|||Interesting...you shouldn't have to do that but it depends I think if the
SQL server is a Secure NAT client or not.
Scott Harding
MCSE, MCSA, A+, Network+
Microsoft MVP - Windows NT Server
"Steve" <as@.joe.ca> wrote in message
news:uplh6uUsEHA.3412@.TK2MSFTNGP14.phx.gbl...[vbcol=seagreen]
> Yes there is a Server rule. Guess what, by doing it the same way I did it
> with the former proxy, it works. I disabled the server publishing rule,
> added the wspcfg.ini file in the mssql7\binn folder and it works? At the
> setup time and according to the situations I had with the ISA, I first
> thought that it wouldn't work using the same settings as it was with the
> proxy server but it appears that is not the case.
> Thanks anyway.
> Steve
>
> "Scott Harding - MS MVP" <scrockel@.**NO_SPAM**hotmail.com> a crit dans le
> message de news:OJeoP1TsEHA.3200@.TK2MSFTNGP09.phx.gbl...
> SP2.
4[vbcol=seagreen]
if[vbcol=seagreen]
> I
opened[vbcol=seagreen]
> is
years[vbcol=seagreen]
> to
> the
which[vbcol=seagreen]
and
> the
> works
>
Connecting to SQL server 7 behind ISA server
Hi,
I recently upgrade a WinNT 4 SP6a Proxy server to Win2K SP4 with ISA SP2. I
have to allow remote users to connect to a SQL server 7 SP4 on Winnt 4 SP6a
behind ISA. The IP is static. It was working fine with Proxy but now I have
the following with clients on the Web:
[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets] Network erro
r and if I
try SQL Query Analyzer I have
Unable to connect to server xxx.xxx.xxx.xxx
ODBC:Msg 0, Level 16, State 1
[Microsoft][ODBC SQL Server Driver] Time out error
I have the ISA port 1433 and 1344 (for the apps running with SQL) opened and
listenning . If I run netstat -na on both servers, both show ports as
listenning. I can telnet the ISA external IP on both ports. ISA client is
installed on the SQL server.
I ran thru a similar problem when I configured it for the proxy 2 years ago
and don't remember what was the problem exactly. With the proxy, I had to
add wspclnt.ini in the sql server binn folder to map the port 1433 to the
proxy server and added a connection in SQL server network utility which was
mapped to the external IP of the Proxy. I tried it with and without and
there is no difference. I also remember that I had to use credtool on the
SQL server. Do I have to do it with ISA?
I'm familiar with ISA and i often have to open ports for apps and it works
fine so what is diffenrent for SQL server?
Any help would be greatly appreciated.
Thanks in advance.
Steve AmiraultTake the firewall client off the SQL server and make sure the default
gateway of the SQL server is the ISA server, if that is the route to the
internet. Did you make the Server Publishing Rule for the machine?
Scott Harding
MCSE, MCSA, A+, Network+
Microsoft MVP - Windows NT Server
"Steve" <as@.joe.ca> wrote in message
news:uqKNAmSsEHA.2660@.TK2MSFTNGP12.phx.gbl...
> Hi,
> I recently upgrade a WinNT 4 SP6a Proxy server to Win2K SP4 with ISA SP2.
I
> have to allow remote users to connect to a SQL server 7 SP4 on Winnt 4
SP6a
> behind ISA. The IP is static. It was working fine with Proxy but now I
have
> the following with clients on the Web:
> [Microsoft][ODBC SQL Server Driver][TCP/IP Sockets] Network er
ror and if I
> try SQL Query Analyzer I have
> Unable to connect to server xxx.xxx.xxx.xxx
> ODBC:Msg 0, Level 16, State 1
> [Microsoft][ODBC SQL Server Driver] Time out error
> I have the ISA port 1433 and 1344 (for the apps running with SQL) opened
and
> listenning . If I run netstat -na on both servers, both show ports as
> listenning. I can telnet the ISA external IP on both ports. ISA client is
> installed on the SQL server.
> I ran thru a similar problem when I configured it for the proxy 2 years
ago
> and don't remember what was the problem exactly. With the proxy, I had to
> add wspclnt.ini in the sql server binn folder to map the port 1433 to the
> proxy server and added a connection in SQL server network utility which
was
> mapped to the external IP of the Proxy. I tried it with and without and
> there is no difference. I also remember that I had to use credtool on the
> SQL server. Do I have to do it with ISA?
> I'm familiar with ISA and i often have to open ports for apps and it works
> fine so what is diffenrent for SQL server?
> Any help would be greatly appreciated.
> Thanks in advance.
> Steve Amirault
>|||Yes there is a Server rule. Guess what, by doing it the same way I did it
with the former proxy, it works. I disabled the server publishing rule,
added the wspcfg.ini file in the mssql7\binn folder and it works? At the
setup time and according to the situations I had with the ISA, I first
thought that it wouldn't work using the same settings as it was with the
proxy server but it appears that is not the case.
Thanks anyway.
Steve
"Scott Harding - MS MVP" <scrockel@.**NO_SPAM**hotmail.com> a crit dans le
message de news:OJeoP1TsEHA.3200@.TK2MSFTNGP09.phx.gbl...
> Take the firewall client off the SQL server and make sure the default
> gateway of the SQL server is the ISA server, if that is the route to the
> internet. Did you make the Server Publishing Rule for the machine?
> --
> Scott Harding
> MCSE, MCSA, A+, Network+
> Microsoft MVP - Windows NT Server
> "Steve" <as@.joe.ca> wrote in message
> news:uqKNAmSsEHA.2660@.TK2MSFTNGP12.phx.gbl...
SP2.[vbcol=seagreen]
> I
> SP6a
> have
I[vbcol=seagreen]
> and
is[vbcol=seagreen]
> ago
to[vbcol=seagreen]
the[vbcol=seagreen]
> was
the[vbcol=seagreen]
works[vbcol=seagreen]
>|||Interesting...you shouldn't have to do that but it depends I think if the
SQL server is a Secure NAT client or not.
Scott Harding
MCSE, MCSA, A+, Network+
Microsoft MVP - Windows NT Server
"Steve" <as@.joe.ca> wrote in message
news:uplh6uUsEHA.3412@.TK2MSFTNGP14.phx.gbl...
> Yes there is a Server rule. Guess what, by doing it the same way I did it
> with the former proxy, it works. I disabled the server publishing rule,
> added the wspcfg.ini file in the mssql7\binn folder and it works? At the
> setup time and according to the situations I had with the ISA, I first
> thought that it wouldn't work using the same settings as it was with the
> proxy server but it appears that is not the case.
> Thanks anyway.
> Steve
>
> "Scott Harding - MS MVP" <scrockel@.**NO_SPAM**hotmail.com> a crit dans le
> message de news:OJeoP1TsEHA.3200@.TK2MSFTNGP09.phx.gbl...
> SP2.
4[vbcol=seagreen]
if[vbcol=seagreen]
> I
opened[vbcol=seagreen]
> is
years[vbcol=seagreen]
> to
> the
which[vbcol=seagreen]
and[vbcol=seagreen]
> the
> works
>
I recently upgrade a WinNT 4 SP6a Proxy server to Win2K SP4 with ISA SP2. I
have to allow remote users to connect to a SQL server 7 SP4 on Winnt 4 SP6a
behind ISA. The IP is static. It was working fine with Proxy but now I have
the following with clients on the Web:
[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets] Network erro
r and if I
try SQL Query Analyzer I have
Unable to connect to server xxx.xxx.xxx.xxx
ODBC:Msg 0, Level 16, State 1
[Microsoft][ODBC SQL Server Driver] Time out error
I have the ISA port 1433 and 1344 (for the apps running with SQL) opened and
listenning . If I run netstat -na on both servers, both show ports as
listenning. I can telnet the ISA external IP on both ports. ISA client is
installed on the SQL server.
I ran thru a similar problem when I configured it for the proxy 2 years ago
and don't remember what was the problem exactly. With the proxy, I had to
add wspclnt.ini in the sql server binn folder to map the port 1433 to the
proxy server and added a connection in SQL server network utility which was
mapped to the external IP of the Proxy. I tried it with and without and
there is no difference. I also remember that I had to use credtool on the
SQL server. Do I have to do it with ISA?
I'm familiar with ISA and i often have to open ports for apps and it works
fine so what is diffenrent for SQL server?
Any help would be greatly appreciated.
Thanks in advance.
Steve AmiraultTake the firewall client off the SQL server and make sure the default
gateway of the SQL server is the ISA server, if that is the route to the
internet. Did you make the Server Publishing Rule for the machine?
Scott Harding
MCSE, MCSA, A+, Network+
Microsoft MVP - Windows NT Server
"Steve" <as@.joe.ca> wrote in message
news:uqKNAmSsEHA.2660@.TK2MSFTNGP12.phx.gbl...
> Hi,
> I recently upgrade a WinNT 4 SP6a Proxy server to Win2K SP4 with ISA SP2.
I
> have to allow remote users to connect to a SQL server 7 SP4 on Winnt 4
SP6a
> behind ISA. The IP is static. It was working fine with Proxy but now I
have
> the following with clients on the Web:
> [Microsoft][ODBC SQL Server Driver][TCP/IP Sockets] Network er
ror and if I
> try SQL Query Analyzer I have
> Unable to connect to server xxx.xxx.xxx.xxx
> ODBC:Msg 0, Level 16, State 1
> [Microsoft][ODBC SQL Server Driver] Time out error
> I have the ISA port 1433 and 1344 (for the apps running with SQL) opened
and
> listenning . If I run netstat -na on both servers, both show ports as
> listenning. I can telnet the ISA external IP on both ports. ISA client is
> installed on the SQL server.
> I ran thru a similar problem when I configured it for the proxy 2 years
ago
> and don't remember what was the problem exactly. With the proxy, I had to
> add wspclnt.ini in the sql server binn folder to map the port 1433 to the
> proxy server and added a connection in SQL server network utility which
was
> mapped to the external IP of the Proxy. I tried it with and without and
> there is no difference. I also remember that I had to use credtool on the
> SQL server. Do I have to do it with ISA?
> I'm familiar with ISA and i often have to open ports for apps and it works
> fine so what is diffenrent for SQL server?
> Any help would be greatly appreciated.
> Thanks in advance.
> Steve Amirault
>|||Yes there is a Server rule. Guess what, by doing it the same way I did it
with the former proxy, it works. I disabled the server publishing rule,
added the wspcfg.ini file in the mssql7\binn folder and it works? At the
setup time and according to the situations I had with the ISA, I first
thought that it wouldn't work using the same settings as it was with the
proxy server but it appears that is not the case.
Thanks anyway.
Steve
"Scott Harding - MS MVP" <scrockel@.**NO_SPAM**hotmail.com> a crit dans le
message de news:OJeoP1TsEHA.3200@.TK2MSFTNGP09.phx.gbl...
> Take the firewall client off the SQL server and make sure the default
> gateway of the SQL server is the ISA server, if that is the route to the
> internet. Did you make the Server Publishing Rule for the machine?
> --
> Scott Harding
> MCSE, MCSA, A+, Network+
> Microsoft MVP - Windows NT Server
> "Steve" <as@.joe.ca> wrote in message
> news:uqKNAmSsEHA.2660@.TK2MSFTNGP12.phx.gbl...
SP2.[vbcol=seagreen]
> I
> SP6a
> have
I[vbcol=seagreen]
> and
is[vbcol=seagreen]
> ago
to[vbcol=seagreen]
the[vbcol=seagreen]
> was
the[vbcol=seagreen]
works[vbcol=seagreen]
>|||Interesting...you shouldn't have to do that but it depends I think if the
SQL server is a Secure NAT client or not.
Scott Harding
MCSE, MCSA, A+, Network+
Microsoft MVP - Windows NT Server
"Steve" <as@.joe.ca> wrote in message
news:uplh6uUsEHA.3412@.TK2MSFTNGP14.phx.gbl...
> Yes there is a Server rule. Guess what, by doing it the same way I did it
> with the former proxy, it works. I disabled the server publishing rule,
> added the wspcfg.ini file in the mssql7\binn folder and it works? At the
> setup time and according to the situations I had with the ISA, I first
> thought that it wouldn't work using the same settings as it was with the
> proxy server but it appears that is not the case.
> Thanks anyway.
> Steve
>
> "Scott Harding - MS MVP" <scrockel@.**NO_SPAM**hotmail.com> a crit dans le
> message de news:OJeoP1TsEHA.3200@.TK2MSFTNGP09.phx.gbl...
> SP2.
4[vbcol=seagreen]
if[vbcol=seagreen]
> I
opened[vbcol=seagreen]
> is
years[vbcol=seagreen]
> to
> the
which[vbcol=seagreen]
and[vbcol=seagreen]
> the
> works
>
Subscribe to:
Posts (Atom)