IIS Website VERY slow when accessed via DNS name; fast when accessed via IP

I have a website that is running on IIS 6. The site is built in Visual Studio 2008 using the Crystal Reports plug-in.

When I access it via the DNS A-record, it runs at least 10 time slower than when I access it via the IP address.

When I resolve the A-record with nslookup or something, it resolves quickly, so it is not actually a DNS resolution problem.

I am completely stumped as to what could be causing this. Any ideas?

Thanks!
netmergenceAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

ChiefITCommented:
Slow on all computers or just one?
0
Colin_A_MoulderCommented:
Do you have more than one IP address? Do you have more than one interface? If so, what interface\IP is in DNS?
 
0
netmergenceAuthor Commented:
In response to the first comment, it is slow everywhere outside of the building. I do not have login access to any other internal machines, so I cannot test it from within their LAN.

The server technically has two IP addresses, because it has it's own private IP, then it has the public IP where 80 and 443 are just forwarded to it. However, the server itself only has the one, private IP assigned to its interface. There is just that one interface, and each IP address is only registerred in its corresponding DNS. (Internal DNS resolves the internal IP; external DNS shows the external IP.)

0
Determine the Perfect Price for Your IT Services

Do you wonder if your IT business is truly profitable or if you should raise your prices? Learn how to calculate your overhead burden with our free interactive tool and use it to determine the right price for your IT services. Download your free eBook now!

netmergenceAuthor Commented:
I figured it out...

It was the "Integrated Windows Authentication" that was causing problems outside the building. I don't fully understand why it would work, but just be very, very slow, but as soon as I disabled Integrated Authentication and instead enabled Basic Authentication, it started working at the normal speed.

How on earth authentication is tied to the DNS name vs. the IP address is beyond me. I'll award the poitns to anyone who can come up with a plausible explination!
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
ChiefITCommented:
Will you close the question and refund yourself points by accepting

07/10/09 02:13 PM, ID: 24828424

as your answer.

I am glad to see this is fixed for you. I am now reviewing IWA to see the ramifications of it.
0
ChiefITCommented:
I also wanted to tell you from what I read, by disabling IWA, you are going to NTLM and LM hash authentication. This is an outdated protocol. We are now on NTLMv5 (Kerberos). So, I can't figure out for the life of me, why enabling the older authentication protocols works best for you.

0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Networking

From novice to tech pro — start learning today.