• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 385
  • Last Modified:

SQL problem unable to see port 1433

Dear Team,

I have installed windows server 2008 R2 and SQL Enterprize Server 2008 R2 on my server.

But there is some problem ...when i run the following command.

netstat -a -n , i am not able to see the SQL port 1433 as listening.

The connections are enabled on the firewall end.

What can be the possible reson how can i switch on the Port 1433 , is there something wrong in SQL installation.


Thanks & Regards

Pranav IT
0
Pranav_IT
Asked:
Pranav_IT
  • 3
  • 2
  • 2
  • +1
1 Solution
 
Kamaraj SubramanianApplication Support AnalystCommented:
you can assign a port number manually.

http://msdn.microsoft.com/en-us/library/ms177440.aspx
0
 
QlemoC++ DeveloperCommented:
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.
0
 
ienaxxxCommented:
The problem is you did not configured the network protocols in the SQL server configuration manager tool you can find under the program group in the start menu.

You should enable TCP/IP and Named Pipes since AFAIK those are not enabled by default.

You'll have to restart the SQL server service in order for you to see the port.
0
Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
Pranav_ITAuthor Commented:
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.
0
 
Pranav_ITAuthor Commented:
How can the SQL browser manage the Port negotiation, can any body help i dont want to uninstall the server.
0
 
QlemoC++ DeveloperCommented:
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.
0
 
ienaxxxCommented:
seen this a lot of times, just check on the configuration manager as i told.
0
 
Pranav_ITAuthor Commented:
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.
0

Featured Post

Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

  • 3
  • 2
  • 2
  • +1
Tackle projects and never again get stuck behind a technical roadblock.
Join Now