Open UDP port 1434 to browse for named instances

q : A local ISP hosted our SQL Server, but I can't see or connect to a named instance running on that computer. I know that the SQL Server 2000 named instance does not use TCP/IP 1433 ports and that the TCP/IP port used by the SQL Server instance is open. Do you have any suggestions?

A: Many people know how to use the SQL Server Network Utility or the SQL Server error log to determine the listening port for an instance of SQL Server. But many people seem to forget or have no idea--udp 1434 ports must also be open to ensure that you are able to access and browse named instances correctly. I suggest that you study this request carefully. By searching for "1434" in the SQL Server online book , you will get three research-worthy search results. In my SQL Server practical tip column of SQL Server Magazine website July 2001, you can also find information about accessing named instances (InstantDoc ID 21127). I would like to explain briefly here. SQL Server establishes a listening service on UDP 1434 ports that allows clients to query a list of named instances and their network configuration information from the server. The listening service is always running on UDP 1434 ports and the user cannot change the running port. <