Answered by:
SQL Native: Connection refused by using IP

Question
-
Hi!!!
I got a problem, if i try to connect with SQL Native client by IP (exemple: 192.168.1.2\MYDATABASE) it doesn't work. But I use: HOME\MYDATABASE it works. But in the 2nd case i cannot connect to SQL Server from another computer.
Thanks fr your help.
fred
Tuesday, February 14, 2006 12:03 AM
Answers
-
You will need to configure to allow remote connection via the Surface Area ConfigTuesday, February 14, 2006 3:36 AM
All replies
-
>> But in the 2nd case i cannot connect to SQL Server from another computer.
Do you mean you can connect to SQL Server from another computer using 192.168.1.2\MYDATABASE ?Tuesday, February 14, 2006 3:21 AM -
It doesn't work from where SQL Server has been installed and from another computer, both by using an IP adress.Tuesday, February 14, 2006 3:25 AM
-
You will need to configure to allow remote connection via the Surface Area ConfigTuesday, February 14, 2006 3:36 AM
-
This tool is located under:
Start Menu -> Programs -> Microsoft SQL Server 2005 -> SQL Server Surface Area Configuration.
SQL Server Configuration Manager is located in the same spot. I have multiple network connections (ie. network cards) on my machine, and this interfered with my host name resolution in the past too. If you continue to experience problems after enabling remote access (in the SQL Server Surface Area Configuration tool), try using a different network protocol (eg. TCP/IP vs Named Pipes). One thing that I did to enable resolution in my case was to set up an alias for my machine with exactly the same name as my machine:
- Open SQL Server Configuration Manager
- Navigate: SQL Server Configuration Manager -> SQL Native Client Configuration -> Aliases.
- Right-click -> New Alias
- In "Alias Name" and "Server", set the name of your machine (eg. MYMACHINE)
- I used Named Pipes for this
Tuesday, February 14, 2006 5:34 AM -
It still doesn't work.
I made a netstat -n and i got:
TCP 192.168.1.4:1159 168.95.192.1:53 TIME_WAIT
TCP 192.168.1.4:1168 168.95.192.1:53 TIME_WAIT
TCP 192.168.1.4:1177 128.63.2.53:53 TIME_WAIT
TCP 192.168.1.4:1181 192.33.4.12:53 TIME_WAITPort 1433 is not indicated so why ?
Tuesday, February 14, 2006 3:34 PM -
I've found the solution, in fact SQL Browser was not running so know i can use IP Adress to connect to SQL Server 2005.
Thks
Tuesday, February 14, 2006 4:28 PM