[RESOLVED] Connecting to SQL express 2008 R2 over local network (Win 7)

Brawler

Brawler

Honorary Master
Joined
May 23, 2006
Messages
13,185
Reaction score
4,410
Hi.

I am working with an application that needs to connect to either a 2005/2008R2 express server via a local network.

In Windows XP / SQL 2005 I can set up the host computer and connect no problems, same thing via the network computers, I just enter the IP address and it finds the server and connects.

In Windows 7 / SQL 2008 R2 its a different story.. I have set up the host computer and the application is running correctly but when trying to connect via the network it freezes. I have enabled TCP/IP in SQL configuration manager and disabled Windows Firewall (for now, testing) but it still won't connect.
Any ideas?

Thanks.
 
Last edited by a moderator:
Disable IPv6 on both the server and client.

Make sure IPv4 is enabled, and that you can ping both server and client from each other.
 
Thanks man.

Disabled IPv6 - no difference..

Both using IPv4 simple static IP's for now 192.168.0.2/3, both can ping and even share files.
 
Not exactly sure how telnet works but from what I gather:

telnet 192.168.0.2 1433

Connecting to 192.168.0.2... could not open connection to the host, on port 1433: connection failed.
 
ok, well at least you used telnet correctly :whistle:

Try the same command on the local server ie: telnet 127.0.0.1 1433

If it connects, its not a sql problem, rather a firewall/network problem. If not, re-check your settings under sql server configuration manager.
 
Windows Firewall is off on both pc. Public and private. If I look in advanced I see a domain firewall aswell but no way to turn it off?
 
Domain firewall is only for domain networks.

What antivirus you using? Some do have firewalls as well - check these out & turn off. (In my experience, Symantec endpoint Protection do have its own firewall - which replaces Windows firewall, but if you don't add an exeption for SQL server, it will block SQL server).
 
on the server:

Connecting to 127.0.0.1... could not open connection to the host, on port 1433: connection failed.
 
Brawler said:
on the server:

Connecting to 127.0.0.1... could not open connection to the host, on port 1433: connection failed.
Click to expand...

Are you quite sure the server is using port 1433? And that the server service is started?

Check the server service status, and the server configuration.
 
Go into SQL server configuration manager and have a look at the ip addresses associated with tcp/ip I have had issues in the past where I installed SQL server while connected to a different subnet and when moving onto my production subnet the server maintained that it was on the development subnet and wouldn't connect.
 
Server service definitely started as I am running the database. Not sure on the port, I didn't change anything. Let me do some digging again.
 
Oh one other thing I didn't mention. I am doing this test in 2 networked virtual machines (vbox), not that it should make a difference.
 
Check in the configuration manager, if you right-click on TCP/IP (there where you enabled it), the port is listed in the properties

But default is 1433.

Also restart the service if you make any changes
 
Brawler said:
Oh one other thing I didn't mention. I am doing this test in 2 networked virtual machines (vbox), not that it should make a difference.
Click to expand...

You did run the last telnet command (to 127.0.0.1) in the correct virtual machine right? :whistle:
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X