SQL Server 2008: Can’t remotely connect via management studio yet can telnet in OK. All settings appear OK
I am in the process of trying to configure SQL Server 2008 to accept remote connections. I have been through all the documentation I can find and yet when I attempt to connect through management studio I get an error stating that the server could not be found.
Interestingly I can connect through telnet to the remote server via the port that sql server is listening on. In the SQL Server logs I can see the connection attempt. So SQL Server is up and running and listening on the correct port – no firewall blocking it.
It would appear that by default SQL Server is listening on port 50314 but management studio attempts to connect on port 1433. Weird.
Server Management Studio = no dice.
Anyone got any ideas? Server is set to allow remote connections – TCP IP is enabled, firewall is off.
If SQL is not listening on port 1433 then you either have to either
Specify the port in your SSMS connection (your servername and port number separated by a comma)
“Server Name: mysqlserver,50314″
- Set up an alias on your SQL Server pointing to the port and make sure the SQL Server Browser service is running on the server.
- No Reporting Server connect option in SQL Server Management Studio 2008 Express
- What ports does Management Studio use to connect to SQL Server (2005)
- Sql Server management studio 2005 cant connect to localhost using windows authentication
- SQL Server Express 2008 R2 with old Management Studio?
- SQL Server Management Studio 2008 Install
Leave a comment
- What is the easiest way to upgrade my existing Perl 5.14 to Perl 5.16 on FreeBSD 9 using the ports system?
- Know if mysql has done its job
- Redirect https .com to https .co.uk without a valid SSL cert on .com without DNS change
- Why is it a bad idea to use customer email as from address
- 100% packets dropped on first RX queue on 3/5 raid6 iSCSI NAS devices using intel igb (resolved)