Solved

Unable to connect to SQLExpress 08 R2 on Port 1433

Posted on 2013-06-27
6
288 Views
Last Modified: 2013-07-08
Hi,
As per the title, I've installed the s/w on a Windows 08 Server (firewall on same disabled) but can't connect to it.
I'm not very familiar with SQLExpress so would appreciate some advice on how to troubleshoot.  
Thanks
0
Comment
Question by:t38
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
6 Comments
 
LVL 29

Accepted Solution

by:
Paul Jackson earned 500 total points
ID: 39281947
0
 
LVL 8

Expert Comment

by:didnthaveaname
ID: 39281955
Also, make sure you're specifying the SQLEXPRESS instance (which is the default instance name, unless you changed it during the install), so it would be servername\SQLEXPRESS (which, will not be on the 1433 port).  If you open SQL Server Configuration Manager (which I think should still install in express), and go to SQL Server Network Configuration > Protocols for instanceName > Right click TCP/IP > go to properties > IP Addresses tab > and look for the TCP port in there.  Named instances default to dynamic ports, also, so you may want to use the instanceName or change the port to a static value here as well.  If it's not that, I would try to connect locally on the server and see if you can successfully do that

Edited: to add some additional information...
0
 
LVL 83

Expert Comment

by:Dave Baldwin
ID: 39282141
To connect to an 'instance name', you need to have the 'sqlbrowser.exe' service running on port 1434.  If you have SQLEXPRESS configuration setup for remote access with TCP/IP, you also need the port defined in the setup to connect directly with an IP address.  I have both things set up on my installations so I can connect by name or IP address.
0
Ransomware-A Revenue Bonanza for Service Providers

Ransomware – malware that gets on your customers’ computers, encrypts their data, and extorts a hefty ransom for the decryption keys – is a surging new threat.  The purpose of this eBook is to educate the reader about ransomware attacks.

 

Author Comment

by:t38
ID: 39283727
Thanks for your input, will check each of the above asap and report back..
0
 
LVL 83

Expert Comment

by:Dave Baldwin
ID: 39283743
Also on other machines, you may need to have the SQL Native Client installed and TCP/IP enabled in it too.  SQL Native Client is installed with the server on that machine.
0
 

Author Closing Comment

by:t38
ID: 39307744
Thanks, in this instance the procedure outlined in the link resolved my problem.
0

Featured Post

Best Practices: Disaster Recovery Testing

Besides backup, any IT division should have a disaster recovery plan. You will find a few tips below relating to the development of such a plan and to what issues one should pay special attention in the course of backup planning.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

After restoring a Microsoft SQL Server database (.bak) from backup or attaching .mdf file, you may run into "Error '15023' User or role already exists in the current database" when you use the "User Mapping" SQL Management Studio functionality to al…
In this article I will describe the Backup & Restore method as one possible migration process and I will add the extra tasks needed for an upgrade when and where is applied so it will cover all.

734 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question