I keep getting the following error on the DotnetNuke NewsFeed module (RSS)

‘You Should Verify The Source Address Is Valid And That Your Hosting Provider Has Configured Their Proxy Server Settings Correctly’

I’ve read the solution in this and other forums but still I cannot access a RSS feed on a remote server.

I get the same result on a WindowsXP and Windows 2003 Server.

This is what I’ve done

1. I copied a valid XML file to my local websever/PC, to rule out the issue if the Proxy Server was causing the issues.
2. For the News Feed Source I’ve entered ‘http://localhost/data.xml’ or ‘http://127.0.0.1/data.xml’ and it works fine.
3. But if I enter my pc/server name (http://PCName/data.xml or http://MyNetworkIPAddress/data.xml)I get the error ‘You Should Verify The Source Address Is Valid And That Your Hosting Provider Has Configured Their Proxy Server Settings Correctly’ I can ping the network name and ip address. so not sure why NewsFeed can't access the file?
   
   I’ve been trying numerous things, but to no avail!

The above works, only when the web.config in changed to ‘High’ ‘<trust level="High" originUrl="http://localhost/.*"/>’ as suggested in a previous post. When it’s set to Medium (the DNN install default) both the localhost and PCName do not work!

Once it get it working on a local networked server, i'll try an internet server 

Any help would be much appreciated.

Thanks for your assistance

Hi,

thansk,  I added my PC to the host file but no success!

I can access the local server XML files (when the web.config is set to 'High' but on on 'Medium), but i cant access any XML url on the network (same subnet). I've used the IP and machine name without success. All pc's can be succesfully pinged.

I'm using DNN 4.03.

mmmmm... don't know where to go from here...

simon

nope, never did figure it out.

We use ISA server which was causing the problem. I setup a rule on the firewall to NOT challange the IP address of the DNN server for user crudentials! And it now works. Not the way I wanted it to work with authentication... but got me passed the initial problem. I'll be doing network traces next month to try and workout why the authentication was not working.