Announcement

Collapse
No announcement yet.

Windoze unable to resolve dns names

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Windoze unable to resolve dns names

    I've seen a few computers do this. I've solved in the past but I cannot remember how I did it.
    Basically you can ping ip address's but not the host name so IE won't work etc. Any ideas.
    Chief Lemon Buyer no more Linux sucks but not as much
    Weather nut and sad git.

    My Weather Page

  • #2
    Hmmm......
    I have also seen thgis wierd behauvier....

    Only thing that cured it was a reinstall.....
    If there's artificial intelligence, there's bound to be some artificial stupidity.

    Jeremy Clarkson "806 brake horsepower..and that on that limp wrist faerie liquid the Americans call petrol, if you run it on the more explosive jungle juice we have in Europe you'd be getting 850 brake horsepower..."

    Comment


    • #3
      Watch out for proggies that mess with DNS. I have seen the new.net program which is installed with kazaa go screwy and cause this behaviour. Check if it is in your add/remove programs list and uninstall it. I have run into this behavior many times and it can sometimes be a battle to resolve.
      Alcohol and Drugs make life tolerable.

      Comment


      • #4
        check your c:\windows\system32\drivers\etc\hosts

        it should contain just one line

        127.0.0.1 localhost
        P4 Northwood 1.8GHz@2.7GHz 1.65V Albatron PX845PEV Pro
        Running two Dell 2005FPW 20" Widescreen LCD
        And of course, Matrox Parhelia | My Matrox histroy: Mill-I, Mill-II, Mystique, G400, Parhelia

        Comment


        • #5
          Yeh I was wondering about a corrupt host file.
          Couldn't see any strange programs floating around. Last time someone had zonealarm installed. The uninstaller removed it from uninstall memu but left running in the background. Deleting the directory solved the problem. However nothing like zonealarm was installe deither.
          Chief Lemon Buyer no more Linux sucks but not as much
          Weather nut and sad git.

          My Weather Page

          Comment


          • #6
            I have used LSPFix (linked on http://www.geocities.com/Pentagon/Qu...newdotnet.html) before to fix a simillar problem.

            Edit: better link: http://www.cexx.org/lspfix.htm
            Good Luck.

            T.
            FT.

            Comment


            • #7
              Thanks I'll hve to wait for someone else walks in with this problem.
              They will sooner or later.
              Chief Lemon Buyer no more Linux sucks but not as much
              Weather nut and sad git.

              My Weather Page

              Comment


              • #8
                You using NTL cable?
                If so, that means CableModem MAC address is not properly registered (or the NIC MAC address).


                You might want to have a look.

                And if you are using NTL, try pinging 194.168.4.100 and 194.168.8.100 they are the DNS servers, see if they response.
                Don't use DHCP, config DNS servers as static setting.

                Hope this helps.
                P4 Northwood 1.8GHz@2.7GHz 1.65V Albatron PX845PEV Pro
                Running two Dell 2005FPW 20" Widescreen LCD
                And of course, Matrox Parhelia | My Matrox histroy: Mill-I, Mill-II, Mystique, G400, Parhelia

                Comment


                • #9
                  The machines in question were both dailup networking to our University. The kid hasn't brought the machine back so I'm presuming uninstalling and re-installing the dialup networking has cured it.
                  Chief Lemon Buyer no more Linux sucks but not as much
                  Weather nut and sad git.

                  My Weather Page

                  Comment

                  Working...
                  X