Announcement

Collapse
No announcement yet.

Corrupt WINS

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

  • Corrupt WINS

    I am having some local name resolution issues. My two DCs are Server 2003. I am noticing some machines that can't log in because they say the domain trust with the local machine is broken, then some cannot get to file shares by \\SERVER on any file shares on the Server 2003 machines. On any server 2008 machines it works fine. Is this because Server 2008 does not require WINS?

    I got WINS errors on one of the DCs and I moved all the C:\windows\system23\wins files into a Directory called OLDwins. Then I could get WINS to start, but now that it's a new database I'm wondering if that is what is causing my name resolution issues. Should'nt DNS though pick up and take me to \\SERVER when I try?

    Thanks,

    Brian

  • #2
    Re: Corrupt WINS

    seems like a DNS Search suffix is not applied.

    could you please post output of ipconfig /all from a problematic server?
    Please do show your appreciation to those who assist you by leaving Rep Point https://www.petri.com/forums/core/im.../icon_beer.gif

    Comment


    • #3
      Re: Corrupt WINS

      Originally posted by tehcamel View Post
      seems like a DNS Search suffix is not applied.

      could you please post output of ipconfig /all from a problematic server?
      Microsoft Windows [Version 5.2.3790]
      (C) Copyright 1985-2003 Microsoft Corp.

      C:\Documents and Settings\Administrator.RTS>ipconfig /all

      Windows IP Configuration

      Host Name . . . . . . . . . . . . : vnetfs1
      Primary Dns Suffix . . . . . . . : location.company.com
      Node Type . . . . . . . . . . . . : Hybrid
      IP Routing Enabled. . . . . . . . : No
      WINS Proxy Enabled. . . . . . . . : No
      DNS Suffix Search List. . . . . . : location.company.com


      Ethernet adapter Local Area Connection:

      Connection-specific DNS Suffix . :
      Description . . . . . . . . . . . : Broadcom BCM5708C NetXtreme II GigE (NDIS
      VBD Client)
      Physical Address. . . . . . . . . : 00-19-B9-C2-2C-90
      DHCP Enabled. . . . . . . . . . . : No
      IP Address. . . . . . . . . . . . : 10.10.10.84
      Subnet Mask . . . . . . . . . . . : 255.255.255.0
      Default Gateway . . . . . . . . . : 10.10.10.254
      DNS Servers . . . . . . . . . . . : 10.10.10.84
      Primary WINS Server . . . . . . . : 10.10.10.84

      Comment


      • #4
        Re: Corrupt WINS

        Is this server your DC/DNS server?
        if not, the network configuration should be pointing to the DNS server for DNS (similar for WINS) not to the same IP as the server itself:

        IP Address. . . . . . . . . . . . : 10.10.10.84
        Subnet Mask . . . . . . . . . . . : 255.255.255.0
        Default Gateway . . . . . . . . . : 10.10.10.254
        DNS Servers . . . . . . . . . . . : IP OF DNS SERVER
        Primary WINS Server . . . . . . . : IP OF WINS SERVER
        Tom Jones
        MCT, MCSE (2000:Security & 2003), MCSA:Security & Messaging, MCDBA, MCDST, MCITP(EA, EMA, SA, EDA, ES, CS), MCTS, MCP, Sec+
        PhD, MSc, FIAP, MIITT
        IT Trainer / Consultant
        Ossian Ltd
        Scotland

        ** Remember to give credit where credit is due and leave reputation points where appropriate **

        Comment


        • #5
          Re: Corrupt WINS

          Originally posted by Ossian View Post
          Is this server your DC/DNS server?
          if not, the network configuration should be pointing to the DNS server for DNS (similar for WINS) not to the same IP as the server itself:

          IP Address. . . . . . . . . . . . : 10.10.10.84
          Subnet Mask . . . . . . . . . . . : 255.255.255.0
          Default Gateway . . . . . . . . . : 10.10.10.254
          DNS Servers . . . . . . . . . . . : IP OF DNS SERVER
          Primary WINS Server . . . . . . . : IP OF WINS SERVER
          This Server is a DC and DNS. This is the server that was showing a corrupt WINS database, and I removed the database and created a new one so that I could get WINS to start on it.

          I am looking at our other DC (Vnetadc2) that also runs DNS and it is showing a DNS error. It runs DNS and It's IP is 10.10.10.87. Maybe some machines are pointing to it and that is causing the problem? but why wouldn't they fail over to the other with the working DNS?

          Comment


          • #6
            Re: Corrupt WINS

            Why not get rid of WINS altogether? I haven't run a WINS server since Windows NT.

            Comment


            • #7
              Re: Corrupt WINS

              Originally posted by joeqwerty View Post
              Why not get rid of WINS altogether? I haven't run a WINS server since Windows NT.
              All depends on the infrastructure

              http://www.techrepublic.com/article/...d-2003/5820760

              Comment


              • #8
                Re: Corrupt WINS

                Eventually that's the plan. Upgrade both DCs to Server 2008 and get rid of WINS.

                Comment


                • #9
                  Re: Corrupt WINS

                  Is it the case that you think WINS is currently neccessary? I haven't seen an infrastructure since Windows NT where WINS was needed.

                  Comment


                  • #10
                    Re: Corrupt WINS

                    When it's not running I have trouble getting to network shares by name, but only network shares on the Server 2003 machines. I'm guessing that something on Server 2003 is using it.

                    Now that it's running again things have been ok.

                    Comment

                    Working...
                    X