SQL Browser is not listening on UDP 1434

We have a 2 node SQL 2005 cluster with 2 named instances running. We have a problem that the dynamic discovery of the instance TCP port is not working correctly. If we specify the port on the remote systems the connection to the database is working correctly.

I have used TCPview and netstat and found that the SQL browser service is not listening on UDP port 1434 as it should be. Everything else on the server seems to be running correctly.

The SQL browser service is started and produces no errors when it starts.

Any ideas as to how I can resolve this
LVL 1
matthewsj11Asked:
Who is Participating?
 
matthewsj11Author Commented:
I don't think that you can configure the SQL browser service to use a different port as this is the one that is pre set for other services to connect to.

I think I have found the solution. In SQL 2005 configuration manager in the advanced properties of the SQL browser there is an option to set the service to active. Setting this and restarting the service seems to have fixed the problem.

No idea how it changed from active to inactive in the first place.
0
 
momi_sabagCommented:
perhaps it is configured to listen on a different port
you can check that in the sql server configuration surface
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.