We installed the agent on both nodes of a clustered SQL Server.  The node that was active when the install was done is working fine, however the passive node will not start SQL Browser because of the following error "The SQLBrowser service port is unavailable for listening, or invalid."

We have confirmed that UDP Port 1434 is not in use.  We found this in MSDN where the agent had caused a issue before

http://blogs.msdn.com/b/sqlserverfaq/archive/2010/08/31/prb-sql-server-browser-service-does-not-start-due-to-winsock-monitoring-software.aspx

 

This did cause a brief production outage while we had to fail back.  How do we get this to work on a SQL Server so it does not block SQL Browser?