I believe that SQL browser listens on UDP port 1434 not TCP port 1434. That makes a difference.

I think the moral of the story is "don't let SQL decode what ports it listens too, always take control.."

CEWII