Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Code Project
  1. Home
  2. Database & SysAdmin
  3. System Admin
  4. dns problems

dns problems

Scheduled Pinned Locked Moved System Admin
sysadmincsharpasp-nethelpquestion
4 Posts 2 Posters 0 Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • S Offline
    S Offline
    Senkwe Chanda
    wrote on last edited by
    #1

    Hi guys, hope there are a few networking gurus online today. I have two machines, a Win2K box and an XP box. I set up the Win2K box with a static IP address and configured it as a DHCP and DNS server. When I first boot up the Win2K and XP boxes, the XP box gets a valid IP from the DHCP server. In addition running "nslookup" on the XP box shows that all is well. However, after a few seconds of being able to access the default share on the Win2K box from the XP box (with me so far?) I get an error message on the XP box stating that the network connection is no longer available. Running "nslookup" on the XP box now returns the infamous "DNS request timed out" "timout was 2 seconds" I'm also unable to ping the Win2K box by name (obviously) OR by IP address. It's like suddenly the DNS server doesn't exist. Mind you, I'm unable to ping the XP box from the Win2K box either. Soon as I reboot the Win2K box though, everything is fine until I again dare to browse across the network. Back to square one. Any ideas? ASP.NET can never fail as working with it is like fitting bras to supermodels - it's one pleasure after the next - David Wulff

    R 1 Reply Last reply
    0
    • S Senkwe Chanda

      Hi guys, hope there are a few networking gurus online today. I have two machines, a Win2K box and an XP box. I set up the Win2K box with a static IP address and configured it as a DHCP and DNS server. When I first boot up the Win2K and XP boxes, the XP box gets a valid IP from the DHCP server. In addition running "nslookup" on the XP box shows that all is well. However, after a few seconds of being able to access the default share on the Win2K box from the XP box (with me so far?) I get an error message on the XP box stating that the network connection is no longer available. Running "nslookup" on the XP box now returns the infamous "DNS request timed out" "timout was 2 seconds" I'm also unable to ping the Win2K box by name (obviously) OR by IP address. It's like suddenly the DNS server doesn't exist. Mind you, I'm unable to ping the XP box from the Win2K box either. Soon as I reboot the Win2K box though, everything is fine until I again dare to browse across the network. Back to square one. Any ideas? ASP.NET can never fail as working with it is like fitting bras to supermodels - it's one pleasure after the next - David Wulff

      R Offline
      R Offline
      Roger Wright
      wrote on last edited by
      #2

      I wish I could help, but all I can do is commiserate. I've had Win2K Server running DNS for over a year, and it's never worked correctly. I've read books, online articles, every single "solution" in the MS Knowledge base, yet nothing works. It can't find anything if I use it instead of my ISP's DNS, and it seems to be at the root of the problem of the server freezing up every few days. A reboot restores everything, and the DNS even seems to work for a while, but it shortly begins malfunctioning again. Just out of curiosity, are you getting a ton of NetLogon 5774 errors in the Event log? Ancient man conquered his rivals with the jawbone of an ass; modern man uses the jawbone of a politician.

      S 1 Reply Last reply
      0
      • R Roger Wright

        I wish I could help, but all I can do is commiserate. I've had Win2K Server running DNS for over a year, and it's never worked correctly. I've read books, online articles, every single "solution" in the MS Knowledge base, yet nothing works. It can't find anything if I use it instead of my ISP's DNS, and it seems to be at the root of the problem of the server freezing up every few days. A reboot restores everything, and the DNS even seems to work for a while, but it shortly begins malfunctioning again. Just out of curiosity, are you getting a ton of NetLogon 5774 errors in the Event log? Ancient man conquered his rivals with the jawbone of an ass; modern man uses the jawbone of a politician.

        S Offline
        S Offline
        Senkwe Chanda
        wrote on last edited by
        #3

        Roger Wright wrote: are you getting a ton of NetLogon 5774 errors in the Event log Nope, I clear the Event Log and it remains clean as a whistle. It's just that all of a sudden I'm unable to contact my DNS server after a few seconds of browsing. It's totally frustrating. I've even done a step by step configuration using Mark Minasis' excellent book on Windows 2000 server. Nothing helps. I've ruined one mouse already after slamming it against the wall in frustration. Setting up a DNS server is not rocket science, especially when the "network" is only 2 PC's big and not connected to the internet in any way. I just don't know. ASP.NET can never fail as working with it is like fitting bras to supermodels - it's one pleasure after the next - David Wulff

        R 1 Reply Last reply
        0
        • S Senkwe Chanda

          Roger Wright wrote: are you getting a ton of NetLogon 5774 errors in the Event log Nope, I clear the Event Log and it remains clean as a whistle. It's just that all of a sudden I'm unable to contact my DNS server after a few seconds of browsing. It's totally frustrating. I've even done a step by step configuration using Mark Minasis' excellent book on Windows 2000 server. Nothing helps. I've ruined one mouse already after slamming it against the wall in frustration. Setting up a DNS server is not rocket science, especially when the "network" is only 2 PC's big and not connected to the internet in any way. I just don't know. ASP.NET can never fail as working with it is like fitting bras to supermodels - it's one pleasure after the next - David Wulff

          R Offline
          R Offline
          Roger Wright
          wrote on last edited by
          #4

          Senkwe Chanda wrote: I clear the Event Log and it remains clean as a whistle Must be nice! I clear mine every two days, as it fills completely with 5774 errors. You're right, it's not rocket science, and it shouldn't be hard at all, especially with your configuration! Mine is similar, two hosts (though one is rarely switched on), but I have a dual-homed server with one card on the LAN and the other on the Internet. I set up DNS using the automatic settings created by the windows installer, including the Default-Site zones that not one of the books on the subject mentions. I'm tempted to create another zone and configure it manually, then delete the defaults, but I'm chicken...:eek: Good luck!:-D Ancient man conquered his rivals with the jawbone of an ass; modern man uses the jawbone of a politician.

          1 Reply Last reply
          0
          Reply
          • Reply as topic
          Log in to reply
          • Oldest to Newest
          • Newest to Oldest
          • Most Votes


          • Login

          • Don't have an account? Register

          • Login or register to search.
          • First post
            Last post
          0
          • Categories
          • Recent
          • Tags
          • Popular
          • World
          • Users
          • Groups