September 3, 2009 at 8:11 am
We have one application which uses SQL Server Express which sits alone on its server. I was trying to connect to the server using SSMS but got the error that the SQL Server Express server did not allow remote connections. I have been on to SQL Server Express server, checked that remote connections were enabled which they are (Surface Area Configuration) and checked that my login is a sysadmin on that server.
However I still get the same error (does not allow remote connections) when I attempt to connect using SQL Server 2005 client tools. As this is the only SQL Server Express application that we have I am a bit stumped. What am I doing wrong
Madame Artois
September 6, 2009 at 12:33 pm
what about firewall settings ?
September 6, 2009 at 5:48 pm
Also check that you are trying to connect using a protocol that the server is listening on (named pipes or TCP/IP).
Paul White
SQLPerformance.com
SQLkiwi blog
@SQL_Kiwi
September 8, 2009 at 8:25 am
Double click (as far as I remember) the protocol settings and check the interfaces SQL Server listens. Also check the port numbers.
Run "netstat -a -p tcp" to check the listening and established connections.
Check whether SQL Server opened the port.
If it did - check firewall setings.
--------------------
StarWind Software developer ( http://www.starwindsoftware.com )
September 8, 2009 at 8:26 am
Are you referencing it by the right InstanceName?
CEWII
September 8, 2009 at 8:34 am
Elliott W noticed the right thing: check whether there is a default instance or check the instance name.
--------------------
StarWind Software developer ( http://www.starwindsoftware.com )
September 24, 2009 at 8:27 am
Dear all
Sorry for not being in contact but I have been off on my hols. I have requested information from the company who set it up. Once I have this or I have cleared all my 'urgent' (!) emails I will be back. Thanks
Madame Artois
Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply