Solved

IIS 6.0/DNS/Network Latency Issue

Posted on 2011-09-06
3
290 Views
Last Modified: 2013-01-15
I feel like I'm taking crazy pills.

Over the weekend, many of our javascript-intensive web applications ceased working. Upon further investigation, we realized that many Ajax calls were timing out with the default timeout period of 250ms. Normally, these URL requests would take about 50ms.

Upon even further investigation, we've identified the root issue:
If you navigate to any of our servers using a fully qualified dns address (even one specified in a hosts file), there is a 1 second delay before any HTTP GET request for a text-based document finishes loading. This means our home page, with several js and css files, takes over 7 seconds to load, whereas it should take about 500ms. This only occurs if you navigate to it by its fully qualified dns address. (Ex. http://web1.ourcompany.net/ or http://web2.ourcompany.net/) This also occurs if I create an arbitrary entry in my hosts file, such as "testintranet.com", pointing to one of my servers (Ex. 10.300.400.55).

If we navigate to any of the servers on our network by its short name or by IP address, the issue doesn't appear. (Ex. http://web1/ or http://10.300.400.55/).

So to summarize:
-It's not browser related - IE6,IE8,Chrome, and Firefox are all affected.
-I don't think it's a network problem (we're running a Cisco shop) because IIS correctly responds without delay when connecting by IP or short name.
-I don't think it's a DNS problem because our DNS server quickly resolves *.ourcompany.net addresses, and I bypassed DNS altogether by using a hosts file.
-I don't think it's an IIS problem because 3 separate servers with different purposes, none of which have had any configuration changes in months, all are affected.
-*It's not entirely workstation-specific as almost every computer we've encountered has been affected.

*= I found two PCs so far unaffected - both of which were connected either to our Core or to a gigabit switch. How could it be a physical network problem if only certain HTTP requests with fully qualified host headers are the ones being affected, and not HTTP requests with shorter host headers?

Please, someone help. I don't know how much longer I can take this insanity.
0
Comment
Question by:tenroc2o0o
  • 2
3 Comments
 
LVL 40

Expert Comment

by:noci
ID: 36494920
Proxy settings? these might [conditionaly through sripting] influence connectivity details.
0
 
LVL 1

Accepted Solution

by:
tenroc2o0o earned 0 total points
ID: 38765767
This turned out to actually be a DNS issue.
0
 
LVL 1

Author Closing Comment

by:tenroc2o0o
ID: 38777613
No other users submitted a probably resolution.
0

Featured Post

Live: Real-Time Solutions, Start Here

Receive instant 1:1 support from technology experts, using our real-time conversation and whiteboard interface. Your first 5 minutes are always free.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Security is one of the biggest concerns when moving and migrating your data from your on-premise location to the Public Cloud.  Where is your data? Who can access it? Will it be safe from accidental deletion?  All of these questions and more are imp…
A phishing scam that claims a recipient’s credit card details have been “suspended” is the latest trend in spoof emails.
After creating this article (http://www.experts-exchange.com/articles/23699/Setup-Mikrotik-routers-with-OSPF.html), I decided to make a video (no audio) to show you how to configure the routers and run some trace routes and pings between the 7 sites…
After creating this article (http://www.experts-exchange.com/articles/23699/Setup-Mikrotik-routers-with-OSPF.html), I decided to make a video (no audio) to show you how to configure the routers and run some trace routes and pings between the 7 sites…

776 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question