Hi all,

I'm a third-party developer working for a client running DotNetNuke as their intranet.

As part of our delivered solution, we produced a simple script that generated an RSS feed of relevant information.

The script runs within the company's internal network, too.


The problem is, the RSS feed module reports an error 502 (Bad Gateway) when we add the feed to DNN.

The reader works great with external feeds (including the actual feed I want it to use), but fails for the actual (internal) feed I'm trying to access, both accessed by IP address and by DNS name.


I realise this certainly is a server issue, but I'm keen to get it sorted out for the clients; do we have to do anything special with IIS to make sure requests for RSS feeds from other computers on the same network get through, as opposed to throwing back 502 errors?

There is definitely a proxy in place on the connection at some level (since the RSS feed reader can access sites external to the network, yet users cannot); it shouldn't be applying for connections to internal devices but I've got someone from their IT division checking that for me.

IE can load the RSS feed fine anywhere within the network.

Hello Chris,

I have the same issue. Basically my website was running fine. But I dont know why all of sudden section on website now compains as server "WebException "The remote name could not be resolved". What could be the reason? and as you were talking about "proxy" can you explain a little more what is proxy and why do we need to take care for this?

 

Thanks!!

Sandeep Sachan

---

Sandeep Sachan

Software Development