What my colleague Rumen shared is merely experience and information from another person that cannot be considered a solution, but an idea. The rest of the discussion, however, contains useful hints - namely - examining the network traffic and working with the IT department to track potential networking issues.
I would also suggest that you post one thread per issue as it will make it more concise.
Here are a few other ideas I can suggest:
- try using the CDN provider
- if you are on an intranet without access to the internet you can consider a custom CDN provider
- clear the browser cache on the problematic machine
- monitor the network traffic on the problematic machine and browser (either through its own dev toolbar, or through fiddler) to find more information:
= if only one browser on the machine shows the problem - try resetting its settings, disabling addons/plugins, reinstalling/upgrading it to see if this helps. If the issue is isolated to a single browser then most likely that browser is corrupt, not the page
= if there are broken requests - speak with your IT department for help on troubleshooting any limitations, rules, firewalls or other settings that may be in place
- if you are using custom tools you need to make sure that their icons are properly referenced and their paths are correct on this site, especially if the problematic page is a default document this may change the paths that are used on it. A possible solution would be to avoid using a default document.
If you want to get updates on new releases, tips and tricks and sneak peeks at our product labs directly from the developers working on the RadControls for ASP.NET AJAX, subscribe to the blog feed