If you have installed a named instance, the port is usually different from 1433, and defined dynamically, as the article the above link points to mentions. In that case you either need to fix the port, and provide it with each connection if different from 1433, or let SQL Browser manage the port negotiation. SQL Browser uses 1434/udp for that, and is asked for ports of a specific instance.
We get it - no one likes a content blocker. Take one extra minute and find out why we block content.
Not exactly the question you had in mind?
Sign up for an EE membership and get your own personalized solution. With an EE membership, you can ask unlimited troubleshooting, research, or opinion questions.
Okay I will recheck, can I remove the Enterpize 2008 R2 edition and put the Standard edition for SQL 2008 will it soilve the problem.
Your help has saved me hundreds of hours of internet surfing.
fblack61
Pranav_IT
ASKER
How can the SQL browser manage the Port negotiation, can any body help i dont want to uninstall the server.
Qlemo
Changing from Enterprise to Standard will not change anything in regard of protocols and ports.
Start your SQL Server Configuration Manager, go into SQL Server Network Configuration, Protocol for ..., and check if TCP is enabled. Then look into the TCP properties of that entry, tab IP Addresses. You should have either Dynamic TCP Ports set with the port number, or TCP Port. The latter is a static setting.
SQL Browser will work as long as you make sure the service named the same is running.
ienaxxx
seen this a lot of times, just check on the configuration manager as i told.
Unlimited question asking, solutions, articles and more.
Pranav_IT
ASKER
Hey guys just reinstalling SQL fixed the issue, the problem was we had installed the sql on some other network setup than what was actually needed, wher it was blocked.
In our new network we removed the old sql and put the new sql with new network settings and finally the issyue was resolved.
http://msdn.microsoft.com/en-us/library/ms177440.aspx