Hm I see, many thanks for checking that. Could you please check some other things for me then (sorry to bombard you with questions!)..
-If you look at the most recent log file or two (Help>Open folder), are there any errors in them?
-Does it make any difference if you profile on an unused port instead of the original port?
-Are you able to profile any other IIS sites running on your machine?
-Does your site have any bindings on the localhost/127.0.0.1 that you could try profiling instead of the one on 220.127.116.11? If not, could you kindly try setting up the site on a different port on localhost (no hostname) to see if profiling that works?
(Also, just a note: if your site is .NET 4.0+, a quick workaround is to start the application normally and then use the 'Attach to .NET 4.0+ Process' profiling option instead)
Red Gate Software Ltd.