Problem with client's cache in Windows 2000
Help. I've built a website for a university department and they seem to be the only people in the world who can't see the site. I can check with the campus webmaster to check on their firewall, but I'm wondering if the fact that they're using Windows 2000 could have anything to do with the problem. I was there yesterday and got the pages to show up after I rebooted the computer and cleared out the temporary internet files and memory caches. But this morning we're getting 404 pages again.
None of the pages are on a secure server and only a portion of them are dynamic.
Brian Farkas posted this at 06:12 — 24th October 2001.
They have: 1,015 posts
Joined: Apr 1999
You're saying that you are able to view these pages on almost every computer _except_ this one, correct? If you got it to display correctly last night, it seems like it should have came up fine today as well. Did you change anything since last night that might have caused the error?
The best thing to do would be to clear out the temporary internet files, as well as the history in Internet Explorer... Theoretically, that should fix the problem. I haven't heard of any issues with caching on Windows 2000, but you might try installing another browser and seeing if it is viewable through that.
Good luck,
Brian
altyfc posted this at 09:45 — 24th October 2001.
They have: 18 posts
Joined: Oct 2001
We have cache problems all the time when we do amendments for clients' websites.
There are a couple of useful shortcuts that are fairly helpful in trying to re-load a page and clear the cache at the same time.
In IE - click on Ctrl F5
In Netscape - click on Shift and Reload
I'm not sure this will overcome this particular problem, but it's worth a try and hopefully it'll help others that have this same persistent problem.
Paul
Business Forum - Sport Forum - Travel Forum
Participation in our forums is rewarded with free ads!
twinspin posted this at 14:22 — 24th October 2001.
They have: 2 posts
Joined: Oct 2001
The problem isn't with the cache - it's definitely their authoritative DNS on their end. The weird thing was how it worked for me on their computer on Monday.
But I'm working with the campus webmaster to get the problem fixed.
Thanks.
Want to join the discussion? Create an account or log in if you already have one. Joining is fast, free and painless! We’ll even whisk you back here when you’ve finished.