Link to home
Start Free TrialLog in
Avatar of Pranav_IT
Pranav_ITFlag for India

asked on

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
Avatar of Kamaraj Subramanian
Kamaraj Subramanian
Flag of Singapore image

you can assign a port number manually.

http://msdn.microsoft.com/en-us/library/ms177440.aspx
Avatar of Qlemo
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.
ASKER CERTIFIED SOLUTION
Avatar of ienaxxx
ienaxxx
Flag of Italy image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of Pranav_IT

ASKER

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