Hello,
I have php 5.0.2 on Apache2/WinXP and database on MS SQL 2005 express.
I cannot connect to server:
Warning: mssql_connect() [function.mssql-connect]: Unable to connect to
server: TESTSERVER\SQLEXPRESS in C:\xxx\test.php on line 11
My source code test.php:
...
$connectstring = mssql_connect("TESTSERVER/SQLEXPRESS","sa","xx");
if ($connectstring == FALSE)
echo "ERROR!";
else
echo "OK!";
...
This example with MSDE2000 work ok, but with SQL2005 Express not. Help
me, please.
J.R.I use new version ntwdblib.dll and all is OK!
http://support.microsoft.com/dllhel...2548&l=55&det=1
Jan Rok napsal(a):
> Hello,
> I have php 5.0.2 on Apache2/WinXP and database on MS SQL 2005 express.
> I cannot connect to server:
> Warning: mssql_connect() [function.mssql-connect]: Unable to connect t
o
> server: TESTSERVER\SQLEXPRESS in C:\xxx\test.php on line 11
> My source code test.php:
> ...
> $connectstring = mssql_connect("TESTSERVER/SQLEXPRESS","sa","xx");
> if ($connectstring == FALSE)
> echo "ERROR!";
> else
> echo "OK!";
> ...
> This example with MSDE2000 work ok, but with SQL2005 Express not. Help
> me, please.
> J.R.|||What happens if you change TESTSERVER/SQLEXPRESS to TESTSERVER\SQLEXPRESS in
your connection string? Did you setup SQL Express for mixed mode access
when you installed it? By default it is Windows authentication only.
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"Jan Rok" <jan.rok@.email.cz> wrote in message
news:e2Z4SUXLGHA.420@.tk2msftngp13.phx.gbl...
> Hello,
> I have php 5.0.2 on Apache2/WinXP and database on MS SQL 2005 express.
> I cannot connect to server:
> Warning: mssql_connect() [function.mssql-connect]: Unable to connect t
o
> server: TESTSERVER\SQLEXPRESS in C:\xxx\test.php on line 11
> My source code test.php:
> ...
> $connectstring = mssql_connect("TESTSERVER/SQLEXPRESS","sa","xx");
> if ($connectstring == FALSE)
> echo "ERROR!";
> else
> echo "OK!";
> ...
> This example with MSDE2000 work ok, but with SQL2005 Express not. Help me,
> please.
> J.R.
Showing posts with label winxp. Show all posts
Showing posts with label winxp. Show all posts
Saturday, February 25, 2012
Cannot connect to SQL2005 Express from PHP
Hello,
I have PHP 5.0.2 on Apache2/WinXP and database on MS SQL 2005 express.
I cannot connect to server:
Warning: mssql_connect() [function.mssql-connect]: Unable to connect to
server: TESTSERVER\SQLEXPRESS in C:\xxx\test.php on line 11
My source code test.php:
...
$connectstring = mssql_connect("TESTSERVER/SQLEXPRESS","sa","xx");
if ($connectstring == FALSE)
echo "ERROR!";
else
echo "OK!";
...
This example with MSDE2000 work ok, but with SQL2005 Express not. Help
me, please.
J.R.
I use new version ntwdblib.dll and all is OK!
http://support.microsoft.com/dllhelp...548&l=55&det=1
Jan Rok napsal(a):
> Hello,
> I have PHP 5.0.2 on Apache2/WinXP and database on MS SQL 2005 express.
> I cannot connect to server:
> Warning: mssql_connect() [function.mssql-connect]: Unable to connect to
> server: TESTSERVER\SQLEXPRESS in C:\xxx\test.php on line 11
> My source code test.php:
> ...
> $connectstring = mssql_connect("TESTSERVER/SQLEXPRESS","sa","xx");
> if ($connectstring == FALSE)
> echo "ERROR!";
> else
> echo "OK!";
> ...
> This example with MSDE2000 work ok, but with SQL2005 Express not. Help
> me, please.
> J.R.
|||What happens if you change TESTSERVER/SQLEXPRESS to TESTSERVER\SQLEXPRESS in
your connection string? Did you setup SQL Express for mixed mode access
when you installed it? By default it is Windows authentication only.
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"Jan Rok" <jan.rok@.email.cz> wrote in message
news:e2Z4SUXLGHA.420@.tk2msftngp13.phx.gbl...
> Hello,
> I have PHP 5.0.2 on Apache2/WinXP and database on MS SQL 2005 express.
> I cannot connect to server:
> Warning: mssql_connect() [function.mssql-connect]: Unable to connect to
> server: TESTSERVER\SQLEXPRESS in C:\xxx\test.php on line 11
> My source code test.php:
> ...
> $connectstring = mssql_connect("TESTSERVER/SQLEXPRESS","sa","xx");
> if ($connectstring == FALSE)
> echo "ERROR!";
> else
> echo "OK!";
> ...
> This example with MSDE2000 work ok, but with SQL2005 Express not. Help me,
> please.
> J.R.
I have PHP 5.0.2 on Apache2/WinXP and database on MS SQL 2005 express.
I cannot connect to server:
Warning: mssql_connect() [function.mssql-connect]: Unable to connect to
server: TESTSERVER\SQLEXPRESS in C:\xxx\test.php on line 11
My source code test.php:
...
$connectstring = mssql_connect("TESTSERVER/SQLEXPRESS","sa","xx");
if ($connectstring == FALSE)
echo "ERROR!";
else
echo "OK!";
...
This example with MSDE2000 work ok, but with SQL2005 Express not. Help
me, please.
J.R.
I use new version ntwdblib.dll and all is OK!
http://support.microsoft.com/dllhelp...548&l=55&det=1
Jan Rok napsal(a):
> Hello,
> I have PHP 5.0.2 on Apache2/WinXP and database on MS SQL 2005 express.
> I cannot connect to server:
> Warning: mssql_connect() [function.mssql-connect]: Unable to connect to
> server: TESTSERVER\SQLEXPRESS in C:\xxx\test.php on line 11
> My source code test.php:
> ...
> $connectstring = mssql_connect("TESTSERVER/SQLEXPRESS","sa","xx");
> if ($connectstring == FALSE)
> echo "ERROR!";
> else
> echo "OK!";
> ...
> This example with MSDE2000 work ok, but with SQL2005 Express not. Help
> me, please.
> J.R.
|||What happens if you change TESTSERVER/SQLEXPRESS to TESTSERVER\SQLEXPRESS in
your connection string? Did you setup SQL Express for mixed mode access
when you installed it? By default it is Windows authentication only.
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"Jan Rok" <jan.rok@.email.cz> wrote in message
news:e2Z4SUXLGHA.420@.tk2msftngp13.phx.gbl...
> Hello,
> I have PHP 5.0.2 on Apache2/WinXP and database on MS SQL 2005 express.
> I cannot connect to server:
> Warning: mssql_connect() [function.mssql-connect]: Unable to connect to
> server: TESTSERVER\SQLEXPRESS in C:\xxx\test.php on line 11
> My source code test.php:
> ...
> $connectstring = mssql_connect("TESTSERVER/SQLEXPRESS","sa","xx");
> if ($connectstring == FALSE)
> echo "ERROR!";
> else
> echo "OK!";
> ...
> This example with MSDE2000 work ok, but with SQL2005 Express not. Help me,
> please.
> J.R.
Friday, February 24, 2012
Cannot connect to SQL Server or MSDE when enable ICF
Hi,
I enable Internet Connection Firewall (ICF) on my machine (WinXP SP1). I have installed both MSDE and SQL server on my machine, while I test my application from another machine my App cannot connect to my machine. Then I think the problem is because the I
CF.
Is there anyone know how to configure the port for SQL server or MSDE?
Cheer,
KPH
Hi,
when you look in the properties of your server there you can see the port,
the server is using.
I dont know if the icf can be configured so that a special port is open.
Perhaps you should use zonealarm for this or an other firewall which can be
more configured.
Or disable the icf, if possible.
I think the standardport is 1433.
Regards
Alexander
"KPH" <KPH@.discussions.microsoft.com> schrieb im Newsbeitrag
news:2D296E26-38B1-48A4-8414-9D8C84A366C7@.microsoft.com...
> Hi,
> I enable Internet Connection Firewall (ICF) on my machine (WinXP SP1). I
have installed both MSDE and SQL server on my machine, while I test my
application from another machine my App cannot connect to my machine. Then I
think the problem is because the ICF.
> Is there anyone know how to configure the port for SQL server or MSDE?
> Cheer,
> KPH
I enable Internet Connection Firewall (ICF) on my machine (WinXP SP1). I have installed both MSDE and SQL server on my machine, while I test my application from another machine my App cannot connect to my machine. Then I think the problem is because the I
CF.
Is there anyone know how to configure the port for SQL server or MSDE?
Cheer,
KPH
Hi,
when you look in the properties of your server there you can see the port,
the server is using.
I dont know if the icf can be configured so that a special port is open.
Perhaps you should use zonealarm for this or an other firewall which can be
more configured.
Or disable the icf, if possible.
I think the standardport is 1433.
Regards
Alexander
"KPH" <KPH@.discussions.microsoft.com> schrieb im Newsbeitrag
news:2D296E26-38B1-48A4-8414-9D8C84A366C7@.microsoft.com...
> Hi,
> I enable Internet Connection Firewall (ICF) on my machine (WinXP SP1). I
have installed both MSDE and SQL server on my machine, while I test my
application from another machine my App cannot connect to my machine. Then I
think the problem is because the ICF.
> Is there anyone know how to configure the port for SQL server or MSDE?
> Cheer,
> KPH
Cannot connect to SQL Server or MSDE when enable ICF
Hi,
I enable Internet Connection Firewall (ICF) on my machine (WinXP SP1). I have installed both MSDE and SQL server on my machine, while I test my application from another machine my App cannot connect to my machine. Then I think the problem is because the ICF.
Is there anyone know how to configure the port for SQL server or MSDE?
Cheer,
KPHHi,
when you look in the properties of your server there you can see the port,
the server is using.
I don´t know if the icf can be configured so that a special port is open.
Perhaps you should use zonealarm for this or an other firewall which can be
more configured.
Or disable the icf, if possible.
I think the standardport is 1433.
Regards
Alexander
"KPH" <KPH@.discussions.microsoft.com> schrieb im Newsbeitrag
news:2D296E26-38B1-48A4-8414-9D8C84A366C7@.microsoft.com...
> Hi,
> I enable Internet Connection Firewall (ICF) on my machine (WinXP SP1). I
have installed both MSDE and SQL server on my machine, while I test my
application from another machine my App cannot connect to my machine. Then I
think the problem is because the ICF.
> Is there anyone know how to configure the port for SQL server or MSDE?
> Cheer,
> KPH
I enable Internet Connection Firewall (ICF) on my machine (WinXP SP1). I have installed both MSDE and SQL server on my machine, while I test my application from another machine my App cannot connect to my machine. Then I think the problem is because the ICF.
Is there anyone know how to configure the port for SQL server or MSDE?
Cheer,
KPHHi,
when you look in the properties of your server there you can see the port,
the server is using.
I don´t know if the icf can be configured so that a special port is open.
Perhaps you should use zonealarm for this or an other firewall which can be
more configured.
Or disable the icf, if possible.
I think the standardport is 1433.
Regards
Alexander
"KPH" <KPH@.discussions.microsoft.com> schrieb im Newsbeitrag
news:2D296E26-38B1-48A4-8414-9D8C84A366C7@.microsoft.com...
> Hi,
> I enable Internet Connection Firewall (ICF) on my machine (WinXP SP1). I
have installed both MSDE and SQL server on my machine, while I test my
application from another machine my App cannot connect to my machine. Then I
think the problem is because the ICF.
> Is there anyone know how to configure the port for SQL server or MSDE?
> Cheer,
> KPH
Cannot connect to SQL Server or MSDE when enable ICF
Hi,
I enable Internet Connection Firewall (ICF) on my machine (WinXP SP1). I hav
e installed both MSDE and SQL server on my machine, while I test my applicat
ion from another machine my App cannot connect to my machine. Then I think t
he problem is because the I
CF.
Is there anyone know how to configure the port for SQL server or MSDE?
Cheer,
KPHHi,
when you look in the properties of your server there you can see the port,
the server is using.
I dont know if the icf can be configured so that a special port is open.
Perhaps you should use zonealarm for this or an other firewall which can be
more configured.
Or disable the icf, if possible.
I think the standardport is 1433.
Regards
Alexander
"KPH" <KPH@.discussions.microsoft.com> schrieb im Newsbeitrag
news:2D296E26-38B1-48A4-8414-9D8C84A366C7@.microsoft.com...
> Hi,
> I enable Internet Connection Firewall (ICF) on my machine (WinXP SP1). I
have installed both MSDE and SQL server on my machine, while I test my
application from another machine my App cannot connect to my machine. Then I
think the problem is because the ICF.
> Is there anyone know how to configure the port for SQL server or MSDE?
> Cheer,
> KPH
I enable Internet Connection Firewall (ICF) on my machine (WinXP SP1). I hav
e installed both MSDE and SQL server on my machine, while I test my applicat
ion from another machine my App cannot connect to my machine. Then I think t
he problem is because the I
CF.
Is there anyone know how to configure the port for SQL server or MSDE?
Cheer,
KPHHi,
when you look in the properties of your server there you can see the port,
the server is using.
I dont know if the icf can be configured so that a special port is open.
Perhaps you should use zonealarm for this or an other firewall which can be
more configured.
Or disable the icf, if possible.
I think the standardport is 1433.
Regards
Alexander
"KPH" <KPH@.discussions.microsoft.com> schrieb im Newsbeitrag
news:2D296E26-38B1-48A4-8414-9D8C84A366C7@.microsoft.com...
> Hi,
> I enable Internet Connection Firewall (ICF) on my machine (WinXP SP1). I
have installed both MSDE and SQL server on my machine, while I test my
application from another machine my App cannot connect to my machine. Then I
think the problem is because the ICF.
> Is there anyone know how to configure the port for SQL server or MSDE?
> Cheer,
> KPH
Cannot connect to Sql Server 2005 Express. Any idea why ?
Hi everybody
I have a system with :
WinXP Pro, MSDE 2000, Framework 2.0 beta. On top of it i installed SqlServer
2005 Beta with Mixed Mode. I am using Query Analyzer and Enterperise Manager
from SQLServer 2000 to connect to it (manual says I can) but with no
success. I tried to log on with windows authentication as well as with Sql
authentication . I tried the following names to connect :
(local)\SQLEXPRESS; COMP_NAME\SQLEXPRESS; SQLEXPRESS; MSSQL$SQLEXPRESS and
so on but never got connected. It always say that the
SQL Server does not exist or Access denied.
I checked in the services where it is set to automatic and is running. I
also stopped and restarted but with no success. What i am missing ?
At the end I uninstalled everything and reinstalled only Framework 2.0 and
Sql Server 2005 Beta but having the same problem.
Anyone know how to fix this ?
Thanks in advance
Raja
hi, Raja,
"Ing. Rajesh Kumar" <iambad(Without This)@.post.cz> ha scritto nel messaggio
news:OFSx33CcEHA.2908@.TK2MSFTNGP10.phx.gbl...
> Hi everybody
> I have a system with :
> WinXP Pro, MSDE 2000, Framework 2.0 beta. On top of it i installed
SqlServer
> 2005 Beta with Mixed Mode. I am using Query Analyzer and Enterperise
Manager
> from SQLServer 2000 to connect to it (manual says I can) but with no
> success. I tried to log on with windows authentication as well as with Sql
> authentication . I tried the following names to connect :
> (local)\SQLEXPRESS; COMP_NAME\SQLEXPRESS; SQLEXPRESS; MSSQL$SQLEXPRESS and
> so on but never got connected. It always say that the
> SQL Server does not exist or Access denied.
> I checked in the services where it is set to automatic and is running. I
> also stopped and restarted but with no success. What i am missing ?
> At the end I uninstalled everything and reinstalled only Framework 2.0 and
> Sql Server 2005 Beta but having the same problem.
frorm microsoft.private.sqlserver2005.express newsgroup:
1. Enable Protocols
a. Launch SQL Computer Manager
b. Expand "Server Network Configuration"
c. Expand Protocols for "SQLEXPRESS"
d. Enable Np (for local access)
e. Enable TCP (for remote access)
2. Restart SQL Express
a. can be done from either SQL Computer Manager, Services applet, or
command line
3. Start SQL Browser service from Service applet or command line
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.8.0 - DbaMgr ver 0.54.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
I have a system with :
WinXP Pro, MSDE 2000, Framework 2.0 beta. On top of it i installed SqlServer
2005 Beta with Mixed Mode. I am using Query Analyzer and Enterperise Manager
from SQLServer 2000 to connect to it (manual says I can) but with no
success. I tried to log on with windows authentication as well as with Sql
authentication . I tried the following names to connect :
(local)\SQLEXPRESS; COMP_NAME\SQLEXPRESS; SQLEXPRESS; MSSQL$SQLEXPRESS and
so on but never got connected. It always say that the
SQL Server does not exist or Access denied.
I checked in the services where it is set to automatic and is running. I
also stopped and restarted but with no success. What i am missing ?
At the end I uninstalled everything and reinstalled only Framework 2.0 and
Sql Server 2005 Beta but having the same problem.
Anyone know how to fix this ?
Thanks in advance
Raja
hi, Raja,
"Ing. Rajesh Kumar" <iambad(Without This)@.post.cz> ha scritto nel messaggio
news:OFSx33CcEHA.2908@.TK2MSFTNGP10.phx.gbl...
> Hi everybody
> I have a system with :
> WinXP Pro, MSDE 2000, Framework 2.0 beta. On top of it i installed
SqlServer
> 2005 Beta with Mixed Mode. I am using Query Analyzer and Enterperise
Manager
> from SQLServer 2000 to connect to it (manual says I can) but with no
> success. I tried to log on with windows authentication as well as with Sql
> authentication . I tried the following names to connect :
> (local)\SQLEXPRESS; COMP_NAME\SQLEXPRESS; SQLEXPRESS; MSSQL$SQLEXPRESS and
> so on but never got connected. It always say that the
> SQL Server does not exist or Access denied.
> I checked in the services where it is set to automatic and is running. I
> also stopped and restarted but with no success. What i am missing ?
> At the end I uninstalled everything and reinstalled only Framework 2.0 and
> Sql Server 2005 Beta but having the same problem.
frorm microsoft.private.sqlserver2005.express newsgroup:
1. Enable Protocols
a. Launch SQL Computer Manager
b. Expand "Server Network Configuration"
c. Expand Protocols for "SQLEXPRESS"
d. Enable Np (for local access)
e. Enable TCP (for remote access)
2. Restart SQL Express
a. can be done from either SQL Computer Manager, Services applet, or
command line
3. Start SQL Browser service from Service applet or command line
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.8.0 - DbaMgr ver 0.54.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
Tuesday, February 14, 2012
Cannot connect to remote SQL 2k5 server in local network
My SQL 2005 Dev Edition hosted on WinXP.
However my another WinXP in the same network cannot connect to the SQL 2k5
using ODBC
Got this error:
Connection failed:
SQLState: '01000'
SQL Server Error: 53
[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionOpen (Connect()).
Connection failed:
SQLState: '08001'
SQL Server Error: 17
[Microsof][ODBC SQL Server Driver][DBNETLIB]SQL Server does not exist or
access denied.
Info:
Host machine:
OS: WinXP SP2
Firewall: Opened 1433 TCP, 1434 UDP
SQL Server 2005 Dev Edit.
Instance Name: Winxp-hongpc\SQL2K5
Network Config: Enabled Shared Memory, Named Pipes, TCP/IP
Inside TCP/IP setting:
IP1:
Active = Yes
Enabled = Yes
IP Address = 192.168.1.100
TCP Dynamic Ports = [blank]
TCP Port = 1433
IP2:
Active = Yes
Enabled = No
IP Address = 127.0.0.1
TCP Dynamic Ports = 0
TCP Port = [blank]
IPAll:
TCP Dynamic Ports: [blank]
TCP Port: 1433
Anyone helps?
"Jason Chan" <no@.email.com> wrote in message
news:u4OvHgPHGHA.2440@.TK2MSFTNGP14.phx.gbl...
> My SQL 2005 Dev Edition hosted on WinXP.
> However my another WinXP in the same network cannot connect to the SQL 2k5
> using ODBC
> Got this error:
> Connection failed:
> SQLState: '01000'
> SQL Server Error: 53
> [Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionOpen (Connect()).
> Connection failed:
> SQLState: '08001'
> SQL Server Error: 17
> [Microsof][ODBC SQL Server Driver][DBNETLIB]SQL Server does not exist or
> access denied.
> Info:
> Host machine:
> OS: WinXP SP2
> Firewall: Opened 1433 TCP, 1434 UDP
> SQL Server 2005 Dev Edit.
> Instance Name: Winxp-hongpc\SQL2K5
> Network Config: Enabled Shared Memory, Named Pipes, TCP/IP
> Inside TCP/IP setting:
> IP1:
> Active = Yes
> Enabled = Yes
> IP Address = 192.168.1.100
> TCP Dynamic Ports = [blank]
> TCP Port = 1433
> IP2:
> Active = Yes
> Enabled = No
> IP Address = 127.0.0.1
> TCP Dynamic Ports = 0
> TCP Port = [blank]
> IPAll:
> TCP Dynamic Ports: [blank]
> TCP Port: 1433
> Anyone helps?
>
well, to begin with, IP2's IP address is the loop-back address and isn't
going to communicate with anything. Check the IP config on this computer.
you may have to reinstall the tcp/ip stack.
steve.
|||Thanks for your reply.
Actually I dont know why there is a IP2, since I have only I network card in
my host winxp.
I get this information from the SQL Server Configuration Manager -> SQL
Server 2005 Network Config. -> Protocols for SQL2K5-> TCP/IP -> IP Address
tab.
The setting in IP2 is there by default, I havn't changed anything.
Tried to deactive the IP2, but still dont make it work.
"molsonexpert" <imdrunk@.work.ca> glsD:egUCLoPHGHA.1760@.TK2MSFTNGP10.phx.g bl...
"Jason Chan" <no@.email.com> wrote in message
news:u4OvHgPHGHA.2440@.TK2MSFTNGP14.phx.gbl...
> My SQL 2005 Dev Edition hosted on WinXP.
> However my another WinXP in the same network cannot connect to the SQL 2k5
> using ODBC
> Got this error:
> Connection failed:
> SQLState: '01000'
> SQL Server Error: 53
> [Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionOpen (Connect()).
> Connection failed:
> SQLState: '08001'
> SQL Server Error: 17
> [Microsof][ODBC SQL Server Driver][DBNETLIB]SQL Server does not exist or
> access denied.
> Info:
> Host machine:
> OS: WinXP SP2
> Firewall: Opened 1433 TCP, 1434 UDP
> SQL Server 2005 Dev Edit.
> Instance Name: Winxp-hongpc\SQL2K5
> Network Config: Enabled Shared Memory, Named Pipes, TCP/IP
> Inside TCP/IP setting:
> IP1:
> Active = Yes
> Enabled = Yes
> IP Address = 192.168.1.100
> TCP Dynamic Ports = [blank]
> TCP Port = 1433
> IP2:
> Active = Yes
> Enabled = No
> IP Address = 127.0.0.1
> TCP Dynamic Ports = 0
> TCP Port = [blank]
> IPAll:
> TCP Dynamic Ports: [blank]
> TCP Port: 1433
> Anyone helps?
>
well, to begin with, IP2's IP address is the loop-back address and isn't
going to communicate with anything. Check the IP config on this computer.
you may have to reinstall the tcp/ip stack.
steve.
|||I retried and I found that I can connect using named piped, so what is the
problem for TCP/IP
"Jason Chan" <no@.email.com> glsD:e047mNRHGHA.344@.TK2MSFTNGP11.phx.gb l...
Thanks for your reply.
Actually I dont know why there is a IP2, since I have only I network card in
my host winxp.
I get this information from the SQL Server Configuration Manager -> SQL
Server 2005 Network Config. -> Protocols for SQL2K5-> TCP/IP -> IP Address
tab.
The setting in IP2 is there by default, I havn't changed anything.
Tried to deactive the IP2, but still dont make it work.
"molsonexpert" <imdrunk@.work.ca> glsD:egUCLoPHGHA.1760@.TK2MSFTNGP10.phx.g bl...
"Jason Chan" <no@.email.com> wrote in message
news:u4OvHgPHGHA.2440@.TK2MSFTNGP14.phx.gbl...
> My SQL 2005 Dev Edition hosted on WinXP.
> However my another WinXP in the same network cannot connect to the SQL 2k5
> using ODBC
> Got this error:
> Connection failed:
> SQLState: '01000'
> SQL Server Error: 53
> [Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionOpen (Connect()).
> Connection failed:
> SQLState: '08001'
> SQL Server Error: 17
> [Microsof][ODBC SQL Server Driver][DBNETLIB]SQL Server does not exist or
> access denied.
> Info:
> Host machine:
> OS: WinXP SP2
> Firewall: Opened 1433 TCP, 1434 UDP
> SQL Server 2005 Dev Edit.
> Instance Name: Winxp-hongpc\SQL2K5
> Network Config: Enabled Shared Memory, Named Pipes, TCP/IP
> Inside TCP/IP setting:
> IP1:
> Active = Yes
> Enabled = Yes
> IP Address = 192.168.1.100
> TCP Dynamic Ports = [blank]
> TCP Port = 1433
> IP2:
> Active = Yes
> Enabled = No
> IP Address = 127.0.0.1
> TCP Dynamic Ports = 0
> TCP Port = [blank]
> IPAll:
> TCP Dynamic Ports: [blank]
> TCP Port: 1433
> Anyone helps?
>
well, to begin with, IP2's IP address is the loop-back address and isn't
going to communicate with anything. Check the IP config on this computer.
you may have to reinstall the tcp/ip stack.
steve.
|||"Jason Chan" <no@.email.com> wrote in message
news:u$rU6ORHGHA.2836@.TK2MSFTNGP14.phx.gbl...
>I retried and I found that I can connect using named piped, so what is the
> problem for TCP/IP
> "Jason Chan" <no@.email.com>
> glsD:e047mNRHGHA.344@.TK2MSFTNGP11.phx.gb l...
> Thanks for your reply.
> Actually I dont know why there is a IP2, since I have only I network card
> in
> my host winxp.
> I get this information from the SQL Server Configuration Manager -> SQL
> Server 2005 Network Config. -> Protocols for SQL2K5-> TCP/IP -> IP Address
> tab.
> The setting in IP2 is there by default, I havn't changed anything.
> Tried to deactive the IP2, but still dont make it work.
> "molsonexpert" <imdrunk@.work.ca>
> glsD:egUCLoPHGHA.1760@.TK2MSFTNGP10.phx.g bl...
> "Jason Chan" <no@.email.com> wrote in message
> news:u4OvHgPHGHA.2440@.TK2MSFTNGP14.phx.gbl...
> well, to begin with, IP2's IP address is the loop-back address and isn't
> going to communicate with anything. Check the IP config on this computer.
> you may have to reinstall the tcp/ip stack.
> steve.
>
>
Try these:
http://support.microsoft.com/search/...de=a&x=11&y=16
http://tinyurl.com/7ef8v
steve.
|||As mentioned, 127.0.0.1 is the loopback adapter. Essentially that's the
network card connecting to itself. This comes with the network card and is
intended for troubleshooting. It's only avalable if you are connecting from
the same computer, so in your case you can just ignore it.
Rick Byham
MCDBA, MCSE, MCSA
Lead Technical Writer,
Microsoft, SQL Server Books Online
This posting is provided "as is" with
no warranties, and confers no rights.
"Jason Chan" <no@.email.com> wrote in message
news:u$rU6ORHGHA.2836@.TK2MSFTNGP14.phx.gbl...
>I retried and I found that I can connect using named piped, so what is the
> problem for TCP/IP
> "Jason Chan" <no@.email.com>
> glsD:e047mNRHGHA.344@.TK2MSFTNGP11.phx.gb l...
> Thanks for your reply.
> Actually I dont know why there is a IP2, since I have only I network card
> in
> my host winxp.
> I get this information from the SQL Server Configuration Manager -> SQL
> Server 2005 Network Config. -> Protocols for SQL2K5-> TCP/IP -> IP Address
> tab.
> The setting in IP2 is there by default, I havn't changed anything.
> Tried to deactive the IP2, but still dont make it work.
> "molsonexpert" <imdrunk@.work.ca>
> glsD:egUCLoPHGHA.1760@.TK2MSFTNGP10.phx.g bl...
> "Jason Chan" <no@.email.com> wrote in message
> news:u4OvHgPHGHA.2440@.TK2MSFTNGP14.phx.gbl...
> well, to begin with, IP2's IP address is the loop-back address and isn't
> going to communicate with anything. Check the IP config on this computer.
> you may have to reinstall the tcp/ip stack.
> steve.
>
>
However my another WinXP in the same network cannot connect to the SQL 2k5
using ODBC
Got this error:
Connection failed:
SQLState: '01000'
SQL Server Error: 53
[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionOpen (Connect()).
Connection failed:
SQLState: '08001'
SQL Server Error: 17
[Microsof][ODBC SQL Server Driver][DBNETLIB]SQL Server does not exist or
access denied.
Info:
Host machine:
OS: WinXP SP2
Firewall: Opened 1433 TCP, 1434 UDP
SQL Server 2005 Dev Edit.
Instance Name: Winxp-hongpc\SQL2K5
Network Config: Enabled Shared Memory, Named Pipes, TCP/IP
Inside TCP/IP setting:
IP1:
Active = Yes
Enabled = Yes
IP Address = 192.168.1.100
TCP Dynamic Ports = [blank]
TCP Port = 1433
IP2:
Active = Yes
Enabled = No
IP Address = 127.0.0.1
TCP Dynamic Ports = 0
TCP Port = [blank]
IPAll:
TCP Dynamic Ports: [blank]
TCP Port: 1433
Anyone helps?
"Jason Chan" <no@.email.com> wrote in message
news:u4OvHgPHGHA.2440@.TK2MSFTNGP14.phx.gbl...
> My SQL 2005 Dev Edition hosted on WinXP.
> However my another WinXP in the same network cannot connect to the SQL 2k5
> using ODBC
> Got this error:
> Connection failed:
> SQLState: '01000'
> SQL Server Error: 53
> [Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionOpen (Connect()).
> Connection failed:
> SQLState: '08001'
> SQL Server Error: 17
> [Microsof][ODBC SQL Server Driver][DBNETLIB]SQL Server does not exist or
> access denied.
> Info:
> Host machine:
> OS: WinXP SP2
> Firewall: Opened 1433 TCP, 1434 UDP
> SQL Server 2005 Dev Edit.
> Instance Name: Winxp-hongpc\SQL2K5
> Network Config: Enabled Shared Memory, Named Pipes, TCP/IP
> Inside TCP/IP setting:
> IP1:
> Active = Yes
> Enabled = Yes
> IP Address = 192.168.1.100
> TCP Dynamic Ports = [blank]
> TCP Port = 1433
> IP2:
> Active = Yes
> Enabled = No
> IP Address = 127.0.0.1
> TCP Dynamic Ports = 0
> TCP Port = [blank]
> IPAll:
> TCP Dynamic Ports: [blank]
> TCP Port: 1433
> Anyone helps?
>
well, to begin with, IP2's IP address is the loop-back address and isn't
going to communicate with anything. Check the IP config on this computer.
you may have to reinstall the tcp/ip stack.
steve.
|||Thanks for your reply.
Actually I dont know why there is a IP2, since I have only I network card in
my host winxp.
I get this information from the SQL Server Configuration Manager -> SQL
Server 2005 Network Config. -> Protocols for SQL2K5-> TCP/IP -> IP Address
tab.
The setting in IP2 is there by default, I havn't changed anything.
Tried to deactive the IP2, but still dont make it work.
"molsonexpert" <imdrunk@.work.ca> glsD:egUCLoPHGHA.1760@.TK2MSFTNGP10.phx.g bl...
"Jason Chan" <no@.email.com> wrote in message
news:u4OvHgPHGHA.2440@.TK2MSFTNGP14.phx.gbl...
> My SQL 2005 Dev Edition hosted on WinXP.
> However my another WinXP in the same network cannot connect to the SQL 2k5
> using ODBC
> Got this error:
> Connection failed:
> SQLState: '01000'
> SQL Server Error: 53
> [Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionOpen (Connect()).
> Connection failed:
> SQLState: '08001'
> SQL Server Error: 17
> [Microsof][ODBC SQL Server Driver][DBNETLIB]SQL Server does not exist or
> access denied.
> Info:
> Host machine:
> OS: WinXP SP2
> Firewall: Opened 1433 TCP, 1434 UDP
> SQL Server 2005 Dev Edit.
> Instance Name: Winxp-hongpc\SQL2K5
> Network Config: Enabled Shared Memory, Named Pipes, TCP/IP
> Inside TCP/IP setting:
> IP1:
> Active = Yes
> Enabled = Yes
> IP Address = 192.168.1.100
> TCP Dynamic Ports = [blank]
> TCP Port = 1433
> IP2:
> Active = Yes
> Enabled = No
> IP Address = 127.0.0.1
> TCP Dynamic Ports = 0
> TCP Port = [blank]
> IPAll:
> TCP Dynamic Ports: [blank]
> TCP Port: 1433
> Anyone helps?
>
well, to begin with, IP2's IP address is the loop-back address and isn't
going to communicate with anything. Check the IP config on this computer.
you may have to reinstall the tcp/ip stack.
steve.
|||I retried and I found that I can connect using named piped, so what is the
problem for TCP/IP
"Jason Chan" <no@.email.com> glsD:e047mNRHGHA.344@.TK2MSFTNGP11.phx.gb l...
Thanks for your reply.
Actually I dont know why there is a IP2, since I have only I network card in
my host winxp.
I get this information from the SQL Server Configuration Manager -> SQL
Server 2005 Network Config. -> Protocols for SQL2K5-> TCP/IP -> IP Address
tab.
The setting in IP2 is there by default, I havn't changed anything.
Tried to deactive the IP2, but still dont make it work.
"molsonexpert" <imdrunk@.work.ca> glsD:egUCLoPHGHA.1760@.TK2MSFTNGP10.phx.g bl...
"Jason Chan" <no@.email.com> wrote in message
news:u4OvHgPHGHA.2440@.TK2MSFTNGP14.phx.gbl...
> My SQL 2005 Dev Edition hosted on WinXP.
> However my another WinXP in the same network cannot connect to the SQL 2k5
> using ODBC
> Got this error:
> Connection failed:
> SQLState: '01000'
> SQL Server Error: 53
> [Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionOpen (Connect()).
> Connection failed:
> SQLState: '08001'
> SQL Server Error: 17
> [Microsof][ODBC SQL Server Driver][DBNETLIB]SQL Server does not exist or
> access denied.
> Info:
> Host machine:
> OS: WinXP SP2
> Firewall: Opened 1433 TCP, 1434 UDP
> SQL Server 2005 Dev Edit.
> Instance Name: Winxp-hongpc\SQL2K5
> Network Config: Enabled Shared Memory, Named Pipes, TCP/IP
> Inside TCP/IP setting:
> IP1:
> Active = Yes
> Enabled = Yes
> IP Address = 192.168.1.100
> TCP Dynamic Ports = [blank]
> TCP Port = 1433
> IP2:
> Active = Yes
> Enabled = No
> IP Address = 127.0.0.1
> TCP Dynamic Ports = 0
> TCP Port = [blank]
> IPAll:
> TCP Dynamic Ports: [blank]
> TCP Port: 1433
> Anyone helps?
>
well, to begin with, IP2's IP address is the loop-back address and isn't
going to communicate with anything. Check the IP config on this computer.
you may have to reinstall the tcp/ip stack.
steve.
|||"Jason Chan" <no@.email.com> wrote in message
news:u$rU6ORHGHA.2836@.TK2MSFTNGP14.phx.gbl...
>I retried and I found that I can connect using named piped, so what is the
> problem for TCP/IP
> "Jason Chan" <no@.email.com>
> glsD:e047mNRHGHA.344@.TK2MSFTNGP11.phx.gb l...
> Thanks for your reply.
> Actually I dont know why there is a IP2, since I have only I network card
> in
> my host winxp.
> I get this information from the SQL Server Configuration Manager -> SQL
> Server 2005 Network Config. -> Protocols for SQL2K5-> TCP/IP -> IP Address
> tab.
> The setting in IP2 is there by default, I havn't changed anything.
> Tried to deactive the IP2, but still dont make it work.
> "molsonexpert" <imdrunk@.work.ca>
> glsD:egUCLoPHGHA.1760@.TK2MSFTNGP10.phx.g bl...
> "Jason Chan" <no@.email.com> wrote in message
> news:u4OvHgPHGHA.2440@.TK2MSFTNGP14.phx.gbl...
> well, to begin with, IP2's IP address is the loop-back address and isn't
> going to communicate with anything. Check the IP config on this computer.
> you may have to reinstall the tcp/ip stack.
> steve.
>
>
Try these:
http://support.microsoft.com/search/...de=a&x=11&y=16
http://tinyurl.com/7ef8v
steve.
|||As mentioned, 127.0.0.1 is the loopback adapter. Essentially that's the
network card connecting to itself. This comes with the network card and is
intended for troubleshooting. It's only avalable if you are connecting from
the same computer, so in your case you can just ignore it.
Rick Byham
MCDBA, MCSE, MCSA
Lead Technical Writer,
Microsoft, SQL Server Books Online
This posting is provided "as is" with
no warranties, and confers no rights.
"Jason Chan" <no@.email.com> wrote in message
news:u$rU6ORHGHA.2836@.TK2MSFTNGP14.phx.gbl...
>I retried and I found that I can connect using named piped, so what is the
> problem for TCP/IP
> "Jason Chan" <no@.email.com>
> glsD:e047mNRHGHA.344@.TK2MSFTNGP11.phx.gb l...
> Thanks for your reply.
> Actually I dont know why there is a IP2, since I have only I network card
> in
> my host winxp.
> I get this information from the SQL Server Configuration Manager -> SQL
> Server 2005 Network Config. -> Protocols for SQL2K5-> TCP/IP -> IP Address
> tab.
> The setting in IP2 is there by default, I havn't changed anything.
> Tried to deactive the IP2, but still dont make it work.
> "molsonexpert" <imdrunk@.work.ca>
> glsD:egUCLoPHGHA.1760@.TK2MSFTNGP10.phx.g bl...
> "Jason Chan" <no@.email.com> wrote in message
> news:u4OvHgPHGHA.2440@.TK2MSFTNGP14.phx.gbl...
> well, to begin with, IP2's IP address is the loop-back address and isn't
> going to communicate with anything. Check the IP config on this computer.
> you may have to reinstall the tcp/ip stack.
> steve.
>
>
Cannot connect to remote SQL 2k5 server in local network
My SQL 2005 Dev Edition hosted on WinXP.
However my another WinXP in the same network cannot connect to the SQL 2k5
using ODBC
Got this error:
Connection failed:
SQLState: '01000'
SQL Server Error: 53
[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionOpen (Connect()).
Connection failed:
SQLState: '08001'
SQL Server Error: 17
[Microsof][ODBC SQL Server Driver][DBNETLIB]SQL Server does not exist or
access denied.
Info:
Host machine:
OS: WinXP SP2
Firewall: Opened 1433 TCP, 1434 UDP
SQL Server 2005 Dev Edit.
Instance Name: Winxp-hongpc\SQL2K5
Network Config: Enabled Shared Memory, Named Pipes, TCP/IP
Inside TCP/IP setting:
IP1:
Active = Yes
Enabled = Yes
IP Address = 192.168.1.100
TCP Dynamic Ports = [blank]
TCP Port = 1433
IP2:
Active = Yes
Enabled = No
IP Address = 127.0.0.1
TCP Dynamic Ports = 0
TCP Port = [blank]
IPAll:
TCP Dynamic Ports: [blank]
TCP Port: 1433
Anyone helps?"Jason Chan" <no@.email.com> wrote in message
news:u4OvHgPHGHA.2440@.TK2MSFTNGP14.phx.gbl...
> My SQL 2005 Dev Edition hosted on WinXP.
> However my another WinXP in the same network cannot connect to the SQL 2k5
> using ODBC
> Got this error:
> Connection failed:
> SQLState: '01000'
> SQL Server Error: 53
> [Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionOpen (Connect()).
> Connection failed:
> SQLState: '08001'
> SQL Server Error: 17
> [Microsof][ODBC SQL Server Driver][DBNETLIB]SQL Server does not exist or
> access denied.
> Info:
> Host machine:
> OS: WinXP SP2
> Firewall: Opened 1433 TCP, 1434 UDP
> SQL Server 2005 Dev Edit.
> Instance Name: Winxp-hongpc\SQL2K5
> Network Config: Enabled Shared Memory, Named Pipes, TCP/IP
> Inside TCP/IP setting:
> IP1:
> Active = Yes
> Enabled = Yes
> IP Address = 192.168.1.100
> TCP Dynamic Ports = [blank]
> TCP Port = 1433
> IP2:
> Active = Yes
> Enabled = No
> IP Address = 127.0.0.1
> TCP Dynamic Ports = 0
> TCP Port = [blank]
> IPAll:
> TCP Dynamic Ports: [blank]
> TCP Port: 1433
> Anyone helps?
>
well, to begin with, IP2's IP address is the loop-back address and isn't
going to communicate with anything. Check the IP config on this computer.
you may have to reinstall the tcp/ip stack.
steve.|||Thanks for your reply.
Actually I dont know why there is a IP2, since I have only I network card in
my host winxp.
I get this information from the SQL Server Configuration Manager -> SQL
Server 2005 Network Config. -> Protocols for SQL2K5-> TCP/IP -> IP Address
tab.
The setting in IP2 is there by default, I havn't changed anything.
Tried to deactive the IP2, but still dont make it work.
"molsonexpert" <imdrunk@.work.ca> ¼¶¼g©ó¶l¥ó·s»D:egUCLoPHGHA.1760@.TK2MSFTNGP10.phx.gbl...
"Jason Chan" <no@.email.com> wrote in message
news:u4OvHgPHGHA.2440@.TK2MSFTNGP14.phx.gbl...
> My SQL 2005 Dev Edition hosted on WinXP.
> However my another WinXP in the same network cannot connect to the SQL 2k5
> using ODBC
> Got this error:
> Connection failed:
> SQLState: '01000'
> SQL Server Error: 53
> [Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionOpen (Connect()).
> Connection failed:
> SQLState: '08001'
> SQL Server Error: 17
> [Microsof][ODBC SQL Server Driver][DBNETLIB]SQL Server does not exist or
> access denied.
> Info:
> Host machine:
> OS: WinXP SP2
> Firewall: Opened 1433 TCP, 1434 UDP
> SQL Server 2005 Dev Edit.
> Instance Name: Winxp-hongpc\SQL2K5
> Network Config: Enabled Shared Memory, Named Pipes, TCP/IP
> Inside TCP/IP setting:
> IP1:
> Active = Yes
> Enabled = Yes
> IP Address = 192.168.1.100
> TCP Dynamic Ports = [blank]
> TCP Port = 1433
> IP2:
> Active = Yes
> Enabled = No
> IP Address = 127.0.0.1
> TCP Dynamic Ports = 0
> TCP Port = [blank]
> IPAll:
> TCP Dynamic Ports: [blank]
> TCP Port: 1433
> Anyone helps?
>
well, to begin with, IP2's IP address is the loop-back address and isn't
going to communicate with anything. Check the IP config on this computer.
you may have to reinstall the tcp/ip stack.
steve.|||I retried and I found that I can connect using named piped, so what is the
problem for TCP/IP
"Jason Chan" <no@.email.com> ¼¶¼g©ó¶l¥ó·s»D:e047mNRHGHA.344@.TK2MSFTNGP11.phx.gbl...
Thanks for your reply.
Actually I dont know why there is a IP2, since I have only I network card in
my host winxp.
I get this information from the SQL Server Configuration Manager -> SQL
Server 2005 Network Config. -> Protocols for SQL2K5-> TCP/IP -> IP Address
tab.
The setting in IP2 is there by default, I havn't changed anything.
Tried to deactive the IP2, but still dont make it work.
"molsonexpert" <imdrunk@.work.ca> ¼¶¼g©ó¶l¥ó·s»D:egUCLoPHGHA.1760@.TK2MSFTNGP10.phx.gbl...
"Jason Chan" <no@.email.com> wrote in message
news:u4OvHgPHGHA.2440@.TK2MSFTNGP14.phx.gbl...
> My SQL 2005 Dev Edition hosted on WinXP.
> However my another WinXP in the same network cannot connect to the SQL 2k5
> using ODBC
> Got this error:
> Connection failed:
> SQLState: '01000'
> SQL Server Error: 53
> [Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionOpen (Connect()).
> Connection failed:
> SQLState: '08001'
> SQL Server Error: 17
> [Microsof][ODBC SQL Server Driver][DBNETLIB]SQL Server does not exist or
> access denied.
> Info:
> Host machine:
> OS: WinXP SP2
> Firewall: Opened 1433 TCP, 1434 UDP
> SQL Server 2005 Dev Edit.
> Instance Name: Winxp-hongpc\SQL2K5
> Network Config: Enabled Shared Memory, Named Pipes, TCP/IP
> Inside TCP/IP setting:
> IP1:
> Active = Yes
> Enabled = Yes
> IP Address = 192.168.1.100
> TCP Dynamic Ports = [blank]
> TCP Port = 1433
> IP2:
> Active = Yes
> Enabled = No
> IP Address = 127.0.0.1
> TCP Dynamic Ports = 0
> TCP Port = [blank]
> IPAll:
> TCP Dynamic Ports: [blank]
> TCP Port: 1433
> Anyone helps?
>
well, to begin with, IP2's IP address is the loop-back address and isn't
going to communicate with anything. Check the IP config on this computer.
you may have to reinstall the tcp/ip stack.
steve.|||"Jason Chan" <no@.email.com> wrote in message
news:u$rU6ORHGHA.2836@.TK2MSFTNGP14.phx.gbl...
>I retried and I found that I can connect using named piped, so what is the
> problem for TCP/IP
> "Jason Chan" <no@.email.com>
> ¼¶¼g©ó¶l¥ó·s»D:e047mNRHGHA.344@.TK2MSFTNGP11.phx.gbl...
> Thanks for your reply.
> Actually I dont know why there is a IP2, since I have only I network card
> in
> my host winxp.
> I get this information from the SQL Server Configuration Manager -> SQL
> Server 2005 Network Config. -> Protocols for SQL2K5-> TCP/IP -> IP Address
> tab.
> The setting in IP2 is there by default, I havn't changed anything.
> Tried to deactive the IP2, but still dont make it work.
> "molsonexpert" <imdrunk@.work.ca>
> ¼¶¼g©ó¶l¥ó·s»D:egUCLoPHGHA.1760@.TK2MSFTNGP10.phx.gbl...
> "Jason Chan" <no@.email.com> wrote in message
> news:u4OvHgPHGHA.2440@.TK2MSFTNGP14.phx.gbl...
>> My SQL 2005 Dev Edition hosted on WinXP.
>> However my another WinXP in the same network cannot connect to the SQL
>> 2k5
>> using ODBC
>> Got this error:
>> Connection failed:
>> SQLState: '01000'
>> SQL Server Error: 53
>> [Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionOpen (Connect()).
>> Connection failed:
>> SQLState: '08001'
>> SQL Server Error: 17
>> [Microsof][ODBC SQL Server Driver][DBNETLIB]SQL Server does not exist or
>> access denied.
>> Info:
>> Host machine:
>> OS: WinXP SP2
>> Firewall: Opened 1433 TCP, 1434 UDP
>> SQL Server 2005 Dev Edit.
>> Instance Name: Winxp-hongpc\SQL2K5
>> Network Config: Enabled Shared Memory, Named Pipes, TCP/IP
>> Inside TCP/IP setting:
>> IP1:
>> Active = Yes
>> Enabled = Yes
>> IP Address = 192.168.1.100
>> TCP Dynamic Ports = [blank]
>> TCP Port = 1433
>> IP2:
>> Active = Yes
>> Enabled = No
>> IP Address = 127.0.0.1
>> TCP Dynamic Ports = 0
>> TCP Port = [blank]
>> IPAll:
>> TCP Dynamic Ports: [blank]
>> TCP Port: 1433
>> Anyone helps?
>>
> well, to begin with, IP2's IP address is the loop-back address and isn't
> going to communicate with anything. Check the IP config on this computer.
> you may have to reinstall the tcp/ip stack.
> steve.
>
>
Try these:
http://support.microsoft.com/search/default.aspx?spid=2855&query=sql+server+error+53&catalog=LCID%3D1033&pwt=true&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode=a&x=11&y=16
http://tinyurl.com/7ef8v
steve.|||As mentioned, 127.0.0.1 is the loopback adapter. Essentially that's the
network card connecting to itself. This comes with the network card and is
intended for troubleshooting. It's only avalable if you are connecting from
the same computer, so in your case you can just ignore it.
--
Rick Byham
MCDBA, MCSE, MCSA
Lead Technical Writer,
Microsoft, SQL Server Books Online
This posting is provided "as is" with
no warranties, and confers no rights.
"Jason Chan" <no@.email.com> wrote in message
news:u$rU6ORHGHA.2836@.TK2MSFTNGP14.phx.gbl...
>I retried and I found that I can connect using named piped, so what is the
> problem for TCP/IP
> "Jason Chan" <no@.email.com>
> ¼¶¼g©ó¶l¥ó·s»D:e047mNRHGHA.344@.TK2MSFTNGP11.phx.gbl...
> Thanks for your reply.
> Actually I dont know why there is a IP2, since I have only I network card
> in
> my host winxp.
> I get this information from the SQL Server Configuration Manager -> SQL
> Server 2005 Network Config. -> Protocols for SQL2K5-> TCP/IP -> IP Address
> tab.
> The setting in IP2 is there by default, I havn't changed anything.
> Tried to deactive the IP2, but still dont make it work.
> "molsonexpert" <imdrunk@.work.ca>
> ¼¶¼g©ó¶l¥ó·s»D:egUCLoPHGHA.1760@.TK2MSFTNGP10.phx.gbl...
> "Jason Chan" <no@.email.com> wrote in message
> news:u4OvHgPHGHA.2440@.TK2MSFTNGP14.phx.gbl...
>> My SQL 2005 Dev Edition hosted on WinXP.
>> However my another WinXP in the same network cannot connect to the SQL
>> 2k5
>> using ODBC
>> Got this error:
>> Connection failed:
>> SQLState: '01000'
>> SQL Server Error: 53
>> [Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionOpen (Connect()).
>> Connection failed:
>> SQLState: '08001'
>> SQL Server Error: 17
>> [Microsof][ODBC SQL Server Driver][DBNETLIB]SQL Server does not exist or
>> access denied.
>> Info:
>> Host machine:
>> OS: WinXP SP2
>> Firewall: Opened 1433 TCP, 1434 UDP
>> SQL Server 2005 Dev Edit.
>> Instance Name: Winxp-hongpc\SQL2K5
>> Network Config: Enabled Shared Memory, Named Pipes, TCP/IP
>> Inside TCP/IP setting:
>> IP1:
>> Active = Yes
>> Enabled = Yes
>> IP Address = 192.168.1.100
>> TCP Dynamic Ports = [blank]
>> TCP Port = 1433
>> IP2:
>> Active = Yes
>> Enabled = No
>> IP Address = 127.0.0.1
>> TCP Dynamic Ports = 0
>> TCP Port = [blank]
>> IPAll:
>> TCP Dynamic Ports: [blank]
>> TCP Port: 1433
>> Anyone helps?
>>
> well, to begin with, IP2's IP address is the loop-back address and isn't
> going to communicate with anything. Check the IP config on this computer.
> you may have to reinstall the tcp/ip stack.
> steve.
>
>
However my another WinXP in the same network cannot connect to the SQL 2k5
using ODBC
Got this error:
Connection failed:
SQLState: '01000'
SQL Server Error: 53
[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionOpen (Connect()).
Connection failed:
SQLState: '08001'
SQL Server Error: 17
[Microsof][ODBC SQL Server Driver][DBNETLIB]SQL Server does not exist or
access denied.
Info:
Host machine:
OS: WinXP SP2
Firewall: Opened 1433 TCP, 1434 UDP
SQL Server 2005 Dev Edit.
Instance Name: Winxp-hongpc\SQL2K5
Network Config: Enabled Shared Memory, Named Pipes, TCP/IP
Inside TCP/IP setting:
IP1:
Active = Yes
Enabled = Yes
IP Address = 192.168.1.100
TCP Dynamic Ports = [blank]
TCP Port = 1433
IP2:
Active = Yes
Enabled = No
IP Address = 127.0.0.1
TCP Dynamic Ports = 0
TCP Port = [blank]
IPAll:
TCP Dynamic Ports: [blank]
TCP Port: 1433
Anyone helps?"Jason Chan" <no@.email.com> wrote in message
news:u4OvHgPHGHA.2440@.TK2MSFTNGP14.phx.gbl...
> My SQL 2005 Dev Edition hosted on WinXP.
> However my another WinXP in the same network cannot connect to the SQL 2k5
> using ODBC
> Got this error:
> Connection failed:
> SQLState: '01000'
> SQL Server Error: 53
> [Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionOpen (Connect()).
> Connection failed:
> SQLState: '08001'
> SQL Server Error: 17
> [Microsof][ODBC SQL Server Driver][DBNETLIB]SQL Server does not exist or
> access denied.
> Info:
> Host machine:
> OS: WinXP SP2
> Firewall: Opened 1433 TCP, 1434 UDP
> SQL Server 2005 Dev Edit.
> Instance Name: Winxp-hongpc\SQL2K5
> Network Config: Enabled Shared Memory, Named Pipes, TCP/IP
> Inside TCP/IP setting:
> IP1:
> Active = Yes
> Enabled = Yes
> IP Address = 192.168.1.100
> TCP Dynamic Ports = [blank]
> TCP Port = 1433
> IP2:
> Active = Yes
> Enabled = No
> IP Address = 127.0.0.1
> TCP Dynamic Ports = 0
> TCP Port = [blank]
> IPAll:
> TCP Dynamic Ports: [blank]
> TCP Port: 1433
> Anyone helps?
>
well, to begin with, IP2's IP address is the loop-back address and isn't
going to communicate with anything. Check the IP config on this computer.
you may have to reinstall the tcp/ip stack.
steve.|||Thanks for your reply.
Actually I dont know why there is a IP2, since I have only I network card in
my host winxp.
I get this information from the SQL Server Configuration Manager -> SQL
Server 2005 Network Config. -> Protocols for SQL2K5-> TCP/IP -> IP Address
tab.
The setting in IP2 is there by default, I havn't changed anything.
Tried to deactive the IP2, but still dont make it work.
"molsonexpert" <imdrunk@.work.ca> ¼¶¼g©ó¶l¥ó·s»D:egUCLoPHGHA.1760@.TK2MSFTNGP10.phx.gbl...
"Jason Chan" <no@.email.com> wrote in message
news:u4OvHgPHGHA.2440@.TK2MSFTNGP14.phx.gbl...
> My SQL 2005 Dev Edition hosted on WinXP.
> However my another WinXP in the same network cannot connect to the SQL 2k5
> using ODBC
> Got this error:
> Connection failed:
> SQLState: '01000'
> SQL Server Error: 53
> [Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionOpen (Connect()).
> Connection failed:
> SQLState: '08001'
> SQL Server Error: 17
> [Microsof][ODBC SQL Server Driver][DBNETLIB]SQL Server does not exist or
> access denied.
> Info:
> Host machine:
> OS: WinXP SP2
> Firewall: Opened 1433 TCP, 1434 UDP
> SQL Server 2005 Dev Edit.
> Instance Name: Winxp-hongpc\SQL2K5
> Network Config: Enabled Shared Memory, Named Pipes, TCP/IP
> Inside TCP/IP setting:
> IP1:
> Active = Yes
> Enabled = Yes
> IP Address = 192.168.1.100
> TCP Dynamic Ports = [blank]
> TCP Port = 1433
> IP2:
> Active = Yes
> Enabled = No
> IP Address = 127.0.0.1
> TCP Dynamic Ports = 0
> TCP Port = [blank]
> IPAll:
> TCP Dynamic Ports: [blank]
> TCP Port: 1433
> Anyone helps?
>
well, to begin with, IP2's IP address is the loop-back address and isn't
going to communicate with anything. Check the IP config on this computer.
you may have to reinstall the tcp/ip stack.
steve.|||I retried and I found that I can connect using named piped, so what is the
problem for TCP/IP
"Jason Chan" <no@.email.com> ¼¶¼g©ó¶l¥ó·s»D:e047mNRHGHA.344@.TK2MSFTNGP11.phx.gbl...
Thanks for your reply.
Actually I dont know why there is a IP2, since I have only I network card in
my host winxp.
I get this information from the SQL Server Configuration Manager -> SQL
Server 2005 Network Config. -> Protocols for SQL2K5-> TCP/IP -> IP Address
tab.
The setting in IP2 is there by default, I havn't changed anything.
Tried to deactive the IP2, but still dont make it work.
"molsonexpert" <imdrunk@.work.ca> ¼¶¼g©ó¶l¥ó·s»D:egUCLoPHGHA.1760@.TK2MSFTNGP10.phx.gbl...
"Jason Chan" <no@.email.com> wrote in message
news:u4OvHgPHGHA.2440@.TK2MSFTNGP14.phx.gbl...
> My SQL 2005 Dev Edition hosted on WinXP.
> However my another WinXP in the same network cannot connect to the SQL 2k5
> using ODBC
> Got this error:
> Connection failed:
> SQLState: '01000'
> SQL Server Error: 53
> [Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionOpen (Connect()).
> Connection failed:
> SQLState: '08001'
> SQL Server Error: 17
> [Microsof][ODBC SQL Server Driver][DBNETLIB]SQL Server does not exist or
> access denied.
> Info:
> Host machine:
> OS: WinXP SP2
> Firewall: Opened 1433 TCP, 1434 UDP
> SQL Server 2005 Dev Edit.
> Instance Name: Winxp-hongpc\SQL2K5
> Network Config: Enabled Shared Memory, Named Pipes, TCP/IP
> Inside TCP/IP setting:
> IP1:
> Active = Yes
> Enabled = Yes
> IP Address = 192.168.1.100
> TCP Dynamic Ports = [blank]
> TCP Port = 1433
> IP2:
> Active = Yes
> Enabled = No
> IP Address = 127.0.0.1
> TCP Dynamic Ports = 0
> TCP Port = [blank]
> IPAll:
> TCP Dynamic Ports: [blank]
> TCP Port: 1433
> Anyone helps?
>
well, to begin with, IP2's IP address is the loop-back address and isn't
going to communicate with anything. Check the IP config on this computer.
you may have to reinstall the tcp/ip stack.
steve.|||"Jason Chan" <no@.email.com> wrote in message
news:u$rU6ORHGHA.2836@.TK2MSFTNGP14.phx.gbl...
>I retried and I found that I can connect using named piped, so what is the
> problem for TCP/IP
> "Jason Chan" <no@.email.com>
> ¼¶¼g©ó¶l¥ó·s»D:e047mNRHGHA.344@.TK2MSFTNGP11.phx.gbl...
> Thanks for your reply.
> Actually I dont know why there is a IP2, since I have only I network card
> in
> my host winxp.
> I get this information from the SQL Server Configuration Manager -> SQL
> Server 2005 Network Config. -> Protocols for SQL2K5-> TCP/IP -> IP Address
> tab.
> The setting in IP2 is there by default, I havn't changed anything.
> Tried to deactive the IP2, but still dont make it work.
> "molsonexpert" <imdrunk@.work.ca>
> ¼¶¼g©ó¶l¥ó·s»D:egUCLoPHGHA.1760@.TK2MSFTNGP10.phx.gbl...
> "Jason Chan" <no@.email.com> wrote in message
> news:u4OvHgPHGHA.2440@.TK2MSFTNGP14.phx.gbl...
>> My SQL 2005 Dev Edition hosted on WinXP.
>> However my another WinXP in the same network cannot connect to the SQL
>> 2k5
>> using ODBC
>> Got this error:
>> Connection failed:
>> SQLState: '01000'
>> SQL Server Error: 53
>> [Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionOpen (Connect()).
>> Connection failed:
>> SQLState: '08001'
>> SQL Server Error: 17
>> [Microsof][ODBC SQL Server Driver][DBNETLIB]SQL Server does not exist or
>> access denied.
>> Info:
>> Host machine:
>> OS: WinXP SP2
>> Firewall: Opened 1433 TCP, 1434 UDP
>> SQL Server 2005 Dev Edit.
>> Instance Name: Winxp-hongpc\SQL2K5
>> Network Config: Enabled Shared Memory, Named Pipes, TCP/IP
>> Inside TCP/IP setting:
>> IP1:
>> Active = Yes
>> Enabled = Yes
>> IP Address = 192.168.1.100
>> TCP Dynamic Ports = [blank]
>> TCP Port = 1433
>> IP2:
>> Active = Yes
>> Enabled = No
>> IP Address = 127.0.0.1
>> TCP Dynamic Ports = 0
>> TCP Port = [blank]
>> IPAll:
>> TCP Dynamic Ports: [blank]
>> TCP Port: 1433
>> Anyone helps?
>>
> well, to begin with, IP2's IP address is the loop-back address and isn't
> going to communicate with anything. Check the IP config on this computer.
> you may have to reinstall the tcp/ip stack.
> steve.
>
>
Try these:
http://support.microsoft.com/search/default.aspx?spid=2855&query=sql+server+error+53&catalog=LCID%3D1033&pwt=true&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode=a&x=11&y=16
http://tinyurl.com/7ef8v
steve.|||As mentioned, 127.0.0.1 is the loopback adapter. Essentially that's the
network card connecting to itself. This comes with the network card and is
intended for troubleshooting. It's only avalable if you are connecting from
the same computer, so in your case you can just ignore it.
--
Rick Byham
MCDBA, MCSE, MCSA
Lead Technical Writer,
Microsoft, SQL Server Books Online
This posting is provided "as is" with
no warranties, and confers no rights.
"Jason Chan" <no@.email.com> wrote in message
news:u$rU6ORHGHA.2836@.TK2MSFTNGP14.phx.gbl...
>I retried and I found that I can connect using named piped, so what is the
> problem for TCP/IP
> "Jason Chan" <no@.email.com>
> ¼¶¼g©ó¶l¥ó·s»D:e047mNRHGHA.344@.TK2MSFTNGP11.phx.gbl...
> Thanks for your reply.
> Actually I dont know why there is a IP2, since I have only I network card
> in
> my host winxp.
> I get this information from the SQL Server Configuration Manager -> SQL
> Server 2005 Network Config. -> Protocols for SQL2K5-> TCP/IP -> IP Address
> tab.
> The setting in IP2 is there by default, I havn't changed anything.
> Tried to deactive the IP2, but still dont make it work.
> "molsonexpert" <imdrunk@.work.ca>
> ¼¶¼g©ó¶l¥ó·s»D:egUCLoPHGHA.1760@.TK2MSFTNGP10.phx.gbl...
> "Jason Chan" <no@.email.com> wrote in message
> news:u4OvHgPHGHA.2440@.TK2MSFTNGP14.phx.gbl...
>> My SQL 2005 Dev Edition hosted on WinXP.
>> However my another WinXP in the same network cannot connect to the SQL
>> 2k5
>> using ODBC
>> Got this error:
>> Connection failed:
>> SQLState: '01000'
>> SQL Server Error: 53
>> [Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionOpen (Connect()).
>> Connection failed:
>> SQLState: '08001'
>> SQL Server Error: 17
>> [Microsof][ODBC SQL Server Driver][DBNETLIB]SQL Server does not exist or
>> access denied.
>> Info:
>> Host machine:
>> OS: WinXP SP2
>> Firewall: Opened 1433 TCP, 1434 UDP
>> SQL Server 2005 Dev Edit.
>> Instance Name: Winxp-hongpc\SQL2K5
>> Network Config: Enabled Shared Memory, Named Pipes, TCP/IP
>> Inside TCP/IP setting:
>> IP1:
>> Active = Yes
>> Enabled = Yes
>> IP Address = 192.168.1.100
>> TCP Dynamic Ports = [blank]
>> TCP Port = 1433
>> IP2:
>> Active = Yes
>> Enabled = No
>> IP Address = 127.0.0.1
>> TCP Dynamic Ports = 0
>> TCP Port = [blank]
>> IPAll:
>> TCP Dynamic Ports: [blank]
>> TCP Port: 1433
>> Anyone helps?
>>
> well, to begin with, IP2's IP address is the loop-back address and isn't
> going to communicate with anything. Check the IP config on this computer.
> you may have to reinstall the tcp/ip stack.
> steve.
>
>
Cannot connect to remote SQL 2k5 server in local network
My SQL 2005 Dev Edition hosted on WinXP.
However my another WinXP in the same network cannot connect to the SQL 2k5
using ODBC
Got this error:
Connection failed:
SQLState: '01000'
SQL Server Error: 53
[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionOpen (Con
nect()).
Connection failed:
SQLState: '08001'
SQL Server Error: 17
[Microsof][ODBC SQL Server Driver][DBNETLIB]SQL Server does not
exist or
access denied.
Info:
Host machine:
OS: WinXP SP2
Firewall: Opened 1433 TCP, 1434 UDP
SQL Server 2005 Dev Edit.
Instance Name: Winxp-hongpc\SQL2K5
Network Config: Enabled Shared Memory, Named Pipes, TCP/IP
Inside TCP/IP setting:
IP1:
Active = Yes
Enabled = Yes
IP Address = 192.168.1.100
TCP Dynamic Ports = [blank]
TCP Port = 1433
IP2:
Active = Yes
Enabled = No
IP Address = 127.0.0.1
TCP Dynamic Ports = 0
TCP Port = [blank]
IPAll:
TCP Dynamic Ports: [blank]
TCP Port: 1433
Anyone helps?"Jason Chan" <no@.email.com> wrote in message
news:u4OvHgPHGHA.2440@.TK2MSFTNGP14.phx.gbl...
> My SQL 2005 Dev Edition hosted on WinXP.
> However my another WinXP in the same network cannot connect to the SQL 2k5
> using ODBC
> Got this error:
> Connection failed:
> SQLState: '01000'
> SQL Server Error: 53
> [Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionOpen (C
onnect()).
> Connection failed:
> SQLState: '08001'
> SQL Server Error: 17
> [Microsof][ODBC SQL Server Driver][DBNETLIB]SQL Server does no
t exist or
> access denied.
> Info:
> Host machine:
> OS: WinXP SP2
> Firewall: Opened 1433 TCP, 1434 UDP
> SQL Server 2005 Dev Edit.
> Instance Name: Winxp-hongpc\SQL2K5
> Network Config: Enabled Shared Memory, Named Pipes, TCP/IP
> Inside TCP/IP setting:
> IP1:
> Active = Yes
> Enabled = Yes
> IP Address = 192.168.1.100
> TCP Dynamic Ports = [blank]
> TCP Port = 1433
> IP2:
> Active = Yes
> Enabled = No
> IP Address = 127.0.0.1
> TCP Dynamic Ports = 0
> TCP Port = [blank]
> IPAll:
> TCP Dynamic Ports: [blank]
> TCP Port: 1433
> Anyone helps?
>
well, to begin with, IP2's IP address is the loop-back address and isn't
going to communicate with anything. Check the IP config on this computer.
you may have to reinstall the tcp/ip stack.
steve.|||Thanks for your reply.
Actually I dont know why there is a IP2, since I have only I network card in
my host winxp.
I get this information from the SQL Server Configuration Manager -> SQL
Server 2005 Network Config. -> Protocols for SQL2K5-> TCP/IP -> IP Address
tab.
The setting in IP2 is there by default, I havn't changed anything.
Tried to deactive the IP2, but still dont make it work.
"molsonexpert" <imdrunk@.work.ca> glsD:egUCLoPHGHA.1760@.TK2MSFTNGP1
0.phx.gbl...
"Jason Chan" <no@.email.com> wrote in message
news:u4OvHgPHGHA.2440@.TK2MSFTNGP14.phx.gbl...
> My SQL 2005 Dev Edition hosted on WinXP.
> However my another WinXP in the same network cannot connect to the SQL 2k5
> using ODBC
> Got this error:
> Connection failed:
> SQLState: '01000'
> SQL Server Error: 53
> [Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionOpen (C
onnect()).
> Connection failed:
> SQLState: '08001'
> SQL Server Error: 17
> [Microsof][ODBC SQL Server Driver][DBNETLIB]SQL Server does no
t exist or
> access denied.
> Info:
> Host machine:
> OS: WinXP SP2
> Firewall: Opened 1433 TCP, 1434 UDP
> SQL Server 2005 Dev Edit.
> Instance Name: Winxp-hongpc\SQL2K5
> Network Config: Enabled Shared Memory, Named Pipes, TCP/IP
> Inside TCP/IP setting:
> IP1:
> Active = Yes
> Enabled = Yes
> IP Address = 192.168.1.100
> TCP Dynamic Ports = [blank]
> TCP Port = 1433
> IP2:
> Active = Yes
> Enabled = No
> IP Address = 127.0.0.1
> TCP Dynamic Ports = 0
> TCP Port = [blank]
> IPAll:
> TCP Dynamic Ports: [blank]
> TCP Port: 1433
> Anyone helps?
>
well, to begin with, IP2's IP address is the loop-back address and isn't
going to communicate with anything. Check the IP config on this computer.
you may have to reinstall the tcp/ip stack.
steve.|||I retried and I found that I can connect using named piped, so what is the
problem for TCP/IP
"Jason Chan" <no@.email.com> glsD:e047mNRHGHA.344@.TK2MSFTNGP11.phx.
gbl...
Thanks for your reply.
Actually I dont know why there is a IP2, since I have only I network card in
my host winxp.
I get this information from the SQL Server Configuration Manager -> SQL
Server 2005 Network Config. -> Protocols for SQL2K5-> TCP/IP -> IP Address
tab.
The setting in IP2 is there by default, I havn't changed anything.
Tried to deactive the IP2, but still dont make it work.
"molsonexpert" <imdrunk@.work.ca> glsD:egUCLoPHGHA.1760@.TK2MSFTNGP1
0.phx.gbl...
"Jason Chan" <no@.email.com> wrote in message
news:u4OvHgPHGHA.2440@.TK2MSFTNGP14.phx.gbl...
> My SQL 2005 Dev Edition hosted on WinXP.
> However my another WinXP in the same network cannot connect to the SQL 2k5
> using ODBC
> Got this error:
> Connection failed:
> SQLState: '01000'
> SQL Server Error: 53
> [Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionOpen (C
onnect()).
> Connection failed:
> SQLState: '08001'
> SQL Server Error: 17
> [Microsof][ODBC SQL Server Driver][DBNETLIB]SQL Server does no
t exist or
> access denied.
> Info:
> Host machine:
> OS: WinXP SP2
> Firewall: Opened 1433 TCP, 1434 UDP
> SQL Server 2005 Dev Edit.
> Instance Name: Winxp-hongpc\SQL2K5
> Network Config: Enabled Shared Memory, Named Pipes, TCP/IP
> Inside TCP/IP setting:
> IP1:
> Active = Yes
> Enabled = Yes
> IP Address = 192.168.1.100
> TCP Dynamic Ports = [blank]
> TCP Port = 1433
> IP2:
> Active = Yes
> Enabled = No
> IP Address = 127.0.0.1
> TCP Dynamic Ports = 0
> TCP Port = [blank]
> IPAll:
> TCP Dynamic Ports: [blank]
> TCP Port: 1433
> Anyone helps?
>
well, to begin with, IP2's IP address is the loop-back address and isn't
going to communicate with anything. Check the IP config on this computer.
you may have to reinstall the tcp/ip stack.
steve.|||"Jason Chan" <no@.email.com> wrote in message
news:u$rU6ORHGHA.2836@.TK2MSFTNGP14.phx.gbl...
>I retried and I found that I can connect using named piped, so what is the
> problem for TCP/IP
> "Jason Chan" <no@.email.com>
> glsD:e047mNRHGHA.344@.TK2MSFTNGP11.phx.gbl...
> Thanks for your reply.
> Actually I dont know why there is a IP2, since I have only I network card
> in
> my host winxp.
> I get this information from the SQL Server Configuration Manager -> SQL
> Server 2005 Network Config. -> Protocols for SQL2K5-> TCP/IP -> IP Address
> tab.
> The setting in IP2 is there by default, I havn't changed anything.
> Tried to deactive the IP2, but still dont make it work.
> "molsonexpert" <imdrunk@.work.ca>
> glsD:egUCLoPHGHA.1760@.TK2MSFTNGP10.phx.gbl...
> "Jason Chan" <no@.email.com> wrote in message
> news:u4OvHgPHGHA.2440@.TK2MSFTNGP14.phx.gbl...
> well, to begin with, IP2's IP address is the loop-back address and isn't
> going to communicate with anything. Check the IP config on this computer.
> you may have to reinstall the tcp/ip stack.
> steve.
>
>
Try these:
http://support.microsoft.com/search...ode=a&x=11&y=16
http://tinyurl.com/7ef8v
steve.|||As mentioned, 127.0.0.1 is the loopback adapter. Essentially that's the
network card connecting to itself. This comes with the network card and is
intended for troubleshooting. It's only avalable if you are connecting from
the same computer, so in your case you can just ignore it.
--
Rick Byham
MCDBA, MCSE, MCSA
Lead Technical Writer,
Microsoft, SQL Server Books Online
This posting is provided "as is" with
no warranties, and confers no rights.
"Jason Chan" <no@.email.com> wrote in message
news:u$rU6ORHGHA.2836@.TK2MSFTNGP14.phx.gbl...
>I retried and I found that I can connect using named piped, so what is the
> problem for TCP/IP
> "Jason Chan" <no@.email.com>
> glsD:e047mNRHGHA.344@.TK2MSFTNGP11.phx.gbl...
> Thanks for your reply.
> Actually I dont know why there is a IP2, since I have only I network card
> in
> my host winxp.
> I get this information from the SQL Server Configuration Manager -> SQL
> Server 2005 Network Config. -> Protocols for SQL2K5-> TCP/IP -> IP Address
> tab.
> The setting in IP2 is there by default, I havn't changed anything.
> Tried to deactive the IP2, but still dont make it work.
> "molsonexpert" <imdrunk@.work.ca>
> glsD:egUCLoPHGHA.1760@.TK2MSFTNGP10.phx.gbl...
> "Jason Chan" <no@.email.com> wrote in message
> news:u4OvHgPHGHA.2440@.TK2MSFTNGP14.phx.gbl...
> well, to begin with, IP2's IP address is the loop-back address and isn't
> going to communicate with anything. Check the IP config on this computer.
> you may have to reinstall the tcp/ip stack.
> steve.
>
>
However my another WinXP in the same network cannot connect to the SQL 2k5
using ODBC
Got this error:
Connection failed:
SQLState: '01000'
SQL Server Error: 53
[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionOpen (Con
nect()).
Connection failed:
SQLState: '08001'
SQL Server Error: 17
[Microsof][ODBC SQL Server Driver][DBNETLIB]SQL Server does not
exist or
access denied.
Info:
Host machine:
OS: WinXP SP2
Firewall: Opened 1433 TCP, 1434 UDP
SQL Server 2005 Dev Edit.
Instance Name: Winxp-hongpc\SQL2K5
Network Config: Enabled Shared Memory, Named Pipes, TCP/IP
Inside TCP/IP setting:
IP1:
Active = Yes
Enabled = Yes
IP Address = 192.168.1.100
TCP Dynamic Ports = [blank]
TCP Port = 1433
IP2:
Active = Yes
Enabled = No
IP Address = 127.0.0.1
TCP Dynamic Ports = 0
TCP Port = [blank]
IPAll:
TCP Dynamic Ports: [blank]
TCP Port: 1433
Anyone helps?"Jason Chan" <no@.email.com> wrote in message
news:u4OvHgPHGHA.2440@.TK2MSFTNGP14.phx.gbl...
> My SQL 2005 Dev Edition hosted on WinXP.
> However my another WinXP in the same network cannot connect to the SQL 2k5
> using ODBC
> Got this error:
> Connection failed:
> SQLState: '01000'
> SQL Server Error: 53
> [Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionOpen (C
onnect()).
> Connection failed:
> SQLState: '08001'
> SQL Server Error: 17
> [Microsof][ODBC SQL Server Driver][DBNETLIB]SQL Server does no
t exist or
> access denied.
> Info:
> Host machine:
> OS: WinXP SP2
> Firewall: Opened 1433 TCP, 1434 UDP
> SQL Server 2005 Dev Edit.
> Instance Name: Winxp-hongpc\SQL2K5
> Network Config: Enabled Shared Memory, Named Pipes, TCP/IP
> Inside TCP/IP setting:
> IP1:
> Active = Yes
> Enabled = Yes
> IP Address = 192.168.1.100
> TCP Dynamic Ports = [blank]
> TCP Port = 1433
> IP2:
> Active = Yes
> Enabled = No
> IP Address = 127.0.0.1
> TCP Dynamic Ports = 0
> TCP Port = [blank]
> IPAll:
> TCP Dynamic Ports: [blank]
> TCP Port: 1433
> Anyone helps?
>
well, to begin with, IP2's IP address is the loop-back address and isn't
going to communicate with anything. Check the IP config on this computer.
you may have to reinstall the tcp/ip stack.
steve.|||Thanks for your reply.
Actually I dont know why there is a IP2, since I have only I network card in
my host winxp.
I get this information from the SQL Server Configuration Manager -> SQL
Server 2005 Network Config. -> Protocols for SQL2K5-> TCP/IP -> IP Address
tab.
The setting in IP2 is there by default, I havn't changed anything.
Tried to deactive the IP2, but still dont make it work.
"molsonexpert" <imdrunk@.work.ca> glsD:egUCLoPHGHA.1760@.TK2MSFTNGP1
0.phx.gbl...
"Jason Chan" <no@.email.com> wrote in message
news:u4OvHgPHGHA.2440@.TK2MSFTNGP14.phx.gbl...
> My SQL 2005 Dev Edition hosted on WinXP.
> However my another WinXP in the same network cannot connect to the SQL 2k5
> using ODBC
> Got this error:
> Connection failed:
> SQLState: '01000'
> SQL Server Error: 53
> [Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionOpen (C
onnect()).
> Connection failed:
> SQLState: '08001'
> SQL Server Error: 17
> [Microsof][ODBC SQL Server Driver][DBNETLIB]SQL Server does no
t exist or
> access denied.
> Info:
> Host machine:
> OS: WinXP SP2
> Firewall: Opened 1433 TCP, 1434 UDP
> SQL Server 2005 Dev Edit.
> Instance Name: Winxp-hongpc\SQL2K5
> Network Config: Enabled Shared Memory, Named Pipes, TCP/IP
> Inside TCP/IP setting:
> IP1:
> Active = Yes
> Enabled = Yes
> IP Address = 192.168.1.100
> TCP Dynamic Ports = [blank]
> TCP Port = 1433
> IP2:
> Active = Yes
> Enabled = No
> IP Address = 127.0.0.1
> TCP Dynamic Ports = 0
> TCP Port = [blank]
> IPAll:
> TCP Dynamic Ports: [blank]
> TCP Port: 1433
> Anyone helps?
>
well, to begin with, IP2's IP address is the loop-back address and isn't
going to communicate with anything. Check the IP config on this computer.
you may have to reinstall the tcp/ip stack.
steve.|||I retried and I found that I can connect using named piped, so what is the
problem for TCP/IP
"Jason Chan" <no@.email.com> glsD:e047mNRHGHA.344@.TK2MSFTNGP11.phx.
gbl...
Thanks for your reply.
Actually I dont know why there is a IP2, since I have only I network card in
my host winxp.
I get this information from the SQL Server Configuration Manager -> SQL
Server 2005 Network Config. -> Protocols for SQL2K5-> TCP/IP -> IP Address
tab.
The setting in IP2 is there by default, I havn't changed anything.
Tried to deactive the IP2, but still dont make it work.
"molsonexpert" <imdrunk@.work.ca> glsD:egUCLoPHGHA.1760@.TK2MSFTNGP1
0.phx.gbl...
"Jason Chan" <no@.email.com> wrote in message
news:u4OvHgPHGHA.2440@.TK2MSFTNGP14.phx.gbl...
> My SQL 2005 Dev Edition hosted on WinXP.
> However my another WinXP in the same network cannot connect to the SQL 2k5
> using ODBC
> Got this error:
> Connection failed:
> SQLState: '01000'
> SQL Server Error: 53
> [Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionOpen (C
onnect()).
> Connection failed:
> SQLState: '08001'
> SQL Server Error: 17
> [Microsof][ODBC SQL Server Driver][DBNETLIB]SQL Server does no
t exist or
> access denied.
> Info:
> Host machine:
> OS: WinXP SP2
> Firewall: Opened 1433 TCP, 1434 UDP
> SQL Server 2005 Dev Edit.
> Instance Name: Winxp-hongpc\SQL2K5
> Network Config: Enabled Shared Memory, Named Pipes, TCP/IP
> Inside TCP/IP setting:
> IP1:
> Active = Yes
> Enabled = Yes
> IP Address = 192.168.1.100
> TCP Dynamic Ports = [blank]
> TCP Port = 1433
> IP2:
> Active = Yes
> Enabled = No
> IP Address = 127.0.0.1
> TCP Dynamic Ports = 0
> TCP Port = [blank]
> IPAll:
> TCP Dynamic Ports: [blank]
> TCP Port: 1433
> Anyone helps?
>
well, to begin with, IP2's IP address is the loop-back address and isn't
going to communicate with anything. Check the IP config on this computer.
you may have to reinstall the tcp/ip stack.
steve.|||"Jason Chan" <no@.email.com> wrote in message
news:u$rU6ORHGHA.2836@.TK2MSFTNGP14.phx.gbl...
>I retried and I found that I can connect using named piped, so what is the
> problem for TCP/IP
> "Jason Chan" <no@.email.com>
> glsD:e047mNRHGHA.344@.TK2MSFTNGP11.phx.gbl...
> Thanks for your reply.
> Actually I dont know why there is a IP2, since I have only I network card
> in
> my host winxp.
> I get this information from the SQL Server Configuration Manager -> SQL
> Server 2005 Network Config. -> Protocols for SQL2K5-> TCP/IP -> IP Address
> tab.
> The setting in IP2 is there by default, I havn't changed anything.
> Tried to deactive the IP2, but still dont make it work.
> "molsonexpert" <imdrunk@.work.ca>
> glsD:egUCLoPHGHA.1760@.TK2MSFTNGP10.phx.gbl...
> "Jason Chan" <no@.email.com> wrote in message
> news:u4OvHgPHGHA.2440@.TK2MSFTNGP14.phx.gbl...
> well, to begin with, IP2's IP address is the loop-back address and isn't
> going to communicate with anything. Check the IP config on this computer.
> you may have to reinstall the tcp/ip stack.
> steve.
>
>
Try these:
http://support.microsoft.com/search...ode=a&x=11&y=16
http://tinyurl.com/7ef8v
steve.|||As mentioned, 127.0.0.1 is the loopback adapter. Essentially that's the
network card connecting to itself. This comes with the network card and is
intended for troubleshooting. It's only avalable if you are connecting from
the same computer, so in your case you can just ignore it.
--
Rick Byham
MCDBA, MCSE, MCSA
Lead Technical Writer,
Microsoft, SQL Server Books Online
This posting is provided "as is" with
no warranties, and confers no rights.
"Jason Chan" <no@.email.com> wrote in message
news:u$rU6ORHGHA.2836@.TK2MSFTNGP14.phx.gbl...
>I retried and I found that I can connect using named piped, so what is the
> problem for TCP/IP
> "Jason Chan" <no@.email.com>
> glsD:e047mNRHGHA.344@.TK2MSFTNGP11.phx.gbl...
> Thanks for your reply.
> Actually I dont know why there is a IP2, since I have only I network card
> in
> my host winxp.
> I get this information from the SQL Server Configuration Manager -> SQL
> Server 2005 Network Config. -> Protocols for SQL2K5-> TCP/IP -> IP Address
> tab.
> The setting in IP2 is there by default, I havn't changed anything.
> Tried to deactive the IP2, but still dont make it work.
> "molsonexpert" <imdrunk@.work.ca>
> glsD:egUCLoPHGHA.1760@.TK2MSFTNGP10.phx.gbl...
> "Jason Chan" <no@.email.com> wrote in message
> news:u4OvHgPHGHA.2440@.TK2MSFTNGP14.phx.gbl...
> well, to begin with, IP2's IP address is the loop-back address and isn't
> going to communicate with anything. Check the IP config on this computer.
> you may have to reinstall the tcp/ip stack.
> steve.
>
>
Friday, February 10, 2012
Cannot connect SQL server 2005 Express with VWD 2005
I have installed MS Visual Web Developer 2005 Express Edition on my Notebook (WinXP Pro SP2). And it's working fine. Then I tried installed SQL Server 2005 Express Edition SP1. There is no error during installation and it seems to be working as I can see the SQL Server (MSSQLServer) service is running. As SQL server configulation manager., the protocal shared memory , named Pipes and TCP/IP are enabled.
But when I want to add connection using VWD 2005 by pointing to datasource (MS SQL Server database file and selecing file from .mdf file from SQL sample database file. Then test connection, I got a error that
"An error has occurred while establishing a conneciton to the server. when connecting to SQL server 2005, this failure may be casued the the fact that under the default settings SQL server does not allow remote connections. (provider: SQL Interfaces, error: 26- Error locating server/instance specified)
Can you please advise what the missing part of my configulation ?
Thanks
hi,
did you elect to enable User Instances at SQLExpress install time?
you can enable them at later time "configuring" the instance via the apposite
EXEC sp_configure
statement
regards
|||This is most likely caused by having the wrong Instance name configured in VWD. You wrote that your could see MSSQLSERVER, which the name of the Default Instance for SQL Server. Normally SQL Express installs to a Named Instance rather than the Default Instance. Did you specifically chose to install the Default Instance when you installed SQL Express?
If so, your problem is that VWD is configured to use a Named Instance of SQLEXPRESS by default. You will need to go into the Tools | Options dialog and look at the Data options. (You may need to show all options to see this.) Once there, you will see a text box where you can set the instance of SQL Express to be used, it will likely say "SQLEXPRESS" and you need to change it to the actual name of your instance.
Mike
|||Mike,
You are correct.
Big Thanks for advise.
Pitak
Cannot connect remotely to MSDE2000 database
Hi,
I have a win98 Pc connecting to a winxp pc - trying to connect to the
MSDE2000 database - the database is operating in mixed mode (allows SQL
logins) rather than windows integrated. The database is working ok on winxp
pc - i can use the SQL Web Data adminsitrator to verify that SQL Logins work
ok - also the ODBC Adminstrator can make connections to the database.
Now when i try using the ODBC Administrator to connect using the same
details it fails - SQL server does not exist or access denied.
Now i have disabled windows firewall to rule that out (although i had
enabled port 1433- sql server listening port).
Now how can i verify SQL server is listening on port 1433 for remote
connections?
How do i configre SQL server to listen for remote connections?
Any other ideas for resolving my connection problem?
Thanks a lot!
hi John,
John Blair wrote:
> Hi,
> I have a win98 Pc connecting to a winxp pc - trying to connect to the
> MSDE2000 database - the database is operating in mixed mode (allows
> SQL logins) rather than windows integrated. The database is working
> ok on winxp pc - i can use the SQL Web Data adminsitrator to verify
> that SQL Logins work ok - also the ODBC Adminstrator can make
> connections to the database.
> Now when i try using the ODBC Administrator to connect using the same
> details it fails - SQL server does not exist or access denied.
> Now i have disabled windows firewall to rule that out (although i had
> enabled port 1433- sql server listening port).
> Now how can i verify SQL server is listening on port 1433 for remote
> connections?
> How do i configre SQL server to listen for remote connections?
> Any other ideas for resolving my connection problem?
> Thanks a lot!
please verify, using Server Network Utility (svrnetcn.exe), that the MSDE
instance allows remote connections via the desired/required network
protocol...
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.10.0 - DbaMgr ver 0.56.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Thanks a lot - very immpressed - that did the trick - TCP/IP protocol was
disabled - i enabled it and it worked!
I've spent 2 days trying to get this working - eventually found out the
registry needed changing to allow mixed mode (SQL login)- found out my
firewall was blocking port 1433 - and finally your suggestion for enabling
the protocol - never even heard of that utility svrnetcn.exe - thanks very
much! John.
"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> wrote in message
news:37md0nF5eceloU1@.individual.net...
> hi John,
> John Blair wrote:
> please verify, using Server Network Utility (svrnetcn.exe), that the MSDE
> instance allows remote connections via the desired/required network
> protocol...
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.10.0 - DbaMgr ver 0.56.0
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>
|||Exposing SQL through a firewall by opening port 1433 is generally considered
to be a bad thing.
-Andrew
"John Blair" <john_blair@.hotmail.com> wrote in message
news:H2oRd.910$gv6.611@.newsfe3-gui.ntli.net...
> Thanks a lot - very immpressed - that did the trick - TCP/IP protocol was
> disabled - i enabled it and it worked!
> I've spent 2 days trying to get this working - eventually found out the
> registry needed changing to allow mixed mode (SQL login)- found out my
> firewall was blocking port 1433 - and finally your suggestion for enabling
> the protocol - never even heard of that utility svrnetcn.exe - thanks very
> much! John.
>
> "Andrea Montanari" <andrea.sqlDMO@.virgilio.it> wrote in message
> news:37md0nF5eceloU1@.individual.net...
>
|||I am only exposing this port on a local intranet - so i wasn't aware that
there are any security risks. Do you have a better way of letting VB6 apps
access a remote SQL Server database? Thanks.
"Andrew" <nemoby@.nospam.nospam> wrote in message
news:uVC2%23ofFFHA.4016@.TK2MSFTNGP09.phx.gbl...
> Exposing SQL through a firewall by opening port 1433 is generally
> considered to be a bad thing.
> -Andrew
> "John Blair" <john_blair@.hotmail.com> wrote in message
> news:H2oRd.910$gv6.611@.newsfe3-gui.ntli.net...
>
I have a win98 Pc connecting to a winxp pc - trying to connect to the
MSDE2000 database - the database is operating in mixed mode (allows SQL
logins) rather than windows integrated. The database is working ok on winxp
pc - i can use the SQL Web Data adminsitrator to verify that SQL Logins work
ok - also the ODBC Adminstrator can make connections to the database.
Now when i try using the ODBC Administrator to connect using the same
details it fails - SQL server does not exist or access denied.
Now i have disabled windows firewall to rule that out (although i had
enabled port 1433- sql server listening port).
Now how can i verify SQL server is listening on port 1433 for remote
connections?
How do i configre SQL server to listen for remote connections?
Any other ideas for resolving my connection problem?
Thanks a lot!
hi John,
John Blair wrote:
> Hi,
> I have a win98 Pc connecting to a winxp pc - trying to connect to the
> MSDE2000 database - the database is operating in mixed mode (allows
> SQL logins) rather than windows integrated. The database is working
> ok on winxp pc - i can use the SQL Web Data adminsitrator to verify
> that SQL Logins work ok - also the ODBC Adminstrator can make
> connections to the database.
> Now when i try using the ODBC Administrator to connect using the same
> details it fails - SQL server does not exist or access denied.
> Now i have disabled windows firewall to rule that out (although i had
> enabled port 1433- sql server listening port).
> Now how can i verify SQL server is listening on port 1433 for remote
> connections?
> How do i configre SQL server to listen for remote connections?
> Any other ideas for resolving my connection problem?
> Thanks a lot!
please verify, using Server Network Utility (svrnetcn.exe), that the MSDE
instance allows remote connections via the desired/required network
protocol...
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.10.0 - DbaMgr ver 0.56.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Thanks a lot - very immpressed - that did the trick - TCP/IP protocol was
disabled - i enabled it and it worked!
I've spent 2 days trying to get this working - eventually found out the
registry needed changing to allow mixed mode (SQL login)- found out my
firewall was blocking port 1433 - and finally your suggestion for enabling
the protocol - never even heard of that utility svrnetcn.exe - thanks very
much! John.
"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> wrote in message
news:37md0nF5eceloU1@.individual.net...
> hi John,
> John Blair wrote:
> please verify, using Server Network Utility (svrnetcn.exe), that the MSDE
> instance allows remote connections via the desired/required network
> protocol...
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.10.0 - DbaMgr ver 0.56.0
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>
|||Exposing SQL through a firewall by opening port 1433 is generally considered
to be a bad thing.
-Andrew
"John Blair" <john_blair@.hotmail.com> wrote in message
news:H2oRd.910$gv6.611@.newsfe3-gui.ntli.net...
> Thanks a lot - very immpressed - that did the trick - TCP/IP protocol was
> disabled - i enabled it and it worked!
> I've spent 2 days trying to get this working - eventually found out the
> registry needed changing to allow mixed mode (SQL login)- found out my
> firewall was blocking port 1433 - and finally your suggestion for enabling
> the protocol - never even heard of that utility svrnetcn.exe - thanks very
> much! John.
>
> "Andrea Montanari" <andrea.sqlDMO@.virgilio.it> wrote in message
> news:37md0nF5eceloU1@.individual.net...
>
|||I am only exposing this port on a local intranet - so i wasn't aware that
there are any security risks. Do you have a better way of letting VB6 apps
access a remote SQL Server database? Thanks.
"Andrew" <nemoby@.nospam.nospam> wrote in message
news:uVC2%23ofFFHA.4016@.TK2MSFTNGP09.phx.gbl...
> Exposing SQL through a firewall by opening port 1433 is generally
> considered to be a bad thing.
> -Andrew
> "John Blair" <john_blair@.hotmail.com> wrote in message
> news:H2oRd.910$gv6.611@.newsfe3-gui.ntli.net...
>
Subscribe to:
Posts (Atom)