>>>>>>If you want to see what scripts are loaded in the browser page in IE 8 and you open Developer Tools I don't see the Network tab.
>>>>>>How else can you see what scripts are being loaded?
>>>>>
>>>>>The very first hit on Google using the thread title is this: http://social.msdn.microsoft.com/Forums/ie/en-US/aa0e3d47-4ead-4666-b1ad-4ab16d49f3dd/network-tab-missing-in-ie8?forum=iewebdevelopment
>>>>
>>>>This browser resides on the customer server and they won't allow me to install anything without corporate IT approval.
>>>
>>>I don't know of any tool on the server itself that could give you that information.
>>>
>>>If you can't touch the server there are a couple of other possibilities:
>>>
>>>- run WireShark on a workstation and sniff traffic between the server and the router
>>>- ask the sysadmin to configure the router to log traffic between the server and the public Internet
>>>
>>>It's probably easier to convince the sysadmin to install an IE add-on, or an alternate browser like FireFox or Chrome which might let you see what you need.
>>
>>As I mentioned to Craig, in this case I connecting to the customer server via Remote Desktop and the client and the server is one and the same. So I don't thing there is an issue of network communication. It is either their browser (IE8) has some setting the "interferes" with my application (ASP.NET 4.0) or I am missing something in the application.
>>
>>Getting anything done by this corporate is very difficult. And the players are changing all the time. The corporate IT people was communicating with only about 6 months ago are all gone. I don't know if they were fired or left on their own accord. But I would not be surprised if it were latter; not a good environment to work.
>
>If I understand correctly this is your situation:
>
>- Customer has a server. This server runs IIS and your ASP.NET 4.0 app is installed on this IIS server
>- You connect to this server remotely via RDP
>- Within your RDP session, you start up IE8 and try to access your app. Your app does not work properly
>
>Some ideas:
>
>1. On servers, by default IE runs in "Enhanced Security Configuration". This breaks a ton of sites. If that's your situation you can Google [ie enhanced security configuration] for ways to turn that off
>
>2. Are there any workstations or other computers at the customer, also using IE8? If so you could ask to be allowed to RDP into one of them from your server RDP session (running a remote desktop from within a remote desktop, sounds tricky but actually works reasonably well). With that you could:
>
>- find out if it's something specific to running IE8 on the server vs. on a workstation
>- maybe they'll let you install Fiddler on IE8, or FireFox or Chrome on the workstation so you can see what's going on
>
>3. You could set up your own test environment, with a server or workstation running IE8 and see if you have the same issues. The problem with this is if it works for you, it won't help determine whatever it is at the customer site that's causing the problems

You are very much correct in understanding the situation.

And you are right that IE on the server runs with certain restrictions. In fact I wanted make some changes (or at least to see if JavaScript is enabled) but the IE -> Tools has the message "Some settings are management by system administrator." And the entry to settings is grayed. I will ask one of the ITs on Monday (that I have known for years) and hopefully he can check things for me in the IE of the server.

I also tried to download and install Chrome on the server but when I go the to Chrome Download page - in the IE 8 browser - and click on any button that should bring to the download/install, nothing happens. So I think something is disabled in this IE 8 on the server.

I simply don't have time to setup test environment in my office. I have IE 10 and everything works fine.

And I will ask one of the users on their network if he would allow me to test this application from his desktop (he is a client on the network).

So hopefully sometimes on Monday or Tuesday I will be able to verify if this is my problem or simply an issue with IE 8.

Thank you for your suggestions.