But I don't understand why it wouldn't work with dynamic ports and the way that it should be set up for named instances. Unless that's just intended behavior to not work with dynamic ports and a firewall
Well I have the incoming ports set up 1433 TCP and 1434 UDP, and sqlbrowser get's the connectiong (see by using sqlbrowser.exe -c) but the client fails to connect
@JoelSpolsky yea. I think in itself it a good idea because it gets us programmers thinking about things that don't have the deterministic answers and it gives us somewhere to ask questions that are harder for non-programmers (or technical minded people) to answer