Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

We have a web application which uses the command:


It has been working well for a few years, but suddenly, a few days ago, we saw that it began generating the following exception:

System.Net.WebException: The remote name could not be resolved

There have been no changes in the code, nor in the server configuration.

A similar question was asked on StackOverflow, but the solution there had to do with a proxy server, which our server isn't.

Strangely, the application does work in localhost, where our pc's use a proxy. But our production servers - that are in an outside network - stopped working...

share|improve this question
The problem is with the remote server I think... Is that an outside one? –  fretje Nov 16 '09 at 8:13
Have you verified you can ping the server from a command prompt to validate DNS settings? –  Wayne Nov 16 '09 at 8:25
nslookup your.server.name your.dns.server.address to check DNS server –  TiFFolk Nov 16 '09 at 8:50

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Browse other questions tagged or ask your own question.