Accessing a url via IP address is very slow.

Are you NATing? Are you using the external address (the NATed one) or the internal address? I'd assume the DNS is definitely the external one...or I could be on the wrong path completely. Any insight here?

nating.

But funny thing is here is an example.

if you go to

hope you understand the issue.

Are you using any sort of a proxy server? You might use Wireshark or another packet sniffer to look and see if it is actually connecting to

Greetings,

This might be a case of crook name resolution for the server, in that the DNS entry is following the correct Server, but the IP address is not. Poorly written Web pages can also cause this.

Cheers................pk.

Wonder if it could have something to do with reverse look-up, which could be different based on whether or not you are using the internal or external IP when you go directly. When you go to the DNS name, you come from outside and the source is from your external NAT interface. However if you are using the local IP when going directly, that will not resolve via reverse-lookup if this is a linksys type situation and you don't have an internal DNS server. I have seen things like this on a few different occasions.

I used microsoft.com as an example this is happenning with anysite if I go using IP it loads very slow, go using name loads really fast.

I would go with what the previous post indicated, if using a proxy server or even some firewalls doing any sort of DNS reverse lookup could slow it down if not resolving back to a name and having to timeout.

When you say slow, is there a delay before the page even starts to load, or is the page contents just taking a while to display as the page loads ?