DNS Authentication Issue

Discussion in 'MCSE' started by John West, Dec 3, 2004.

  1. John West

    John West Guest

    Gang,

    I have been working on trying to connect an XP workstation to a win 2003
    server and seem to be having some DNS issues. The error message below is
    from the XP workstation when I try to configure the client XP workstation to
    the domain phoenix.com.

    All computers have the latest and greatest patches and I can ping via name
    and ip address to the server from the client and from the server to the
    client via ip address. Also when I do an ns lookup on the server it comes
    back with server01.phoenix.com, also on the workstation has the same
    nslookup response

    Server 172.16.0.2 /24
    Workstation 172.16.0.5 /24
    Server name Server
    Domain=Phoenix.com

    Not sure if what other infor you will need.

    ***************************************************************
    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
    D:\WINDOWS\debug\dcdiag.txt.

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

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

    The following domain controllers were identified by the query:

    server01.phoenix.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.

    ***********************************************
     
    John West, Dec 3, 2004
    #1
    1. Advertising

  2. John West

    Neil Guest

    did you hear "John West" <> say in
    news:n35sd.174868$cJ3.155850@fed1read06:

    > Gang,
    >
    > I have been working on trying to connect an XP workstation to a win
    > 2003 server and seem to be having some DNS issues. The error message
    > below is from the XP workstation when I try to configure the client XP
    > workstation to the domain phoenix.com.
    >
    > All computers have the latest and greatest patches and I can ping via
    > name and ip address to the server from the client and from the server
    > to the client via ip address. Also when I do an ns lookup on the
    > server it comes back with server01.phoenix.com, also on the
    > workstation has the same nslookup response
    >
    > Server 172.16.0.2 /24
    > Workstation 172.16.0.5 /24
    > Server name Server
    > Domain=Phoenix.com
    >
    > Not sure if what other infor you will need.
    >
    > ***************************************************************
    > 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 D:\WINDOWS\debug\dcdiag.txt.
    >
    > DNS was successfully queried for the service location (SRV) resource
    > record used to locate a domain controller for domain Phoenix.com:
    >
    > The query was for the SRV record for _ldap._tcp.dc._msdcs.Phoenix.com
    >
    > The following domain controllers were identified by the query:
    >
    > server01.phoenix.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.
    >
    > ***********************************************
    >
    >


    other than checking the possible cuases listed in the error can you ping
    server01.pheonix.com and get replies? Is the DNS configured correctly?
    does this happen with just on machine or is this global to every machine?
    nslookup?

    this might be worth a read:

    http://support.microsoft.com/default.aspx?scid=kb;en-us;314861

    --
    Neil MCNGP #30
    "Human beings, who are almost unique in having the ability to
    learn from the experience of others, are also remarkable for
    their apparent disinclination to do so."
    -- a quote by Doug Adams (Author of the Hitchhiker's Guide to the Galaxy)
     
    Neil, Dec 4, 2004
    #2
    1. Advertising

  3. Finding a domain controller is a 2 step job:
    first, the client ask the DNS server for the name of DC.
    This is the query for _ldap._tcp.dc._msdcs.Phoenix.com which is successfull
    and return server01.phoenix.com
    Second, you have to resolve the IP address for the just found DC.
    This does not work.
    Can you ping server01.phoenix.com from your client?


    "John West" <> wrote in message
    news:n35sd.174868$cJ3.155850@fed1read06...
    > DNS was successfully queried for the service location (SRV) resource
    > record used to locate a domain controller for domain Phoenix.com:
    >
    > The query was for the SRV record for _ldap._tcp.dc._msdcs.Phoenix.com
    >
    > The following domain controllers were identified by the query:
    >
    > server01.phoenix.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.
     
    Corrado Labinaz, Dec 5, 2004
    #3
  4. John West

    beoweolf Guest

    Did you try running DCdiag /fix...on the server?

    What is your server DNS configuration? As requested in another message, is
    the client the only one with the problem or is this more general, wide
    spread? Are you running DHCP, AD-integrated DNS, have your run Scavenge?
    checked for duplicate IP addresses?



    "John West" <> wrote in message
    news:n35sd.174868$cJ3.155850@fed1read06...
    > Gang,
    >
    > I have been working on trying to connect an XP workstation to a win 2003
    > server and seem to be having some DNS issues. The error message below is
    > from the XP workstation when I try to configure the client XP workstation
    > to the domain phoenix.com.
    >
    > All computers have the latest and greatest patches and I can ping via name
    > and ip address to the server from the client and from the server to the
    > client via ip address. Also when I do an ns lookup on the server it comes
    > back with server01.phoenix.com, also on the workstation has the same
    > nslookup response
    >
    > Server 172.16.0.2 /24
    > Workstation 172.16.0.5 /24
    > Server name Server
    > Domain=Phoenix.com
    >
    > Not sure if what other infor you will need.
    >
    > ***************************************************************
    > 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
    > D:\WINDOWS\debug\dcdiag.txt.
    >
    > DNS was successfully queried for the service location (SRV) resource
    > record used to locate a domain controller for domain Phoenix.com:
    >
    > The query was for the SRV record for _ldap._tcp.dc._msdcs.Phoenix.com
    >
    > The following domain controllers were identified by the query:
    >
    > server01.phoenix.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.
    >
    > ***********************************************
    >
     
    beoweolf, Dec 5, 2004
    #4
  5. John West

    John West Guest

    Thanks for the reply I can ping the sever but when I do an nslookup I
    receive the messsage default server unknown and server 172.16.0.2 non
    existent domain.

    I can ping in both directions so I know the IP portion of this is good...

    Ant thoughts ?

    Thanks!
    John


    "Corrado Labinaz" <> wrote in message
    news:...
    > Finding a domain controller is a 2 step job:
    > first, the client ask the DNS server for the name of DC.
    > This is the query for _ldap._tcp.dc._msdcs.Phoenix.com which is
    > successfull and return server01.phoenix.com
    > Second, you have to resolve the IP address for the just found DC.
    > This does not work.
    > Can you ping server01.phoenix.com from your client?
    >
    >
    > "John West" <> wrote in message
    > news:n35sd.174868$cJ3.155850@fed1read06...
    >> DNS was successfully queried for the service location (SRV) resource
    >> record used to locate a domain controller for domain Phoenix.com:
    >>
    >> The query was for the SRV record for _ldap._tcp.dc._msdcs.Phoenix.com
    >>
    >> The following domain controllers were identified by the query:
    >>
    >> server01.phoenix.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.

    >
    >
     
    John West, Dec 6, 2004
    #5
  6. John West

    John West Guest

    I ran the test earlier and the only issue that failed was a test concerning
    DHCP not being able to find AD, really nothing as I am not using DHCP on
    this box. I guess i should disable the service :> But then again if DHCP
    cant find AD I wonder if DNS has the same issue? This box is runing an
    evualation copy not a full vesion but that should not make a difference.

    As for clients, all of them seem to have the same issue. As for the DHCP,
    AD-integrated DNS, yes this is what I am running. As for the Scavenge check
    I only have two current computers on this network to resolve this issue, at
    one point I had many but reduced to two computers now no possible way I
    could have dup IP addresses.

    What other logs or tests can I run for you guys?

    A phone call on this would be great and anyone who can fix this gets a quick
    50 via paypall or check from me. I have been working on this issue for the
    past 6 weeks off and on what a drag, but I am learning a lot!


    Any thoughts?

    Thanks

    John


    "beoweolf" <> wrote in message
    news:2CGsd.54774$...
    > Did you try running DCdiag /fix...on the server?
    >
    > What is your server DNS configuration? As requested in another message, is
    > the client the only one with the problem or is this more general, wide
    > spread? Are you running DHCP, AD-integrated DNS, have your run Scavenge?
    > checked for duplicate IP addresses?
    >
    >
    >
    > "John West" <> wrote in message
    > news:n35sd.174868$cJ3.155850@fed1read06...
    >> Gang,
    >>
    >> I have been working on trying to connect an XP workstation to a win 2003
    >> server and seem to be having some DNS issues. The error message below is
    >> from the XP workstation when I try to configure the client XP workstation
    >> to the domain phoenix.com.
    >>
    >> All computers have the latest and greatest patches and I can ping via
    >> name and ip address to the server from the client and from the server to
    >> the client via ip address. Also when I do an ns lookup on the server it
    >> comes back with server01.phoenix.com, also on the workstation has the
    >> same nslookup response
    >>
    >> Server 172.16.0.2 /24
    >> Workstation 172.16.0.5 /24
    >> Server name Server
    >> Domain=Phoenix.com
    >>
    >> Not sure if what other infor you will need.
    >>
    >> ***************************************************************
    >> 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
    >> D:\WINDOWS\debug\dcdiag.txt.
    >>
    >> DNS was successfully queried for the service location (SRV) resource
    >> record used to locate a domain controller for domain Phoenix.com:
    >>
    >> The query was for the SRV record for _ldap._tcp.dc._msdcs.Phoenix.com
    >>
    >> The following domain controllers were identified by the query:
    >>
    >> server01.phoenix.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.
    >>
    >> ***********************************************
    >>

    >
    >
     
    John West, Dec 6, 2004
    #6
  7. John West

    John West Guest

    Neil sorry I did not get back to you sooner! Yes I can ping
    server01.phoenix.com to the client and from the client to the server so
    network is working good. As for DNS being configured correclty everyting
    looks right from my end that is why I just do not understand what is going
    on with this issue.

    Any thoughts?

    Thanks

    John
    "Neil" <guess!!!@gmail.com> wrote in message
    news:Xns95B5A309DE0C3neilmcsegmailcom@207.46.248.16...
    > did you hear "John West" <> say in
    > news:n35sd.174868$cJ3.155850@fed1read06:
    >
    >> Gang,
    >>
    >> I have been working on trying to connect an XP workstation to a win
    >> 2003 server and seem to be having some DNS issues. The error message
    >> below is from the XP workstation when I try to configure the client XP
    >> workstation to the domain phoenix.com.
    >>
    >> All computers have the latest and greatest patches and I can ping via
    >> name and ip address to the server from the client and from the server
    >> to the client via ip address. Also when I do an ns lookup on the
    >> server it comes back with server01.phoenix.com, also on the
    >> workstation has the same nslookup response
    >>
    >> Server 172.16.0.2 /24
    >> Workstation 172.16.0.5 /24
    >> Server name Server
    >> Domain=Phoenix.com
    >>
    >> Not sure if what other infor you will need.
    >>
    >> ***************************************************************
    >> 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 D:\WINDOWS\debug\dcdiag.txt.
    >>
    >> DNS was successfully queried for the service location (SRV) resource
    >> record used to locate a domain controller for domain Phoenix.com:
    >>
    >> The query was for the SRV record for _ldap._tcp.dc._msdcs.Phoenix.com
    >>
    >> The following domain controllers were identified by the query:
    >>
    >> server01.phoenix.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.
    >>
    >> ***********************************************
    >>
    >>

    >
    > other than checking the possible cuases listed in the error can you ping
    > server01.pheonix.com and get replies? Is the DNS configured correctly?
    > does this happen with just on machine or is this global to every machine?
    > nslookup?
    >
    > this might be worth a read:
    >
    > http://support.microsoft.com/default.aspx?scid=kb;en-us;314861
    >
    > --
    > Neil MCNGP #30
    > "Human beings, who are almost unique in having the ability to
    > learn from the experience of others, are also remarkable for
    > their apparent disinclination to do so."
    > -- a quote by Doug Adams (Author of the Hitchhiker's Guide to the Galaxy)
     
    John West, Dec 6, 2004
    #7
  8. John West

    Neil Guest

    did you hear "John West" <> say in
    news:vSQsd.175754$cJ3.5266@fed1read06:

    > Neil sorry I did not get back to you sooner! Yes I can ping
    > server01.phoenix.com to the client and from the client to the server
    > so network is working good. As for DNS being configured correclty
    > everyting looks right from my end that is why I just do not understand
    > what is going on with this issue.
    >
    > Any thoughts?
    >
    > Thanks
    >
    > John



    since it's 2k3 drop down to a command prompt and run the dnslint command

    dnslint /ad /s /v server01.pheonix.com

    this might give you a better idea as to what's happening.

    More than that, well it looks fine from here :)

    --
    Neil MCNGP #30
    "Human beings, who are almost unique in having the ability to
    learn from the experience of others, are also remarkable for
    their apparent disinclination to do so."
    -- a quote by Doug Adams (Author of the Hitchhiker's Guide to the Galaxy)
     
    Neil, Dec 6, 2004
    #8
  9. John West

    Neil Guest

    did you hear Neil <guess!!!@gmail.com> say in
    news:Xns95B76A162E789neilmcsegmailcom@207.46.248.16:

    > dnslint /ad /s /v server01.pheonix.com


    feh, sorry, use the IP addy of server01 instead...

    --
    Neil MCNGP #30
    "Human beings, who are almost unique in having the ability to
    learn from the experience of others, are also remarkable for
    their apparent disinclination to do so."
    -- a quote by Doug Adams (Author of the Hitchhiker's Guide to the Galaxy)
     
    Neil, Dec 6, 2004
    #9
  10. John West

    John West Guest

    This is from the client side of things I have also changed the ip addressing
    fearing the ip zero subnet thing:> The nslookup thing really bugs me cant
    figure out why nslookup cant resolve the name in dns?



    ****************************************************************
    D:\tools>nltest /dclist:phoenix.com
    Get list of DCs in domain 'phoenix.com' from '\\server01.phoenix.com'.
    You don't have access to DsBind to phoenix.com (\\server01.phoenix.com)
    (Trying
    NetServerEnum).
    I_NetGetDCList failed: Status = 6118 0x17e6 ERROR_NO_BROWSER_SERVERS_FOUND
    *****************************************************************
    D:\tools>nltest /dcname:phoenix.com
    NetGetDCName failed: Status = 2453 0x995 NERR_DCNotFound
    ****************************************************************


    D:\tools>nltest /dsgetdc:phoenix.com
    DC: \\server01.phoenix.com
    Address: \\172.16.1.8
    Dom Guid: c8876d07-d748-47cc-9dde-9967cb103e46
    Dom Name: phoenix.com
    Forest Name: phoenix.com
    Dc Site Name: Default-First-Site-Name
    Our Site Name: Default-First-Site-Name
    Flags: PDC GC DS LDAP KDC TIMESERV GTIMESERV WRITABLE DNS_DC
    DNS_DOMAIN
    DNS_FOREST CLOSE_SITE
    The command completed successfully
    ***************************************************************
    D:\>nslookup
    *** Can't find server name for address 172.16.1.8: Non-existent domain
    *************************************************************








    "Neil" <guess!!!@gmail.com> wrote in message
    news:Xns95B76AF0EAFC6neilmcsegmailcom@207.46.248.16...
    > did you hear Neil <guess!!!@gmail.com> say in
    > news:Xns95B76A162E789neilmcsegmailcom@207.46.248.16:
    >
    >> dnslint /ad /s /v server01.pheonix.com

    >
    > feh, sorry, use the IP addy of server01 instead...
    >
    > --
    > Neil MCNGP #30
    > "Human beings, who are almost unique in having the ability to
    > learn from the experience of others, are also remarkable for
    > their apparent disinclination to do so."
    > -- a quote by Doug Adams (Author of the Hitchhiker's Guide to the Galaxy)
     
    John West, Dec 6, 2004
    #10
  11. John West

    John West Guest

    C:\TOOLS>dnslint /ad /s 172.16.1.8 /v

    DNSLint will attempt to verify the

    DNS entries used in AD replication

    Using 127.0.0.1 for LDAP

    Starting with 172.16.1.8 for DNS

    This process may take several minutes to complete...

    Finding the name of the root of the AD forest...found

    AD forest root is called:

    DC=phoenix,DC=com

    Attempting to get a list of GUIDs for the forest...

    DC: SERVER01

    GUID: ce44d53d-c8c5-4da4-b474-7b2fdb672a74

    1 GUIDs found



    by-passing www.internic.net lookup...

    using 172.16.1.8

    Attempting to find host name for 172.16.1.8...name

    found

    attempting to find authoritative DNS servers and

    to check them for records related to forest GUIDs...

    Checking SOA record on:

    phoenix.com (172.16.1.8)...

    Checking if _msdcs subdomain has been delegated to 172.16.1.8... SOA record
    does exist on name server _msdcs zone has been delegated...

    Authoritative name server: server01.phoenix.com

    Hostmaster: hostmaster.phoenix.com

    Zone serial number: 32

    Refresh period: 900 seconds

    Retry delay: 600 seconds

    Zone expires in: 86400 seconds

    Default (minimum) TTL: 3600 seconds

    Querying for NS records...

    Additional authoritative NS records for domain: server01.phoenix.com
    172.16.1.8



    querying for CNAME record data...

    querying CNAME record for:


    ce44d53d-c8c5-4da4-b474-7b2fdb672a74._msdcs.phoenix.com...found

    server01.phoenix.com

    finding the glue record...found

    IP address: 172.16.1.8

    =============================

    CNAME records found on this DNS server: 1

    Checking SOA record on:

    server01.phoenix.com (172.16.1.8)...

    Checking if _msdcs subdomain has been delegated to 172.16.1.8... SOA record
    does exist on name server _msdcs zone has been delegated...

    Authoritative name server: server01.phoenix.com

    Hostmaster: hostmaster.phoenix.com

    Zone serial number: 32

    Refresh period: 900 seconds

    Retry delay: 600 seconds

    Zone expires in: 86400 seconds

    Default (minimum) TTL: 3600 seconds

    Querying for NS records...

    Additional authoritative NS records for domain: server01.phoenix.com
    172.16.1.8



    querying for CNAME record data...

    querying CNAME record for:


    ce44d53d-c8c5-4da4-b474-7b2fdb672a74._msdcs.phoenix.com...found

    server01.phoenix.com

    finding the glue record...found

    IP address: 172.16.1.8

    =============================

    CNAME records found on this DNS server: 1

    A file called dnslint.htm already exists

    Do you want to overwrite it? (Y/N)y

    overwriting existing .htm file...

    __________________________________________________
     
    John West, Dec 6, 2004
    #11
  12. John West

    John West Guest

    Re: DNSLINT report

    DNSLint Report

    System Date: Mon Dec 06 09:21:45 2004

    Command run:

    DNSLINT /ad /s 172.16.1.8 /v

    Root of Active Directory Forest:

    phoenix.com

    Active Directory Forest Replication GUIDs Found:

    DC: SERVER01

    GUID: ce44d53d-c8c5-4da4-b474-7b2fdb672a74



    Total GUIDs found: 1

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

    The following 2 DNS servers were checked for records

    related to AD forest replication:

    DNS server: phoenix.com

    IP Address: 172.16.1.8

    UDP port 53 responding to queries: YES

    TCP port 53 responding to queries: Not tested

    Answering authoritatively for domain: NO

    SOA record data from server:

    Authoritative name server: server01.phoenix.com

    Hostmaster: hostmaster.phoenix.com

    Zone serial number: 32

    Zone expires in: 1.00 day(s)

    Refresh period: 900 seconds

    Retry delay: 600 seconds

    Default (minimum) TTL: 3600 seconds



    Additional authoritative (NS) records from server: server01.phoenix.com
    172.16.1.8







    Alias (CNAME) and glue (A) records for forest GUIDs

    from server:

    CNAME:

    ce44d53d-c8c5-4da4-b474-7b2fdb672a74._msdcs.phoenix.com

    Alias: server01.phoenix.com

    Glue: 172.16.1.8



    Total number of CNAME records found on this server: 1

    Total number of CNAME records missing on this server:

    0

    Total number of glue (A) records this server could not

    find: 0





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

    DNS server: server01.phoenix.com

    IP Address: 172.16.1.8

    UDP port 53 responding to queries: YES

    TCP port 53 responding to queries: Not tested

    Answering authoritatively for domain: YES

    SOA record data from server:

    Authoritative name server: server01.phoenix.com

    Hostmaster: hostmaster.phoenix.com

    Zone serial number: 32

    Zone expires in: 1.00 day(s)

    Refresh period: 900 seconds

    Retry delay: 600 seconds

    Default (minimum) TTL: 3600 seconds



    Additional authoritative (NS) records from server: server01.phoenix.com
    172.16.1.8







    Alias (CNAME) and glue (A) records for forest GUIDs

    from server:

    CNAME:

    ce44d53d-c8c5-4da4-b474-7b2fdb672a74._msdcs.phoenix.com

    Alias: server01.phoenix.com

    Glue: 172.16.1.8



    Total number of CNAME records found on this server: 1

    Total number of CNAME records missing on this server:

    0

    Total number of glue (A) records this server could not

    find: 0





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

    Notes:

    One or more DNS servers is not authoritative for the

    domain
     
    John West, Dec 6, 2004
    #12
  13. John West

    John West Guest

    Computer Name: SERVER01

    DNS Host Name: server01.phoenix.com

    System info : Windows 2000 Server (Build 3790)

    Processor : x86 Family 15 Model 3 Stepping 4,

    GenuineIntel

    List of installed hotfixes :

    KB819696

    KB823182

    KB823353

    KB823559

    KB824105

    KB824141

    KB825119

    KB828035

    KB828741

    KB833987

    KB834707

    KB835732

    KB837001

    KB839643

    KB839645

    KB840315

    KB840374

    KB840987

    KB841356

    KB841533

    KB867460

    KB873376

    Q147222

    Q828026



    Netcard queries test . . . . . . . : Passed





    Per interface results:

    Adapter : Local Area Connection

    Netcard queries test . . . : Passed

    Host Name. . . . . . . . . : server01

    IP Address . . . . . . . . : 172.16.1.8

    Subnet Mask. . . . . . . . : 255.255.255.0

    Default Gateway. . . . . . : 172.16.1.1

    Dns Servers. . . . . . . . : 172.16.1.8



    AutoConfiguration results. . . . . . : Passed

    Default gateway test . . . : Passed

    NetBT name test. . . . . . : Passed

    [WARNING] At least one of the <00>

    'WorkStation Service', <03> 'Messenger Service', <20>

    'WINS' names is missing.

    WINS service test. . . . . : Skipped

    There are no WINS servers configured for

    this interface.



    Global results:



    Domain membership test . . . . . . : Passed



    NetBT transports test. . . . . . . : Passed

    List of NetBt transports currently configured:


    NetBT_Tcpip_{1B7149B6-77C5-4F02-9B29-4A160A1FD931}

    1 NetBt transport currently configured.



    Autonet address test . . . . . . . : Passed



    IP loopback ping test. . . . . . . : Passed



    Default gateway test . . . . . . . : Passed



    NetBT name test. . . . . . . . . . : Passed

    [WARNING] You don't have a single interface with

    the <00> 'WorkStation Service', <03> 'Messenger

    Service', <20> 'WINS' names defined.



    Winsock test . . . . . . . . . . . : Passed



    DNS test . . . . . . . . . . . . . : Passed

    PASS - All the DNS entries for DC are registered

    on DNS server '172.16.1.8'.



    Redir and Browser test . . . . . . : Passed

    List of NetBt transports currently bound to the

    Redir


    NetBT_Tcpip_{1B7149B6-77C5-4F02-9B29-4A160A1FD931}

    The redir is bound to 1 NetBt transport.

    List of NetBt transports currently bound to the

    browser


    NetBT_Tcpip_{1B7149B6-77C5-4F02-9B29-4A160A1FD931}

    The browser is bound to 1 NetBt transport.



    DC discovery test. . . . . . . . . : Passed



    DC list test . . . . . . . . . . . : Passed



    Trust relationship test. . . . . . : Skipped



    Kerberos test. . . . . . . . . . . : Passed



    LDAP test. . . . . . . . . . . . . : Passed



    Bindings test. . . . . . . . . . . : Passed



    WAN configuration test . . . . . . : Skipped

    No active remote access connections.



    Modem diagnostics test . . . . . . : Passed

    IP Security test . . . . . . . . . : Skipped

    Note: run "netsh ipsec dynamic show /?" for more

    detailed information



    The command completed successfully
     
    John West, Dec 6, 2004
    #13
  14. John West

    Kurt Guest

    Nslookup is failing? What is the failiure?

    ....kurt

    "John West" <> wrote in message
    news:Rv%sd.175790$cJ3.89890@fed1read06...
    > This is from the client side of things I have also changed the ip

    addressing
    > fearing the ip zero subnet thing:> The nslookup thing really bugs me cant
    > figure out why nslookup cant resolve the name in dns?
    >
    >
    >
    > ****************************************************************
    > D:\tools>nltest /dclist:phoenix.com
    > Get list of DCs in domain 'phoenix.com' from '\\server01.phoenix.com'.
    > You don't have access to DsBind to phoenix.com (\\server01.phoenix.com)
    > (Trying
    > NetServerEnum).
    > I_NetGetDCList failed: Status = 6118 0x17e6 ERROR_NO_BROWSER_SERVERS_FOUND
    > *****************************************************************
    > D:\tools>nltest /dcname:phoenix.com
    > NetGetDCName failed: Status = 2453 0x995 NERR_DCNotFound
    > ****************************************************************
    >
    >
    > D:\tools>nltest /dsgetdc:phoenix.com
    > DC: \\server01.phoenix.com
    > Address: \\172.16.1.8
    > Dom Guid: c8876d07-d748-47cc-9dde-9967cb103e46
    > Dom Name: phoenix.com
    > Forest Name: phoenix.com
    > Dc Site Name: Default-First-Site-Name
    > Our Site Name: Default-First-Site-Name
    > Flags: PDC GC DS LDAP KDC TIMESERV GTIMESERV WRITABLE DNS_DC
    > DNS_DOMAIN
    > DNS_FOREST CLOSE_SITE
    > The command completed successfully
    > ***************************************************************
    > D:\>nslookup
    > *** Can't find server name for address 172.16.1.8: Non-existent domain
    > *************************************************************
    >
    >
    >
    >
    >
    >
    >
    >
    > "Neil" <guess!!!@gmail.com> wrote in message
    > news:Xns95B76AF0EAFC6neilmcsegmailcom@207.46.248.16...
    > > did you hear Neil <guess!!!@gmail.com> say in
    > > news:Xns95B76A162E789neilmcsegmailcom@207.46.248.16:
    > >
    > >> dnslint /ad /s /v server01.pheonix.com

    > >
    > > feh, sorry, use the IP addy of server01 instead...
    > >
    > > --
    > > Neil MCNGP #30
    > > "Human beings, who are almost unique in having the ability to
    > > learn from the experience of others, are also remarkable for
    > > their apparent disinclination to do so."
    > > -- a quote by Doug Adams (Author of the Hitchhiker's Guide to the

    Galaxy)
    >
    >
     
    Kurt, Dec 6, 2004
    #14
  15. John West

    Kurt Guest

    Is the DHCP server also the DNS server and DC? If so, is it pointing to
    itself for DNS? (is it it's own DNS server?). Since I'm sure you're already
    way past that (can't hurt to ask, though),
    Could you post the folowing:

    DC IP address
    DNS Server IP Address
    DHCP Server IP Address

    Output of "ipconfig /all" from each
    Output of "ipconfig /all" from one of the XP boxes that is not working

    Output of "route print" from one of the XP Boxes that is not working

    ....kurt

    "John West" <> wrote in message
    news:CLQsd.175752$cJ3.79434@fed1read06...
    > I ran the test earlier and the only issue that failed was a test

    concerning
    > DHCP not being able to find AD, really nothing as I am not using DHCP on
    > this box. I guess i should disable the service :> But then again if DHCP
    > cant find AD I wonder if DNS has the same issue? This box is runing an
    > evualation copy not a full vesion but that should not make a difference.
    >
    > As for clients, all of them seem to have the same issue. As for the DHCP,
    > AD-integrated DNS, yes this is what I am running. As for the Scavenge

    check
    > I only have two current computers on this network to resolve this issue,

    at
    > one point I had many but reduced to two computers now no possible way I
    > could have dup IP addresses.
    >
    > What other logs or tests can I run for you guys?
    >
    > A phone call on this would be great and anyone who can fix this gets a

    quick
    > 50 via paypall or check from me. I have been working on this issue for

    the
    > past 6 weeks off and on what a drag, but I am learning a lot!
    >
    >
    > Any thoughts?
    >
    > Thanks
    >
    > John
    >
    >
    > "beoweolf" <> wrote in message
    > news:2CGsd.54774$...
    > > Did you try running DCdiag /fix...on the server?
    > >
    > > What is your server DNS configuration? As requested in another message,

    is
    > > the client the only one with the problem or is this more general, wide
    > > spread? Are you running DHCP, AD-integrated DNS, have your run Scavenge?
    > > checked for duplicate IP addresses?
    > >
    > >
    > >
    > > "John West" <> wrote in message
    > > news:n35sd.174868$cJ3.155850@fed1read06...
    > >> Gang,
    > >>
    > >> I have been working on trying to connect an XP workstation to a win

    2003
    > >> server and seem to be having some DNS issues. The error message below

    is
    > >> from the XP workstation when I try to configure the client XP

    workstation
    > >> to the domain phoenix.com.
    > >>
    > >> All computers have the latest and greatest patches and I can ping via
    > >> name and ip address to the server from the client and from the server

    to
    > >> the client via ip address. Also when I do an ns lookup on the server

    it
    > >> comes back with server01.phoenix.com, also on the workstation has the
    > >> same nslookup response
    > >>
    > >> Server 172.16.0.2 /24
    > >> Workstation 172.16.0.5 /24
    > >> Server name Server
    > >> Domain=Phoenix.com
    > >>
    > >> Not sure if what other infor you will need.
    > >>
    > >> ***************************************************************
    > >> 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
    > >> D:\WINDOWS\debug\dcdiag.txt.
    > >>
    > >> DNS was successfully queried for the service location (SRV) resource
    > >> record used to locate a domain controller for domain Phoenix.com:
    > >>
    > >> The query was for the SRV record for _ldap._tcp.dc._msdcs.Phoenix.com
    > >>
    > >> The following domain controllers were identified by the query:
    > >>
    > >> server01.phoenix.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.
    > >>
    > >> ***********************************************
    > >>

    > >
    > >

    >
    >
     
    Kurt, Dec 6, 2004
    #15
  16. John West

    ptwilliams Guest

    NSLOOKUP is failing because you do not have a reverse-
    lookup zone. This, in itself, will not stop AD from
    working. But for piece of mind and troubleshooting I
    always recommend a Reverse lookup Zone. To simplify
    administration, use a subnet that encompasses all of your
    network. For example, if you have four class-c nets,
    create a class-b reverse zone.

    --

    Going back to another point you made, do not disable the
    DHCP client service on the DC. Netlogon uses the DHCP
    client service to dynamically register the SRV records
    (every 12 hours by default, but you'll be hard-pressed to
    find this documented). If it's not running, you won't
    register SRV records.

    Perform the following on the DC:

    -- Set DHCP service to automatic and start
    -- Ensure that the DC is pointing to it's own IP for DNS
    -- Ensure the DNS zone accepts dynamic updates
    -- Stop netlogon
    -- Start netlogon
    -- For good measure, type ipconfig /registerdns too ;-)


    Also ensure that the workstations are configured to point
    to the internal DNS server.

    Once this is done, install the support tools on one of the
    clients and type nltest /dsgetdc:domain-name.com. If the
    dsGetDc call succeeds, then the IP-DNS locator should be
    able to get enough info to work. Logoff and Logon again.

    --

    Check that both DNS servers are listed in the Name Servers
    tab -if they're not, add the appropriate servers. The
    Name Servers tab is what defines the NS record and
    therefore which servers are authorative for the domain.


    --

    Paul Williams

    http://www.msresource.net/
    http://forums.msresource.net/


    >-----Original Message-----
    >This is from the client side of things I have also

    changed the ip addressing
    >fearing the ip zero subnet thing:> The nslookup thing

    really bugs me cant
    >figure out why nslookup cant resolve the name in dns?
    >
    >
    >
    >**********************************************************

    ******
    >D:\tools>nltest /dclist:phoenix.com
    >Get list of DCs in domain 'phoenix.com'

    from '\\server01.phoenix.com'.
    >You don't have access to DsBind to phoenix.com

    (\\server01.phoenix.com)
    >(Trying
    >NetServerEnum).
    >I_NetGetDCList failed: Status = 6118 0x17e6

    ERROR_NO_BROWSER_SERVERS_FOUND
    >**********************************************************

    *******
    >D:\tools>nltest /dcname:phoenix.com
    >NetGetDCName failed: Status = 2453 0x995 NERR_DCNotFound
    >**********************************************************

    ******
    >
    >
    >D:\tools>nltest /dsgetdc:phoenix.com
    > DC: \\server01.phoenix.com
    > Address: \\172.16.1.8
    > Dom Guid: c8876d07-d748-47cc-9dde-9967cb103e46
    > Dom Name: phoenix.com
    > Forest Name: phoenix.com
    > Dc Site Name: Default-First-Site-Name
    >Our Site Name: Default-First-Site-Name
    > Flags: PDC GC DS LDAP KDC TIMESERV GTIMESERV

    WRITABLE DNS_DC
    >DNS_DOMAIN
    >DNS_FOREST CLOSE_SITE
    >The command completed successfully
    >**********************************************************

    *****
    >D:\>nslookup
    >*** Can't find server name for address 172.16.1.8: Non-

    existent domain
    >**********************************************************

    ***
    >
    >
    >
    >
    >
    >
    >
    >
    >"Neil" <guess!!!@gmail.com> wrote in message
    >news:Xns95B76AF0EAFC6neilmcsegmailcom@207.46.248.16...
    >> did you hear Neil <guess!!!@gmail.com> say in
    >> news:Xns95B76A162E789neilmcsegmailcom@207.46.248.16:
    >>
    >>> dnslint /ad /s /v server01.pheonix.com

    >>
    >> feh, sorry, use the IP addy of server01 instead...
    >>
    >> --
    >> Neil MCNGP #30
    >> "Human beings, who are almost unique in having the

    ability to
    >> learn from the experience of others, are also

    remarkable for
    >> their apparent disinclination to do so."
    >> -- a quote by Doug Adams (Author of the Hitchhiker's

    Guide to the Galaxy)
    >
    >
    >.
    >
     
    ptwilliams, Dec 7, 2004
    #16
    1. Advertising

Want to reply to this thread or ask your own question?

It takes just 2 minutes to sign up (and it's free!). Just click the sign up button to choose a username and then you can ask your own questions on the forum.
Similar Threads
  1. Rafael
    Replies:
    1
    Views:
    3,318
  2. Lars Bonnesen
    Replies:
    9
    Views:
    7,416
    chris
    Apr 8, 2006
  3. none
    Replies:
    5
    Views:
    3,251
  4. Johnny
    Replies:
    11
    Views:
    3,154
    Cerebrus
    Aug 4, 2006
  5. zillah
    Replies:
    0
    Views:
    746
    zillah
    Nov 9, 2006
Loading...

Share This Page