Announcement

Collapse
No announcement yet.

Help Getting AD Working

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

  • Help Getting AD Working

    Hello all,

    My first post. I had the exact same situation:
    geekswithblogs.net mhamilton archive 2007 04 15 111674.

    (add http at the beginning, the spaces are /'s and aspx at the end)

    or google: How to recover domain when the primary domain controller failes and there are member domain controllers

    I followed the instructions and was able to seize the 4 fsmo roles.

    Now:
    - users can't join the domain; error details say that no DC can be contacted and that there are SRV records missing.

    I'm sure I understand why it is saying this.

    Can anyone help me to take one problem at a time and go through this?

    Any help to move me forward would be appreciated.
    Right now, dcdiag shows some successes and some failures. I'm not sure what to try to tacle next? There are still traces of other obsolete DC's in AD, so maybe I have to do that first?
    I was also thinking to try to completely remove DNS and WINS and then reinstall from scratch.

    Can anyone help to get me going, here? I would prefer detailed help, if possible.

    Thanks in advance!

  • #2
    Re: Help Getting AD Working

    What OS?
    What domain and forest functional levels?
    Please describe your environment a bit more (sites, DCs etc)?

    First thoughts:
    Check replication using repadmin/showrepl
    Run a DCDIAG
    Check at least one server is a GC
    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


    • #3
      Re: Help Getting AD Working

      Thanks for the fast reply!

      Win2k server (yes..I know )

      Wasn't sure what you meant about "What domain and forest functional levels?" so I got this:
      In Windows 2000, the terminology for domain functional levels was domain modes. Forests in Windows 2000 have one mode and domains can have the domain mode set as either mixed mode or native mode. With Windows Server 2003 Active Directory came the introduction of the Windows Server 2003 interim functional level and Windows Server 2003 functional level for both domains and forests. The four domain functional levels that can be set for domain controllers are Windows 2000 mixed, Windows 2000 native, Windows Server 2003 interim, and Windows Server 2003. The default domain functional level is Windows 2000 mixed. The three forest functional levels are Windows 2000, Windows Server 2003 interim, and Windows Server 2003. The default forest functional level is Windows 2000.

      I believe it is mixed mode, compatible with NT4 domains.

      There were 2 DC's. P & B. P failed. Now I have the Backup showing that it is the operations master in AD Users and Computers.
      In AD sites and services I still see the orphaned server listed and there is another older orphaned server listed there also.

      It was always just one domain - very simple.

      I will run those and post the results? Is that what's next?

      EDIT: just finished completing authoritative time server. Was also giving me that error.
      Last edited by GreenGhost; 2nd April 2012, 09:46.

      Comment


      • #4
        Re: Help Getting AD Working

        Ran that, here they are:


        C:\>dcdiag

        DC Diagnosis

        Performing initial setup:
        Done gathering initial info.

        Doing initial non skippeable tests

        Testing server: xxxx01\NETSERVER
        Starting test: Connectivity
        ......................... NETSERVER passed test Connectivity

        Doing primary tests

        Testing server: xxxx01\NETSERVER
        Starting test: Replications
        [Replications Check,NETSERVER] A recent replication attempt failed:
        From REMNETSERVER to NETSERVER
        Naming Context: CN=Schema,CN=Configuration,DC=xxxx01,DC=xxxxxxxxx, DC=com
        The replication generated an error (8524):
        The DSA operation is unable to proceed because of a DNS lookup failure.
        The failure occurred at 2012-04-02 04:58.21.
        The last success occurred at 2008-10-28 13:48.08.
        13647 failures have occurred since the last success.
        The guid-based DNS name a5f620e9-d69f-452a-8b1f-581c74a27ab5._msdcs.xxxx01.xxxxxxxxx.com
        is not registered on one or more DNS servers.
        [REMNETSERVER] DsBind() failed with error 1722,
        The RPC server is unavailable..
        [Replications Check,NETSERVER] A recent replication attempt failed:
        From LANSERVER to NETSERVER
        Naming Context: CN=Schema,CN=Configuration,DC=xxxx01,DC=xxxxxxxxx, DC=com
        The replication generated an error (8524):
        The DSA operation is unable to proceed because of a DNS lookup failure.
        The failure occurred at 2012-04-02 04:58.21.
        The last success occurred at 2008-10-28 21:53.47.
        13637 failures have occurred since the last success.
        The guid-based DNS name c85d3526-4767-41c9-bc2a-da1bf5e71da1._msdcs.xxxx01.xxxxxxxxx.com
        is not registered on one or more DNS servers.
        [LANSERVER] DsBind() failed with error 1722,
        The RPC server is unavailable..
        [Replications Check,NETSERVER] A recent replication attempt failed:
        From REMNETSERVER to NETSERVER
        Naming Context: CN=Configuration,DC=xxxx01,DC=xxxxxxxxx,DC=com
        The replication generated an error (8524):
        The DSA operation is unable to proceed because of a DNS lookup failure.
        The failure occurred at 2012-04-02 04:58.21.
        The last success occurred at 2008-10-28 13:48.08.
        13648 failures have occurred since the last success.
        The guid-based DNS name a5f620e9-d69f-452a-8b1f-581c74a27ab5._msdcs.xxxx01.xxxxxxxxx.com
        is not registered on one or more DNS servers.
        [Replications Check,NETSERVER] A recent replication attempt failed:
        From LANSERVER to NETSERVER
        Naming Context: CN=Configuration,DC=xxxx01,DC=xxxxxxxxx,DC=com
        The replication generated an error (8524):
        The DSA operation is unable to proceed because of a DNS lookup failure.
        The failure occurred at 2012-04-02 04:58.21.
        The last success occurred at 2008-10-28 21:54.00.
        13638 failures have occurred since the last success.
        The guid-based DNS name c85d3526-4767-41c9-bc2a-da1bf5e71da1._msdcs.xxxx01.xxxxxxxxx.com
        is not registered on one or more DNS servers.
        [Replications Check,NETSERVER] A recent replication attempt failed:
        From REMNETSERVER to NETSERVER
        Naming Context: DC=xxxx01,DC=xxxxxxxxx,DC=com
        The replication generated an error (8524):
        The DSA operation is unable to proceed because of a DNS lookup failure.
        The failure occurred at 2012-04-02 04:58.21.
        The last success occurred at 2008-10-28 13:48.08.
        13650 failures have occurred since the last success.
        The guid-based DNS name a5f620e9-d69f-452a-8b1f-581c74a27ab5._msdcs.xxxx01.xxxxxxxxx.com
        is not registered on one or more DNS servers.
        [Replications Check,NETSERVER] A recent replication attempt failed:
        From LANSERVER to NETSERVER
        Naming Context: DC=xxxx01,DC=xxxxxxxxx,DC=com
        The replication generated an error (8524):
        The DSA operation is unable to proceed because of a DNS lookup failure.
        The failure occurred at 2012-04-02 04:58.21.
        The last success occurred at 2008-10-28 21:53.46.
        13640 failures have occurred since the last success.
        The guid-based DNS name c85d3526-4767-41c9-bc2a-da1bf5e71da1._msdcs.xxxx01.xxxxxxxxx.com
        is not registered on one or more DNS servers.
        ......................... NETSERVER passed test Replications
        tarting test: NCSecDesc
        ......................... NETSERVER passed test NCSecDesc
        tarting test: NetLogons
        ......................... NETSERVER passed test NetLogons
        tarting test: Advertising
        Fatal ErrorsGetDcName (NETSERVER) call failed, error 1355
        The Locator could not find the server.
        ......................... NETSERVER failed test Advertising
        tarting test: KnowsOfRoleHolders
        ......................... NETSERVER passed test KnowsOfRoleHolders
        tarting test: RidManager
        ......................... NETSERVER passed test RidManager
        tarting test: MachineAccount
        ......................... NETSERVER passed test MachineAccount
        tarting test: Services
        ......................... NETSERVER passed test Services
        tarting test: ObjectsReplicated
        ......................... NETSERVER passed test ObjectsReplicated
        tarting test: frssysvol
        Error: No record of File Replication System, SYSVOL started.
        The Active Directory may be prevented from starting.
        There are errors after the SYSVOL has been shared.
        The SYSVOL can prevent the AD from starting.
        ......................... NETSERVER passed test frssysvol
        tarting test: kccevent
        An Error Event occured. EventID: 0xC0000466
        Time Generated: 04/02/2012 04:59:56
        (Event String could not be retrieved)
        ......................... NETSERVER failed test kccevent
        tarting test: systemlog
        An Error Event occured. EventID: 0xC00A0032
        Time Generated: 04/02/2012 04:32:12
        Event String: The RDP protocol component "DATA ENCRYPTION"
        An Error Event occured. EventID: 0x00000457
        Time Generated: 04/02/2012 04:37:31
        Event String: Driver Samsung ML-1640 Series required for
        An Error Event occured. EventID: 0x00000452
        Time Generated: 04/02/2012 04:37:31
        Event String: The printer could not be installed.
        An Error Event occured. EventID: 0x00000457
        Time Generated: 04/02/2012 04:37:32
        Event String: Driver HP psc 1600 series required for printer
        An Error Event occured. EventID: 0x00000452
        Time Generated: 04/02/2012 04:37:32
        Event String: The printer could not be installed.
        An Error Event occured. EventID: 0x00000457
        Time Generated: 04/02/2012 04:37:40
        Event String: Driver HP ePrint Mobile required for printer
        An Error Event occured. EventID: 0x00000452
        Time Generated: 04/02/2012 04:37:40
        Event String: The printer could not be installed.
        An Error Event occured. EventID: 0x00000457
        Time Generated: 04/02/2012 04:37:41
        Event String: Driver HP Photosmart D110 series required for
        An Error Event occured. EventID: 0x00000452
        Time Generated: 04/02/2012 04:37:41
        Event String: The printer could not be installed.
        An Error Event occured. EventID: 0x00000457
        Time Generated: 04/02/2012 04:37:41
        Event String: Driver Microsoft XPS Document Writer required for
        An Error Event occured. EventID: 0x00000452
        Time Generated: 04/02/2012 04:37:41
        Event String: The printer could not be installed.
        An Error Event occured. EventID: 0x00000457
        Time Generated: 04/02/2012 04:37:42
        Event String: Driver Samsung ML-1640 Series required for
        An Error Event occured. EventID: 0x00000452
        Time Generated: 04/02/2012 04:37:42
        Event String: The printer could not be installed.
        An Error Event occured. EventID: 0x0000041B
        Time Generated: 04/02/2012 04:51:54
        Event String: The DHCP/BINL service has determined that it is
        An Error Event occured. EventID: 0x00000416
        Time Generated: 04/02/2012 04:51:55
        Event String: The DHCP/BINL service on the local machine,
        ......................... NETSERVER failed test systemlog

        Running enterprise tests on : xxxx01.xxxxxxxxx.com
        Starting test: Intersite
        ......................... xxxx01.xxxxxxxxx.com passed test Intersite
        Starting test: FsmoCheck
        Warning: DcGetDcName(GC_SERVER_REQUIRED) call failed, error 1355
        A Global Catalog Server could not be located - All GC's are down.
        Warning: DcGetDcName(TIME_SERVER) call failed, error 1355
        A Time Server could not be located.
        The server holding the PDC role is down.
        Warning: DcGetDcName(GOOD_TIME_SERVER_PREFERRED) call failed, error 1355
        A Good Time Server could not be located.
        Warning: DcGetDcName(KDC_REQUIRED) call failed, error 1355
        A KDC could not be located - All the KDCs are down.
        ......................... xxxx01.xxxxxxxxx.com failed test FsmoCheck

        The system log errors are because I was RDP'd in and it couldn't load the printer drivers for my laptop, just ignore that.
        Last edited by GreenGhost; 2nd April 2012, 11:27.

        Comment


        • #5
          Re: Help Getting AD Working

          And the other:


          C:\>repadmin
          Usage: repadmin <cmd> <args> [/u:{domain\\user}] [/pw:{password|*}]

          Supported <cmd>s & args:
          /sync <Naming Context> <Dest DSA> <Source DSA UUID> [/force] [/async]
          [/full] [/addref] [/allsources]
          /syncall <Dest DSA> [<Naming Context>] [<flags>]
          /kcc [DSA] [/async]
          /bind [DSA]
          /propcheck <Naming Context> <Originating DSA Invocation ID>
          <Originating USN> [DSA from which to enumerate host DSAs]
          /getchanges NamingContext [SourceDSA] [/cookie:<file>]
          /getchanges NamingContext [DestDSA] SourceDSAObjectGuid
          [/verbose] [/statistics]

          /showreps [Naming Context] [DSA [Source DSA objectGuid]] [/verbose]
          [/unreplicated] [/nocache]
          /showvector <Naming Context> [DSA] [/nocache]
          /showmeta <Object DN> [DSA] [/nocache]
          /showtime <DS time value>
          /showmsg <Win32 error>
          /showism [<Transport DN>] [/verbose] (must be executed locally)
          /showsig [DSA]
          /showconn [DSA] [Container DN | <DSA guid>] (default is local site)
          /showcert [DSA]

          /queue [DSA]
          /failcache [DSA]
          /showctx [DSA] [/nocache]

          Note:- <Dest DSA>, <Source DSA>, <DSA> : Names of the appropriate servers
          <Naming Context> is the Distinguished Name of the root of the NC
          Example: DC=My-Domain,DC=Microsoft,DC=Com
          ----------------------------------------------------------------------------

          C:\>repadmin /showreps
          xxxx01\NETSERVER
          DSA Options : IS_GC
          objectGuid : 406c474f-2c2d-4da7-b2e8-10cb3920e19c
          invocationID: 49f04b44-1c06-4f80-bfe6-187669b8b2d0

          ==== INBOUND NEIGHBORS ======================================

          CN=Schema,CN=Configuration,DC=xxxx01,DC=xxxxxxxxx, DC=com
          xxxx01\REMNETSERVER via RPC
          objectGuid: a5f620e9-d69f-452a-8b1f-581c74a27ab5
          Last attempt @ 2012-04-02 03:58.21 failed, result 8524:
          The DSA operation is unable to proceed because of a DNS lookup failure.
          Last success @ 2008-10-28 13:48.08.
          13646 consecutive failure(s).
          xxxx01\LANSERVER via RPC
          objectGuid: c85d3526-4767-41c9-bc2a-da1bf5e71da1
          Last attempt @ 2012-04-02 03:58.21 failed, result 8524:
          The DSA operation is unable to proceed because of a DNS lookup failure.
          Last success @ 2008-10-28 21:53.47.
          13636 consecutive failure(s).

          CN=Configuration,DC=xxxx01,DC=xxxxxxxxxx,DC=com
          xxxx01\REMNETSERVER via RPC
          objectGuid: a5f620e9-d69f-452a-8b1f-581c74a27ab5
          Last attempt @ 2012-04-02 03:58.21 failed, result 8524:
          The DSA operation is unable to proceed because of a DNS lookup failure.
          Last success @ 2008-10-28 13:48.08.
          13647 consecutive failure(s).
          xxxx01\LANSERVER via RPC
          objectGuid: c85d3526-4767-41c9-bc2a-da1bf5e71da1
          Last attempt @ 2012-04-02 03:58.21 failed, result 8524:
          The DSA operation is unable to proceed because of a DNS lookup failure.
          Last success @ 2008-10-28 21:54.00.
          13637 consecutive failure(s).

          DC=xxxx01,DC=gerardfiorito,DC=com
          xxxx01\REMNETSERVER via RPC
          objectGuid: a5f620e9-d69f-452a-8b1f-581c74a27ab5
          Last attempt @ 2012-04-02 03:58.21 failed, result 8524:
          The DSA operation is unable to proceed because of a DNS lookup failure.
          Last success @ 2008-10-28 13:48.08.
          13649 consecutive failure(s).
          xxxx01\LANSERVER via RPC
          objectGuid: c85d3526-4767-41c9-bc2a-da1bf5e71da1
          Last attempt @ 2012-04-02 03:58.21 failed, result 8524:
          The DSA operation is unable to proceed because of a DNS lookup failure.
          Last success @ 2008-10-28 21:53.46.
          13639 consecutive failure(s).

          ==== OUTBOUND NEIGHBORS FOR CHANGE NOTIFICATIONS ============

          CN=Schema,CN=Configuration,DC=xxxx01,DC=xxxxxxxxxx ,DC=com
          xxxx01\LANSERVER via RPC
          objectGuid: c85d3526-4767-41c9-bc2a-da1bf5e71da1

          CN=Configuration,DC=YUL001,DC=xxxxxxxxxxx,DC=com
          xxxx01\LANSERVER via RPC
          objectGuid: c85d3526-4767-41c9-bc2a-da1bf5e71da1

          DC=xxxx01,DC=xxxxxxxxxx,DC=com
          xxxx01\LANSERVER via RPC
          objectGuid: c85d3526-4767-41c9-bc2a-da1bf5e71da1

          C:\>

          Comment


          • #6
            Re: Help Getting AD Working

            As you can see, No GC's

            DNS is pointing to the orphaned PDC. So nothing works.

            The blog I found and used to help me just prior, was saying not to Seize the Infrastructure Master role, it's not desirable to have the IM role on the same DC as the GC server. he said if the IM runs on a GC server it would stop updating object information because it doesn't contain any references to objects that it doesn't hold.
            So I only seized the 4 other roles.

            I just don't know what to do next.

            The machine I'm trying to promote is the one called NETSERVER. I also have another machine on the network, a win2k3 server that is stand alone. I don't know if that is useful but it's there.

            Thanks for your help.
            Last edited by GreenGhost; 2nd April 2012, 10:48.

            Comment


            • #7
              Re: Help Getting AD Working

              IM on a GC is only an issue with multiple domains -- you need at least one GC for AD to function properly (think single DC environment)

              There is a very good article on the main site on cleaning up active directory -- for "metadata cleanup
              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


              • #8
                Re: Help Getting AD Working

                So are you saying I should I have Seized that 5th role anyways? For the IM?

                Comment


                • #9
                  Re: Help Getting AD Working

                  I was also trying to get the NTP service configured before. I need to open a port on the router to enable that, right?

                  The router itself is a reliable time source. Can Win2k server get the time from the router? It would save opening a port. I can configure the router to broadcast but I'm not sure that Windows server can receive those?

                  Anyone know?

                  Comment


                  • #10
                    Re: Help Getting AD Working

                    All your FSMOs will need to be on a live DC, as will DNS and it should be a GC
                    Get that sorted first, then deal with time later (I have never opened specific ports for time)
                    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


                    • #11
                      Re: Help Getting AD Working

                      Have time to work on this, this weekend.

                      Seized the infrastructure master role

                      still have the same problem with workstations not being able to join.

                      I will look at the article you mentioned about cleaning up the metadata and see how far I can get doing that

                      Comment


                      • #12
                        Re: Help Getting AD Working

                        The error I'm getting from the workstations when they try to connect to the domain is a DNS failure error.

                        It's saying that they couldn't find a domain controller. In fact the query is being directed to the old PDC that doesn't exist anymore.

                        This is the error:
                        --------------------------------------------------------------------------------------------------------

                        Note: This information is intended for a network administrator. If you are not your network's administrator, notify the

                        administrator that you received this information, which has been recorded in the file C:\WINDOWS\debug\dcdiag.txt.

                        DNS was successfully queried for the service location (SRV) resource record used to locate a domain controller for domain

                        xxxx01.xxxxxxxxxxxxx.com:

                        The query was for the SRV record for _ldap._tcp.dc._msdcs.xxxx01.xxxxxxxxxxxxx.com

                        The following domain controllers were identified by the query:

                        netserver.xxxx01.xxxxxxxxxxxxx.com

                        Common causes of this error include:

                        - Host (A) records that map the name of the domain controller to its IP addresses are missing or contain incorrect addresses.

                        - Domain controllers registered in DNS are not connected to the network or are not running.

                        For information about correcting this problem, click Help.

                        --------------------------------------------------------------------------------------------------------

                        So it's looking for the old PDC that doesn't exist anymore.

                        What is the best way to proceed here?

                        - clean up the metadata (using that article that you mentioned)

                        or

                        - forget cleaning up and try to fix the DNS first?

                        Comment


                        • #13
                          Re: Help Getting AD Working

                          Can you post an IPCONFIG/ALL from a (working) DC and from a client?
                          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


                          • #14
                            Re: Help Getting AD Working

                            From the DC:

                            C:\>ipconfig /all

                            Windows 2000 IP Configuration

                            Host Name . . . . . . . . . . . . : netserver
                            Primary DNS Suffix . . . . . . . : XXXX01.xxxxxxxxxxxxx.com
                            Node Type . . . . . . . . . . . . : Hybrid
                            IP Routing Enabled. . . . . . . . : Yes
                            WINS Proxy Enabled. . . . . . . . : No
                            DNS Suffix Search List. . . . . . : XXXX01.xxxxxxxxxxxxx.com
                            xxxxxxxxxxx.com

                            Ethernet adapter NTSRVR_XXXX01_Main:

                            Connection-specific DNS Suffix . :
                            Description . . . . . . . . . . . : Intel(R) PRO/100 VE Desktop Connection
                            Physical Address. . . . . . . . . : XX-XX-XX-XX-XX-C4
                            DHCP Enabled. . . . . . . . . . . : No
                            IP Address. . . . . . . . . . . . : 192.168.8.99
                            Subnet Mask . . . . . . . . . . . : 255.255.255.224
                            Default Gateway . . . . . . . . . : 192.168.8.97
                            DNS Servers . . . . . . . . . . . : 192.168.8.99
                            192.168.8.100
                            Primary WINS Server . . . . . . . : 192.168.8.100
                            Secondary WINS Server . . . . . . : 192.168.8.99

                            Comment


                            • #15
                              Re: Help Getting AD Working

                              From a workstation (mine):


                              Microsoft Windows [Version 6.0.6002]
                              Copyright (c) 2006 Microsoft Corporation. All rights reserved.

                              c:\ipconfig /all

                              Windows IP Configuration

                              Host Name . . . . . . . . . . . . : WORKSTATION7
                              Primary Dns Suffix . . . . . . . :
                              Node Type . . . . . . . . . . . . : Hybrid
                              IP Routing Enabled. . . . . . . . : No
                              WINS Proxy Enabled. . . . . . . . : No
                              DNS Suffix Search List. . . . . . : XXXX01.xxxxxxxxxxx.com

                              Wireless LAN adapter WLAN:

                              Media State . . . . . . . . . . . : Media disconnected
                              Connection-specific DNS Suffix . :
                              Description . . . . . . . . . . . : Intel(R) Wireless WiFi Link 5100
                              Physical Address. . . . . . . . . : XX-XX-XX-XX-XX-20
                              DHCP Enabled. . . . . . . . . . . : Yes
                              Autoconfiguration Enabled . . . . : Yes

                              Ethernet adapter LAN:

                              Connection-specific DNS Suffix . : XXXX01.xxxxxxxxxx.com
                              Description . . . . . . . . . . . : Marvell Yukon 88E8055 PCI-E Gigabit Ethernet Controller
                              Physical Address. . . . . . . . . : XX-XX-XX-XX-XX-26
                              DHCP Enabled. . . . . . . . . . . : Yes
                              Autoconfiguration Enabled . . . . : Yes
                              Link-local IPv6 Address . . . . . : XXXX::XXXX:34b0:80d:XXXX(Preferred)
                              IPv4 Address. . . . . . . . . . . : 192.168.8.125(Preferred)
                              Subnet Mask . . . . . . . . . . . : 255.255.255.224
                              Lease Obtained. . . . . . . . . . : April-16-12 2:37:53 AM
                              Lease Expires . . . . . . . . . . : April-21-12 2:37:52 AM
                              Default Gateway . . . . . . . . . : 192.168.8.97
                              DHCP Server . . . . . . . . . . . : 192.168.8.99
                              DHCPv6 IAID . . . . . . . . . . . : 25166XXXX
                              DHCPv6 Client DUID. . . . . . . . : XX-XX-XX-XX-XX-XX-XX-XX-XX-XX-XX-XX-XX-26
                              DNS Servers . . . . . . . . . . . : 192.168.8.100
                              192.168.8.99
                              Primary WINS Server . . . . . . . : 192.168.8.100
                              Secondary WINS Server . . . . . . : 192.168.8.99
                              NetBIOS over Tcpip. . . . . . . . : Enabled

                              .....snip......................................... ................................

                              Comment

                              Working...
                              X