ASP.NET - Remote name could not be resolved

Collapse
This topic is closed.
X
X
 
  • Time
  • Show
Clear All
new posts
  • =?Utf-8?B?U2hpdmEgUmFtYW5p?=

    ASP.NET - Remote name could not be resolved

    Iam trying to read a RSS feed (through XmlTextReader) from my application.
    The url (ex: "http://www.wipro.com/RSSFeed.xml") is accessible through the
    browser but when the same when tried from the asp.net application I get
    "The remote name could not be resolved: 'www.wipro.com' "
    This happens the same for all the other URLs also.

    My browser LAN Settings has "Automatica lly detect settings" being set. My
    authentication on the app is set to Windows Authentication.
    Do I need to change/specify anything when trying to access outside url's in
    IIS
  • Peter Bromberg [C# MVP]

    #2
    Re: ASP.NET - Remote name could not be resolved

    It sounds like your LAN has a proxy. The brower is automatically detecting
    it. But, .NET isn't as smart - you'll need to set the Globalproxy settings
    to the correct settings first.
    Peter

    "Shiva Ramani" <ShivaRamani@di scussions.micro soft.comwrote in message
    news:8A4F154E-5B99-4EDF-95E0-983154615A26@mi crosoft.com...
    Iam trying to read a RSS feed (through XmlTextReader) from my application.
    The url (ex: "http://www.wipro.com/RSSFeed.xml") is accessible through the
    browser but when the same when tried from the asp.net application I get
    "The remote name could not be resolved: 'www.wipro.com' "
    This happens the same for all the other URLs also.
    >
    My browser LAN Settings has "Automatica lly detect settings" being set. My
    authentication on the app is set to Windows Authentication.
    Do I need to change/specify anything when trying to access outside url's
    in
    IIS

    Comment

    • Peter Bromberg [C# MVP]

      #3
      Re: ASP.NET - Remote name could not be resolved

      It sounds like your LAN has a proxy. The brower is automatically detecting
      it. But, .NET isn't as smart - you'll need to set the Globalproxy settings
      to the correct settings first.
      Peter

      "Shiva Ramani" <ShivaRamani@di scussions.micro soft.comwrote in message
      news:8A4F154E-5B99-4EDF-95E0-983154615A26@mi crosoft.com...
      Iam trying to read a RSS feed (through XmlTextReader) from my application.
      The url (ex: "http://www.wipro.com/RSSFeed.xml") is accessible through the
      browser but when the same when tried from the asp.net application I get
      "The remote name could not be resolved: 'www.wipro.com' "
      This happens the same for all the other URLs also.
      >
      My browser LAN Settings has "Automatica lly detect settings" being set. My
      authentication on the app is set to Windows Authentication.
      Do I need to change/specify anything when trying to access outside url's
      in
      IIS

      Comment

      • =?Utf-8?B?U2hpdmEgUmFtYW5p?=

        #4
        Re: ASP.NET - Remote name could not be resolved

        Can you pls tell me where this could be done ?


        "Peter Bromberg [C# MVP]" wrote:
        It sounds like your LAN has a proxy. The brower is automatically detecting
        it. But, .NET isn't as smart - you'll need to set the Globalproxy settings
        to the correct settings first.
        Peter
        >
        "Shiva Ramani" <ShivaRamani@di scussions.micro soft.comwrote in message
        news:8A4F154E-5B99-4EDF-95E0-983154615A26@mi crosoft.com...
        Iam trying to read a RSS feed (through XmlTextReader) from my application.
        The url (ex: "http://www.wipro.com/RSSFeed.xml") is accessible through the
        browser but when the same when tried from the asp.net application I get
        "The remote name could not be resolved: 'www.wipro.com' "
        This happens the same for all the other URLs also.

        My browser LAN Settings has "Automatica lly detect settings" being set. My
        authentication on the app is set to Windows Authentication.
        Do I need to change/specify anything when trying to access outside url's
        in
        IIS
        >

        Comment

        • Thomas Jenkins

          #5
          Proxy


          Comment

          Working...