The entire site fails to load? Or just specific areas?
Everything you have on the client suggests it should work perfectly. DNS resolves and you can open the TCP connection, not really much else to it.
That leaves something acting as a Proxy for the connection (to explain the difference in behaviour) when using the Browser instead of the command line.
Does this occur in all web browsers? You might consider logging the network traffic to see which requests are going where, specifically those that are failing. If the Firewall can't do that a packet sniffer on a client will, WireShark is probably the best bet there (
http://www.wireshark.org)
.
Chris