Thanks for your reply.
I also emailed the host to ask if they could change the Firewall rule to allow the server to see himself and this is their reply (by the way the site is currently using just an IP address as the domain because it's in test mode - when it's live it will use an actual domain name):
"I'm guessing that this isn't always going to access via an IP address, which is what the problem is at the moment. If you were to try the URL:
http://_____________/FckEditor/filemanager/browser/default/connectors/asp/ResizeAspNet.aspx?TestAspNet=yes
And replace the blank line with a domain name, then it should work fine, as we use DNS doctoring on the firewall to prevent the sort of loopback issue we're running into with the IP addresses.
So, if we setup the domain name in IIS as a host header, and then setup a mapping in the HOSTS file of the server, this should alleviate the issue altogether."
So I'll wait and see what happens when we change the nameservers and start using the real domain name.
Thanks for your help.
|
|
|