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.
>
>
Tuesday, February 14, 2012
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment