Ok i have never had an issue like this before. basically we have a website we use for e-commerce etc. When users go to edit certain products (products with a big pricing database behind them) the page either takes more than 5 mins to load or simply times out. With products with smaller pricing databases it works fine.

my first thought is the pricing databases are simply too big, but when i tried logging on and editing at home (on a slower connection) it loaded up within 5 secs

any ideas what could be causing such silly load times/ time outs?

just a little more info if it helps, we're running exchange 2003 here in the office and all going through a router supplied by BT (reset the router, flushed dns etc) we also have websense web security

Just cropped up. i have seen it working fine up until a couple of weeks ago. It still works absolutly fine if i access it off site. i have a sneaky suspision its somthing to do with the set up here, but then again we dont seem to have a problem with any other sites. in all honesty not sure where to start looking for the problem.

the only thing that has changed in those couple of weeks is we have upgraded broadband connection and had a new router installed. started thinking it was a router problem but then again, as i said, it only seems to affect this site.

Considering that my input so far has consisted mostly of questions, I'm not sure how much help it has been.

That said, I am a non-believer of coincidence with these things. If the network was changed and a new router was installed, I would normally feel pretty safe in figuring that was where the problem resides. Especially if everything still works fine elsewhere.

However, the biggest problem with that scenario is that you said that only certain products are giving you grief. So it isn't a site problem, really, but certain products within the problem site. But only from your location. Aaauuuggghhh!

My best guess now is that these data intensive products are somehow being throttled for bandwidth either by the new router or by the ISP - neither of which seems likely.

going home now anyways...think i'll play with the router tomorrow and ...errrmm i don't know...might get someone to re-input one of the products that don't seem to work into it and see what happens....cheers for your help!

If the site is only slow from inside your business, and you don't have trouble with out sites, I suggest investigating how you connect to the ecommerce site.

It is possible that there is a connection from the site back to your network (on the back end), quite possibly for data updates or maintenance. The problems you are seeing could be related to the configuration (or misconfiguration) of any such configuration.

If you documented your router configurations, check the old router config for static routes, lan-to-lan, and lan-to-host VPN connections. Also, look at RPC or other remote connections that may have been allowed by IP address through the firewall.

Compare these to the new router configuration. Generally, when you change ISP services, the only configuration item to change is your public IP addresses (unless you moved to MPLS or some other service type).

Something that bit us when we added our sonicwall (since you mentioned a new router), we were not allowing the web checks through our external firewall, so the content filter needed to time out on certain sites before it would allow access.

That led to exactly what you are describing (slow access from inside the building, but nowhere else).

Check you new router and see if it is filtering at all (and if possible turn the filtering off as a test).

What are your access times like for other protocols to your server? (ftp, ssh etc)

When users go to edit certain products (products with a big pricing database behind them) the page either takes more than 5 mins to load or simply times out. With products with smaller pricing databases it works fine.

Keep in mind, guys, that Paul said that it was only on certain products that he was having a problem with, not the entire site. Which puts a wrinkle in the routing problem possibilities. I'm not saying that it isn't that but it seems that something additional is at play here.