odd problem with html transmission
-
Ok, this one is really stange. I am hoping that one of you have run across this. I have a relatively simple asp.net app. When the main page is requested, it takes normally like 2 seconds for it to be sent to the client and rendered in IE. I have a couple of workstations however where it is taking in excess of a minute for the html to be sent to the browsers. I have ran sql profiler on the database so I can say for sure that the queries are not the cause of the issue. I have connected to different points on my network and experienced the problems still only on the few workstations. I ran a packet sniffer on the web server and the tcp packets transmitted were equivalent between a 'good' and a 'problematic' workstation. The only difference was the total time it took for all the packets to be sent and ACKd by the workstations. I have other asp.net apps running on the same server and the workstations don't have a problem with them so it seems to be application-workstation specific. I am totally at a loss. Any of you ever see anything like this?
-
Ok, this one is really stange. I am hoping that one of you have run across this. I have a relatively simple asp.net app. When the main page is requested, it takes normally like 2 seconds for it to be sent to the client and rendered in IE. I have a couple of workstations however where it is taking in excess of a minute for the html to be sent to the browsers. I have ran sql profiler on the database so I can say for sure that the queries are not the cause of the issue. I have connected to different points on my network and experienced the problems still only on the few workstations. I ran a packet sniffer on the web server and the tcp packets transmitted were equivalent between a 'good' and a 'problematic' workstation. The only difference was the total time it took for all the packets to be sent and ACKd by the workstations. I have other asp.net apps running on the same server and the workstations don't have a problem with them so it seems to be application-workstation specific. I am totally at a loss. Any of you ever see anything like this?
Hi Tim. Are there any other differences on those couple of workstations? Different OS? Different patches? Different browsers? Different browser versions?
-
Ok, this one is really stange. I am hoping that one of you have run across this. I have a relatively simple asp.net app. When the main page is requested, it takes normally like 2 seconds for it to be sent to the client and rendered in IE. I have a couple of workstations however where it is taking in excess of a minute for the html to be sent to the browsers. I have ran sql profiler on the database so I can say for sure that the queries are not the cause of the issue. I have connected to different points on my network and experienced the problems still only on the few workstations. I ran a packet sniffer on the web server and the tcp packets transmitted were equivalent between a 'good' and a 'problematic' workstation. The only difference was the total time it took for all the packets to be sent and ACKd by the workstations. I have other asp.net apps running on the same server and the workstations don't have a problem with them so it seems to be application-workstation specific. I am totally at a loss. Any of you ever see anything like this?
Are you sure it is an http problem? Usually when I see delays like this, there is a dns configuration problem on the client. If the client is trying to use the wrong dns server, or routing configuration problems prevent the client from reaching it's primary dns server. This is especially true if WINS is also configured on the network/and/or client.
-
Hi Tim. Are there any other differences on those couple of workstations? Different OS? Different patches? Different browsers? Different browser versions?
No, the two workstations appear to be nearly identical. Both XP Pro (SP1) and IE 6. All the available hotfixes/patches have been installed via windows update on both.
-
Are you sure it is an http problem? Usually when I see delays like this, there is a dns configuration problem on the client. If the client is trying to use the wrong dns server, or routing configuration problems prevent the client from reaching it's primary dns server. This is especially true if WINS is also configured on the network/and/or client.
Hmm.. Let me double check that tomorrow. I'll look at the primary DNS servers on both. Both workstation 'lease' their IP from a DHCP server so it's all dynamic. Do you know if it's possible that the DHCP server could be sending the wrong primary DNS ip to some computers?
-
Hmm.. Let me double check that tomorrow. I'll look at the primary DNS servers on both. Both workstation 'lease' their IP from a DHCP server so it's all dynamic. Do you know if it's possible that the DHCP server could be sending the wrong primary DNS ip to some computers?
If both machines are using the same DHCP server, it is probably correct. It has been 1.5 years since I last did any network support, and I don't remember the specifics. We had 2 networks connected by fiber and gatewayed by switches. Each network had a DNS server. When a client machine was configured improperly, it would try to resolve the address using WINS. For some reason, it would try until a timeout, then eventually it would use the DNS server and resolve the address. When I would remove WINS from the config, all would work normally. Unfortunately, I don't remember how to do that, since my machine (xp pro on a home network) doesn't look the same as the machines I remember from work (mostly win2k with some win me, xp pro, and win 98). Try packet sniffing to see if your client machine is hitting the server right away (and the delay is in the server), or if the delay is caused by name resolution. A third option is that something else is happening and the delay is happening before name resolution. Sorry my post is so vague, but it has been awhile. Basically, I would reconfigure networking on the client from scratch, and the problem would go away.
-
If both machines are using the same DHCP server, it is probably correct. It has been 1.5 years since I last did any network support, and I don't remember the specifics. We had 2 networks connected by fiber and gatewayed by switches. Each network had a DNS server. When a client machine was configured improperly, it would try to resolve the address using WINS. For some reason, it would try until a timeout, then eventually it would use the DNS server and resolve the address. When I would remove WINS from the config, all would work normally. Unfortunately, I don't remember how to do that, since my machine (xp pro on a home network) doesn't look the same as the machines I remember from work (mostly win2k with some win me, xp pro, and win 98). Try packet sniffing to see if your client machine is hitting the server right away (and the delay is in the server), or if the delay is caused by name resolution. A third option is that something else is happening and the delay is happening before name resolution. Sorry my post is so vague, but it has been awhile. Basically, I would reconfigure networking on the client from scratch, and the problem would go away.
Thanks a lot, I'll look at it more from this angle.