Sql 2005 Instance; Dynamic Ports And Firewall Issue

We have an internal sql 2000 server that acts as the database backend for our
Internet presence. I believe that the sql server can be accessed because of a
firewall "exception" (?) that allows the external web server to talk to the
sql server using a specific IP address and port (namely that of the sql server.)


Now we need to install a sql 2005 instance on the same box which needs to act
as an Internet backend. The sql browser service will resolve all client
requests to the default or named instance. But I read that the sql browser service
assigns a "dynamic" port to the Instance! If that is the case, it's unlikely that,
unless the firewall has all ports open for outgoing traffic, that the sql instance will be
able to communicate with the web server.



My conclusion:

Leave the default instance (sql 2000) port at its current value;
assign the named instance an unused port;
Make sure the sql browser is running on the box!
Tell the firewall guys to make an exception for the new port.

Does this seems reasonable to you?


TIA,

barkingdog