Recently, the system which developed by us has been deployed to customer's production environment(using IE6/7/8 at client):
Windows 2003 Enterprise Edition SP2
ASP.NET 3.5 (with ajax functionality)
When we access the site entry point which is named Default.aspx from the WAN internet connection, it works just fine. However when we access the site from the LAN connection pages take a long time to render.
It shows us a blank page with loading information on the IE's status bar. Whilst it is loading I viewed the source code three times by right clicking on the page and saw the contents increased each time which means that the page is indeed loading.
We know that the connection speed in customer's LAN environment is slow. However, we have to try and resolve this.
So, could anybody give me some tips on how to improve this?
Update:
In reply to your comments.
To Michael:
Yes, we all think it should be a network problem, but can't find out where could we go.
To tsegay:
Yes, it just slow from local network which have LAN internet connection. But there is no problem in our lan intranet test/development environment.
If it is a LAN security problem, then you would need to isolate an HTTP traffic issue, so IT people can fix. Install Fiddler on the client and check which session(s) is slow. Is it Default.aspx or a resource (if any)? There may be a java script file or an objects (i.e. active-X) on the page that firewall/virus-scan do not like. You will see where the traffic got stuck or crawling.
Security scan can change HTML. Compare in Fiddler content length of Default.aspx accessed via LAN and WAN to make sure that it is not altered. Also, if the problem is with DNS, Fiddler will show high DNS time.
Related
The connection to the website was reset.
Error Code: INET_E_DOWNLOAD_FAILURE
I have a C# web application running on our internal IIS 10 Server and the site uses Windows Authentication. Our networking team setup everything needed to get to the site from the Internet. I get the above error when connecting from the Internet and have the site listed in Local Sites.
I have users with laptops that sometimes work in the office and on the road. So, we've added the url to Security - Local Sites so they aren't required to enter a login an password each time they go to the site. This works fine until they hit the road where they get the above error.
If I remove the site from Local sites or added it to trusted sites, it works. It works if they use Chrome, but not IE or Edge. It also works if the VPN in, but they don't want to do that.
The message is very vague and I've tried a variety of things based on research I've been doing, but no luck. One suggestion was to setup the Developers tools and capture the error, but this also proved to be of no value, unless I'm doing something wrong.
The message returns quickly, so it's not timing out. I've also checked Event Logs and not finding any related messages.
I've tested this using different Custom Security Levels - Automatic Login with Current User, etc.
Please let me know if you have other suggestions or if I can supply additional information.
VS 2017, C#, IIS 10, .Net 4.6
I have an ASP.Net Website (not a web app, fwiw) that builds and works just fine locally through IIS on my dev laptop.
However, when I publish it to our QA box and try to view while I'm remoting into that server, I get a message from IE saying "Internet Explorer cannot display the webpage". Firefox just spits back a quick "Connection Timed Out"
There is absolutely nothing in the event log nor the IIS log about this. I'm unsure where I can look for more info.
I'm fairly confident it is an ASP.Net issue. I can install a sample site from our vendor, Ektron, into IIS and it will run. If I overwrite the sample's web.config with my own, it continues to run. If I then blow away the entire sample site and copy over my site from my local, I'll get the message about how "Internet Explorer cannot display the webpage".
I've tried to keep the environments as close together as I can. Both boxes are running IIS 7.5 under an integrated app pool for .Net 4.0. I browse via localhost on dev and via an IP on the server.
I am not terribly familiar with the Website template, so I might be missing something obvious (I hope!). I'm hoping someone can provide some guidance into how I can get more info on what the heck is going on so I can resolve this issue.
UPDATE
I think I'm getting closer. By using Fiddler (thanks for the suggestion, Amy!) I notice that it redirects the request to SSL. SSL requires a different license from our vendor, so that might be it. I'm still trying to understand why that redirect is taking place, but at least I have something now to look at.
I'd look into the SSL settings in the web.config / IIS - settings for Mime Types and also into Ektron's MIME Types in the MimeType.config file. I found that some .aspx pages like (ekajaxtransform.aspx) weren't functioning correctly because of firewall/proxy issues/restrictions.
Hope it helps. :)
I have an application that displays PDF files via Crystal Reports in a new window to the user. This works perfectly on my development machine and when accessing the site directly on the production server (remote desktop running browser installed on server) but when i access the site from the out side over the internet i get the error. Other reports display fine and this report used to work until i recently made some changes and re-installed the site. All code is in try ... catch but not info is being written to my error files. Cant figure out why it would work locally on the server but not over the internet and only this one report.
Have tried the System.Web attributes maxRequestLength and executionTimeout.
The Server is:
Windows Web Server 2008
IIS 7
Framework 4
This turned out to be an issue with the crystal report file, i never found out exactly why but i narrowed it down to one of the fields causing the problem, remove the field and no problem. I think it may have been linked to the reports xml based data source but cannot prove it.
Probably a firewall setting. Please make sure your firewall explicitly allows incoming connections to the TCP port 80 (or 443 for https, or anything else if you are accessing the site via another port) and try again.
I hope you are going to understand what i want to accomplish...
I have local web server with web application on it and 10 hosts. Because of poor communication link with the server, I would like to know is it possible to store pictures and maybe some css scripts locally to host so that browser load it from local hard drive
This is no longer allowed due to security issues. This may be possible with a local web server though.
See: How to show local picture in web page?
I have published ASP.NET web site, using IIS7 on Win7. I can access this web site on my localhost, but it is inaccessable from other computers via internet. I have tried to disable firewall and anti-virus program, but with no success.
Does anyone know what may be causing this problem?
It works fine if I publish it on winXP.
Try checking out your router settings for port 80 forwarding;
Check out information about your internet provider as well;
There are providers that block port 80 outgoing traffic.
Try checking to see if the website is actually bound to 127.0.0.1. If it is, it would work for you but no one else.
Try to hit the website from a different computer on the internal network. If you can't hit it internally, then it is an issue with the local configuration on the webserver. If you can hit it internally, but can't hit it externally, then there is some kind of routing issue from the outside.
Its likely a routing issue from the outside, so think about these steps:
External DNS
Proper NAT/Firewall settings
Try using telnet to connect to the website and see if you get a response
Use tracert from the outside to see where the traffic is failing (if its failing)
Check the security settings on the deployed folder and check "Everyone" has read access. If you've not deployed under wwwroot they may not