\\domainname.com\SYSVOL\ is not browseable

Discussion in 'DNS Server' started by David Lewis, Dec 21, 2004.

  1. David Lewis

    David Lewis Guest

    Having a problem with GPO. The error is saying that I cannot browse \\domainname.com\SYSVOL\
    but the \\netbiosname\SYSVOL\ is browsable. On the 2003 DC both are browseable with windows exployer.
    On my XP client both are browseable. But on a mix of 2000 and XP clients \\domainname.com\SYSVOL\ is not browseable.
    I'm not sure if its a dns issue as the server and some workstations work. All workstations are using dhcp to get the
    same dns settings.
     
    David Lewis, Dec 21, 2004
    #1
    1. Advertisements

  2. In
    Does DHCP assign only the internal DNS?

    --
    Best regards,
    Kevin D4 Dad Goodknecht Sr. [MVP]
    Hope This Helps
    ===================================
    When responding to posts, please "Reply to Group"
    via your newsreader so that others may learn and
    benefit from your issue, to respond directly to
    me remove the nospam. from my email address.
    ===================================
    http://www.lonestaramerica.com/
    ===================================
    Use Outlook Express?... Get OE_Quotefix:
    It will strip signature out and more
    http://home.in.tum.de/~jain/software/oe-quotefix/
    ===================================
    Keep a back up of your OE settings and folders
    with OEBackup:
    http://www.oehelp.com/OEBackup/Default.aspx
    ===================================
     
    Kevin D. Goodknecht Sr. [MVP], Dec 21, 2004
    #2
    1. Advertisements

  3. David Lewis

    David Lewis Guest

    In DHCP under scope options > 006 DNS Servers 192.168.0.3, 151.164.1.8

    I just fried my computer today and setup a new workstation with a new xp os.
    It got a dynamic ip from the dhcp and it was able to browse \\domainname.com right
    out of the box. Whats wrong with all my other workstations?


    "Kevin D. Goodknecht Sr. [MVP]" <>
    |>In |>David Lewis <> commented
    |>Then Kevin replied below:
    |>> Having a problem with GPO. The error is saying that I
    |>> cannot browse \\domainname.com\SYSVOL\
    |>> but the \\netbiosname\SYSVOL\ is browsable. On the 2003
    |>> DC both are browseable with windows exployer.
    |>> On my XP client both are browseable. But on a mix of
    |>> 2000 and XP clients \\domainname.com\SYSVOL\ is not
    |>> browseable.
    |>> I'm not sure if its a dns issue as the server and some
    |>> workstations work. All workstations are using dhcp to
    |>> get the
    |>> same dns settings.
    |>
    |>Does DHCP assign only the internal DNS?
     
    David Lewis, Dec 22, 2004
    #3
  4. You are getting inconsistencies because you are giving your workstations
    your ISP's DNS server address: 151.164.1.8. When they attempt to browse,
    some of them are asking this server, and it has no idea what the name
    resolves to.

    Here's a repost of something I've offered others explaining why one cannot
    use an ISP's DNS, especially if you have AD... I hope it helps out to
    understand the intricacies and the reliance of DNS for AD.

    =============================
    Actually, with an AD network, all domain members (DCs, clients and servers),
    need only use your internal DNS server(s) only. Reason why, is AD stores
    it's resources and service locations in DNS in the form of SRV records
    (those folders with the underscore in them). They are used for a multitude
    of things, such as finding the domain when a client logons, domain
    replication from one DC to another, authentication, and more. To illustrate,
    if a client queried the external DNS server with a query such as, "Where is
    my domain", will that server have the answer? NO.

    That's also the reason why it's resolving your external address.

    Recommendation: Point all machines only to the internal servers, and
    configure a forwarder to your ISP's DNS. This way all machines query your
    DNS and if it doesn;'t have the answer, it asks outside. If the forwarding
    option is grayed out, delete the root zone, (it looks like a period),
    refresh the console, and try again. If not sure how to configure this, this
    article will guide you thru it:
    http://support.microsoft.com/?id=300202

    _________________________
    AD & DNS:
    If you have your ISP's DNS addresses in your IP configuration (DCs and
    clients), they need to be REMOVED. This is what is
    causing the whole problem.

    Just a little background: AD uses DNS. DNS stores AD's resource and service
    locations in the form of SRV records, hence how everything that is part of
    the domain will find resources in the domain. If the ISP's DNS is configured
    in the any of the internal AD member machines' IP properties, (including all
    client machines and DCs), the machines will be asking the ISP's DNS 'where
    is the domain controller for my domain?", whenever it needs to perform a
    function, (such as a logon request, replication request, querying and
    applying GPOs, etc). Unfortunately, the ISP's DNS does not have that info.

    If this is the current scenario, it is highly suggested and recommended to
    only use the internal DNS servers on the network that is hosting the AD zone
    name. This applies to all machines, (DCs and clients). Believe me, Internet
    resolution will still work with the use of the Root hints (as long as the
    root zone doesn't exist).

    If there are multiple DNS entries on a machine (whether a DC, member server
    or client), it will ask the first entry first. If it doesn't have the
    answer, it will go to the second entry, but it REMOVES the first entry from
    the eligible resolvers list, and won't go back to it. THis can cause issues
    within AD when accessing a resource such as a printer, folder, getting GPOs
    to function, etc. Another good reason to ONLY use the internal DNS server.

    However, for more effcient Internet resolution, it's HIGHLY recommended to
    configure a forwarder. If the forwarding option is grayed out, delete the
    Root zone (looks like a period). If not sure how to preform these two tasks,
    please follow one of the two articles listed below, depending on your
    operating system. They show a step by step on how to perform these tasks:

    323380 - HOW TO Configure DNS for Internet Access in Windows Server 2003 :
    http://support.microsoft.com/?id=323380

    300202 - HOW TO Configure DNS for Internet Access in Windows Server 2000 :
    http://support.microsoft.com/?id=300202


    Some additional reading that may help:

    825036 - Best practices for DNS client settings in Windows 2000 Server and
    in Windows Server 2003:
    http://support.microsoft.com/default.aspx?scid=kb;en-us;825036

    DNS and AD (Windows 2000 & 2003) FAQ:
    http://support.microsoft.com/?id=291382

    Domain Controller's Domain Name System Suffix Does Not Match Domain Name:
    http://support.microsoft.com/?id=257623

    Clients cannot dynamically register DNS records in a single-label forward
    lookup zone:
    http://support.microsoft.com/?id=826743

    __________________________

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

    --
    Regards,
    Ace

    G O E A G L E S !!!
    Please direct all replies ONLY to the Microsoft public newsgroups
    so all can benefit.

    This posting is provided "AS-IS" with no warranties or guarantees
    and confers no rights.

    Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSE+I, MCT, MVP
    Microsoft Windows MVP - Windows Server - Directory Services

    Security Is Like An Onion, It Has Layers
    HAM AND EGGS: A day's work for a chicken;
    A lifetime commitment for a pig.
     
    Ace Fekay [MVP], Dec 22, 2004
    #4
  5. In
    You must remove SBC's DNS from your TCP/IP configuration, you can use it as
    a forwarder, do not use it in TCP/IP properties, in any position. SBC's DNS
    has no way of knowing the IP address for any of your internal servers or
    clients.



    --
    Best regards,
    Kevin D4 Dad Goodknecht Sr. [MVP]
    Hope This Helps
    ===================================
    When responding to posts, please "Reply to Group"
    via your newsreader so that others may learn and
    benefit from your issue, to respond directly to
    me remove the nospam. from my email address.
    ===================================
    http://www.lonestaramerica.com/
    ===================================
    Use Outlook Express?... Get OE_Quotefix:
    It will strip signature out and more
    http://home.in.tum.de/~jain/software/oe-quotefix/
    ===================================
    Keep a back up of your OE settings and folders
    with OEBackup:
    http://www.oehelp.com/OEBackup/Default.aspx
    ===================================
     
    Kevin D. Goodknecht Sr. [MVP], Dec 22, 2004
    #5
  6. David Lewis

    David Lewis Guest

    ok so if I remove SBC's dns how does my workstations browse the net if my DNS server goes down?

    "Kevin D. Goodknecht Sr. [MVP]" <>
    |>In |>David Lewis <> commented
    |>Then Kevin replied below:
    |>> In DHCP under scope options > 006 DNS Servers
    |>> 192.168.0.3, 151.164.1.8
    |>>
    |>> I just fried my computer today and setup a new
    |>> workstation with a new xp os.
    |>> It got a dynamic ip from the dhcp and it was able to
    |>> browse \\domainname.com right
    |>> out of the box. Whats wrong with all my other
    |>> workstations?
    |>
    |>You must remove SBC's DNS from your TCP/IP configuration, you can use it as
    |>a forwarder, do not use it in TCP/IP properties, in any position. SBC's DNS
    |>has no way of knowing the IP address for any of your internal servers or
    |>clients.
     
    David Lewis, Dec 24, 2004
    #6
  7. David Lewis

    David Lewis Guest

    I removed SBC's dns from my server. Renewed my workstations ip address and flushed the dns for good measure.
    I still get the error.

    Windows cannot find '\\domain.com' Check the spelling and try again, or.......

    C:\>ipconfig /all

    Windows IP Configuration

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

    Ethernet adapter Local Area Connection:

    Connection-specific DNS Suffix . : mydomain.com
    Description . . . . . . . . . . . : Intel(R) PRO/100 VE Network Connection
    Physical Address. . . . . . . . . : 00-11-11-02-BD-A0
    Dhcp Enabled. . . . . . . . . . . : Yes
    Autoconfiguration Enabled . . . . : Yes
    IP Address. . . . . . . . . . . . : 192.168.0.87
    Subnet Mask . . . . . . . . . . . : 255.255.255.0
    Default Gateway . . . . . . . . . : 192.168.0.1
    DHCP Server . . . . . . . . . . . : 192.168.0.3
    DNS Servers . . . . . . . . . . . : 192.168.0.3
    Primary WINS Server . . . . . . . : 192.168.0.3
    Lease Obtained. . . . . . . . . . : Thursday, December 23, 2004 4:15:08PM
    Lease Expires . . . . . . . . . . : Friday, December 24, 2004 4:15:08 PM



    C:\>ping mydomain.com

    Pinging mydomain.com [192.168.0.3] with 32 bytes of data:

    Reply from 192.168.0.3: bytes=32 time<1ms TTL=128
    Reply from 192.168.0.3: bytes=32 time<1ms TTL=128






    "Ace Fekay [MVP]" <PleaseSubstituteMyActualFirstName&>
    |>
    |>|>> In DHCP under scope options > 006 DNS Servers 192.168.0.3, 151.164.1.8
    |>>
    |>> I just fried my computer today and setup a new workstation with a new xp
    |>> os.
    |>> It got a dynamic ip from the dhcp and it was able to browse
    |>> \\domainname.com right
    |>> out of the box. Whats wrong with all my other workstations?
    |>
    |>You are getting inconsistencies because you are giving your workstations
    |>your ISP's DNS server address: 151.164.1.8. When they attempt to browse,
    |>some of them are asking this server, and it has no idea what the name
    |>resolves to.
    |>
    |>Here's a repost of something I've offered others explaining why one cannot
    |>use an ISP's DNS, especially if you have AD... I hope it helps out to
    |>understand the intricacies and the reliance of DNS for AD.
    |>
    |>=============================
    |>Actually, with an AD network, all domain members (DCs, clients and servers),
    |>need only use your internal DNS server(s) only. Reason why, is AD stores
    |>it's resources and service locations in DNS in the form of SRV records
    |>(those folders with the underscore in them). They are used for a multitude
    |>of things, such as finding the domain when a client logons, domain
    |>replication from one DC to another, authentication, and more. To illustrate,
    |>if a client queried the external DNS server with a query such as, "Where is
    |>my domain", will that server have the answer? NO.
    |>
    |>That's also the reason why it's resolving your external address.
    |>
    |>Recommendation: Point all machines only to the internal servers, and
    |>configure a forwarder to your ISP's DNS. This way all machines query your
    |>DNS and if it doesn;'t have the answer, it asks outside. If the forwarding
    |>option is grayed out, delete the root zone, (it looks like a period),
    |>refresh the console, and try again. If not sure how to configure this, this
    |>article will guide you thru it:
    |>http://support.microsoft.com/?id=300202
    |>
    |>_________________________
    |>AD & DNS:
    |>If you have your ISP's DNS addresses in your IP configuration (DCs and
    |>clients), they need to be REMOVED. This is what is
    |>causing the whole problem.
    |>
    |>Just a little background: AD uses DNS. DNS stores AD's resource and service
    |>locations in the form of SRV records, hence how everything that is part of
    |>the domain will find resources in the domain. If the ISP's DNS is configured
    |>in the any of the internal AD member machines' IP properties, (including all
    |>client machines and DCs), the machines will be asking the ISP's DNS 'where
    |>is the domain controller for my domain?", whenever it needs to perform a
    |>function, (such as a logon request, replication request, querying and
    |>applying GPOs, etc). Unfortunately, the ISP's DNS does not have that info.
    |>
    |>If this is the current scenario, it is highly suggested and recommended to
    |>only use the internal DNS servers on the network that is hosting the AD zone
    |>name. This applies to all machines, (DCs and clients). Believe me, Internet
    |>resolution will still work with the use of the Root hints (as long as the
    |>root zone doesn't exist).
    |>
    |>If there are multiple DNS entries on a machine (whether a DC, member server
    |>or client), it will ask the first entry first. If it doesn't have the
    |>answer, it will go to the second entry, but it REMOVES the first entry from
    |>the eligible resolvers list, and won't go back to it. THis can cause issues
    |>within AD when accessing a resource such as a printer, folder, getting GPOs
    |>to function, etc. Another good reason to ONLY use the internal DNS server.
    |>
    |>However, for more effcient Internet resolution, it's HIGHLY recommended to
    |>configure a forwarder. If the forwarding option is grayed out, delete the
    |>Root zone (looks like a period). If not sure how to preform these two tasks,
    |>please follow one of the two articles listed below, depending on your
    |>operating system. They show a step by step on how to perform these tasks:
    |>
    |>323380 - HOW TO Configure DNS for Internet Access in Windows Server 2003 :
    |>http://support.microsoft.com/?id=323380
    |>
    |>300202 - HOW TO Configure DNS for Internet Access in Windows Server 2000 :
    |>http://support.microsoft.com/?id=300202
    |>
    |>
    |>Some additional reading that may help:
    |>
    |>825036 - Best practices for DNS client settings in Windows 2000 Server and
    |>in Windows Server 2003:
    |>http://support.microsoft.com/default.aspx?scid=kb;en-us;825036
    |>
    |>DNS and AD (Windows 2000 & 2003) FAQ:
    |>http://support.microsoft.com/?id=291382
    |>
    |>Domain Controller's Domain Name System Suffix Does Not Match Domain Name:
    |>http://support.microsoft.com/?id=257623
    |>
    |>Clients cannot dynamically register DNS records in a single-label forward
    |>lookup zone:
    |>http://support.microsoft.com/?id=826743
    |>
    |>__________________________
    |>
    |>---------------------------
    |>
    |>--
    |>Regards,
    |>Ace
    |>
    |>G O E A G L E S !!!
    |>Please direct all replies ONLY to the Microsoft public newsgroups
    |>so all can benefit.
    |>
    |>This posting is provided "AS-IS" with no warranties or guarantees
    |>and confers no rights.
    |>
    |>Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSE+I, MCT, MVP
    |>Microsoft Windows MVP - Windows Server - Directory Services
    |>
    |>Security Is Like An Onion, It Has Layers
    |>HAM AND EGGS: A day's work for a chicken;
    |>A lifetime commitment for a pig.
     
    David Lewis, Dec 24, 2004
    #7
  8. In
    If your DNS server goes down, believe me, browsing the net will be the least
    of your problems. If your DNS goes down within 10 minutes you will not be
    able to authenticate with the DC and your workstations will be so slow
    you'll know you have a problem. The DNS service rarely fails because it uses
    so little of your system resources.



    --
    Best regards,
    Kevin D4 Dad Goodknecht Sr. [MVP]
    Hope This Helps
    ===================================
    When responding to posts, please "Reply to Group"
    via your newsreader so that others may learn and
    benefit from your issue, to respond directly to
    me remove the nospam. from my email address.
    ===================================
    http://www.lonestaramerica.com/
    ===================================
    Use Outlook Express?... Get OE_Quotefix:
    It will strip signature out and more
    http://home.in.tum.de/~jain/software/oe-quotefix/
    ===================================
    Keep a back up of your OE settings and folders
    with OEBackup:
    http://www.oehelp.com/OEBackup/Default.aspx
    ===================================
     
    Kevin D. Goodknecht Sr. [MVP], Dec 24, 2004
    #8
  9. In
    Before we go farther here just verify, \\domain.com will not be accessible
    just to make sure you are using the DFS share \\domain.com\sysvol



    --
    Best regards,
    Kevin D4 Dad Goodknecht Sr. [MVP]
    Hope This Helps
    ===================================
    When responding to posts, please "Reply to Group"
    via your newsreader so that others may learn and
    benefit from your issue, to respond directly to
    me remove the nospam. from my email address.
    ===================================
    http://www.lonestaramerica.com/
    ===================================
    Use Outlook Express?... Get OE_Quotefix:
    It will strip signature out and more
    http://home.in.tum.de/~jain/software/oe-quotefix/
    ===================================
    Keep a back up of your OE settings and folders
    with OEBackup:
    http://www.oehelp.com/OEBackup/Default.aspx
    ===================================
     
    Kevin D. Goodknecht Sr. [MVP], Dec 24, 2004
    #9
  10. David Lewis

    David Lewis Guest

    true but the users need something to do, so I figure I'd give them internet access.
    This has happened in the past. The one server in a 10 man office goes down and
    everyone wants to surf while I fix it.

    "Kevin D. Goodknecht Sr. [MVP]" <>
    |>In |>David Lewis <> commented
    |>Then Kevin replied below:
    |>> ok so if I remove SBC's dns how does my workstations
    |>> browse the net if my DNS server goes down?
    |>
    |>If your DNS server goes down, believe me, browsing the net will be the least
    |>of your problems. If your DNS goes down within 10 minutes you will not be
    |>able to authenticate with the DC and your workstations will be so slow
    |>you'll know you have a problem. The DNS service rarely fails because it uses
    |>so little of your system resources.
     
    David Lewis, Dec 24, 2004
    #10
  11. In David Lewis <> made a post then I commented below
    :: ok so if I remove SBC's dns how does my workstations browse the net
    :: if my DNS server goes down?

    By default the DNS server will use Root Hints. You can make it more
    efficient by configuring a forwarder. My previous post explains exactly how
    to do this.

    Ace
     
    Ace Fekay [MVP], Dec 24, 2004
    #11
  12. In David Lewis <> made a post then I commented below
    :: true but the users need something to do, so I figure I'd give them
    :: internet access. This has happened in the past. The one server in a
    :: 10 man office goes down and everyone wants to surf while I fix it.

    Sounds like compromising AD functionality for Internet surfing. AD
    malfunctions using an external DNS.

    Ace
     
    Ace Fekay [MVP], Dec 24, 2004
    #12
  13. In David Lewis <> made a post then I commented below
    :: I removed SBC's dns from my server. Renewed my workstations ip
    :: address and flushed the dns for good measure. I still get the error.
    ::
    :: Windows cannot find '\\domain.com' Check the spelling and try
    :: again, or.......

    Well, I get the same thing on my machines: \\domain.com is not accessible,
    asking me if the syntax and name is correct. That's just a design
    limitation, unless you are using DFS.

    However, it should work by using \\domain.com\sysvol or \\domain\sysvol. but
    I don't think you want your users to connect to that share.

    Are you using DFS?

    Ace
     
    Ace Fekay [MVP], Dec 24, 2004
    #13
  14. David Lewis

    David Lewis Guest

    thankx, I deleted the ISP's dns and still the issue remains
    On an effected workstation

    --------------------------------------------------------------------------------------------
    C:\>net view \\domain.com
    System error 53 has occurred.

    The network path was not found.
    --------------------------------------------------------------------------------------------

    On my work station that works

    C:\>net view \\domain.com
    Shared resources at \\domain.com

    Domain

    Share name Type Used as Comment

    ---------------------------------------------------
    HP_LJ5000 Print B/W Laser Printer

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

    Both machines are winxp sp2
    Both dhcp

    Subnet Mask . . . . . . . . . . . : 255.255.255.0
    Default Gateway . . . . . . . . . : 192.168.0.1
    DHCP Server . . . . . . . . . . . : 192.168.0.3
    DNS Servers . . . . . . . . . . . : 192.168.0.3
    Primary WINS Server . . . . . . . : 192.168.0.3


    net view \\192.168.0.3 does work on the problem workstation.

    C:\>DIR \\domain.COM\SYSVOL
    The network location cannot be reached. For information about network troublesho
    oting, see Windows Help.


    "Ace Fekay [MVP]" <PleaseSubstituteMyActualFirstName&>
    |>
    |>|>> In DHCP under scope options > 006 DNS Servers 192.168.0.3, 151.164.1.8
    |>>
    |>> I just fried my computer today and setup a new workstation with a new xp
    |>> os.
    |>> It got a dynamic ip from the dhcp and it was able to browse
    |>> \\domainname.com right
    |>> out of the box. Whats wrong with all my other workstations?
    |>
    |>You are getting inconsistencies because you are giving your workstations
    |>your ISP's DNS server address: 151.164.1.8. When they attempt to browse,
    |>some of them are asking this server, and it has no idea what the name
    |>resolves to.
    |>
    |>Here's a repost of something I've offered others explaining why one cannot
    |>use an ISP's DNS, especially if you have AD... I hope it helps out to
    |>understand the intricacies and the reliance of DNS for AD.
    |>
    |>=============================
    |>Actually, with an AD network, all domain members (DCs, clients and servers),
    |>need only use your internal DNS server(s) only. Reason why, is AD stores
    |>it's resources and service locations in DNS in the form of SRV records
    |>(those folders with the underscore in them). They are used for a multitude
    |>of things, such as finding the domain when a client logons, domain
    |>replication from one DC to another, authentication, and more. To illustrate,
    |>if a client queried the external DNS server with a query such as, "Where is
    |>my domain", will that server have the answer? NO.
    |>
    |>That's also the reason why it's resolving your external address.
    |>
    |>Recommendation: Point all machines only to the internal servers, and
    |>configure a forwarder to your ISP's DNS. This way all machines query your
    |>DNS and if it doesn;'t have the answer, it asks outside. If the forwarding
    |>option is grayed out, delete the root zone, (it looks like a period),
    |>refresh the console, and try again. If not sure how to configure this, this
    |>article will guide you thru it:
    |>http://support.microsoft.com/?id=300202
    |>
    |>_________________________
    |>AD & DNS:
    |>If you have your ISP's DNS addresses in your IP configuration (DCs and
    |>clients), they need to be REMOVED. This is what is
    |>causing the whole problem.
    |>
    |>Just a little background: AD uses DNS. DNS stores AD's resource and service
    |>locations in the form of SRV records, hence how everything that is part of
    |>the domain will find resources in the domain. If the ISP's DNS is configured
    |>in the any of the internal AD member machines' IP properties, (including all
    |>client machines and DCs), the machines will be asking the ISP's DNS 'where
    |>is the domain controller for my domain?", whenever it needs to perform a
    |>function, (such as a logon request, replication request, querying and
    |>applying GPOs, etc). Unfortunately, the ISP's DNS does not have that info.
    |>
    |>If this is the current scenario, it is highly suggested and recommended to
    |>only use the internal DNS servers on the network that is hosting the AD zone
    |>name. This applies to all machines, (DCs and clients). Believe me, Internet
    |>resolution will still work with the use of the Root hints (as long as the
    |>root zone doesn't exist).
    |>
    |>If there are multiple DNS entries on a machine (whether a DC, member server
    |>or client), it will ask the first entry first. If it doesn't have the
    |>answer, it will go to the second entry, but it REMOVES the first entry from
    |>the eligible resolvers list, and won't go back to it. THis can cause issues
    |>within AD when accessing a resource such as a printer, folder, getting GPOs
    |>to function, etc. Another good reason to ONLY use the internal DNS server.
    |>
    |>However, for more effcient Internet resolution, it's HIGHLY recommended to
    |>configure a forwarder. If the forwarding option is grayed out, delete the
    |>Root zone (looks like a period). If not sure how to preform these two tasks,
    |>please follow one of the two articles listed below, depending on your
    |>operating system. They show a step by step on how to perform these tasks:
    |>
    |>323380 - HOW TO Configure DNS for Internet Access in Windows Server 2003 :
    |>http://support.microsoft.com/?id=323380
    |>
    |>300202 - HOW TO Configure DNS for Internet Access in Windows Server 2000 :
    |>http://support.microsoft.com/?id=300202
    |>
    |>
    |>Some additional reading that may help:
    |>
    |>825036 - Best practices for DNS client settings in Windows 2000 Server and
    |>in Windows Server 2003:
    |>http://support.microsoft.com/default.aspx?scid=kb;en-us;825036
    |>
    |>DNS and AD (Windows 2000 & 2003) FAQ:
    |>http://support.microsoft.com/?id=291382
    |>
    |>Domain Controller's Domain Name System Suffix Does Not Match Domain Name:
    |>http://support.microsoft.com/?id=257623
    |>
    |>Clients cannot dynamically register DNS records in a single-label forward
    |>lookup zone:
    |>http://support.microsoft.com/?id=826743
    |>
    |>__________________________
    |>
    |>---------------------------
    |>
    |>--
    |>Regards,
    |>Ace
    |>
    |>G O E A G L E S !!!
    |>Please direct all replies ONLY to the Microsoft public newsgroups
    |>so all can benefit.
    |>
    |>This posting is provided "AS-IS" with no warranties or guarantees
    |>and confers no rights.
    |>
    |>Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSE+I, MCT, MVP
    |>Microsoft Windows MVP - Windows Server - Directory Services
    |>
    |>Security Is Like An Onion, It Has Layers
    |>HAM AND EGGS: A day's work for a chicken;
    |>A lifetime commitment for a pig.
     
    David Lewis, Jan 3, 2005
    #14
  15. In

    Some XP member clients have exhibited this behavior, below are some of the
    articles that cover this.

    Try these:
    Group policies are not applied the way you expect; Event ID 1058 and Event
    ID 1030 errors in the application log:
    http://support.microsoft.com/default.aspx?scid=kb;en-us;314494

    You experience a delay when you use your Windows XP computer to log on to a
    domain or to connect to a network resource:
    http://support.microsoft.com/default.aspx?scid=kb;en-us;832161

    Connectivity Delay with Multiple Redirectors Installed:
    http://support.microsoft.com/default.aspx?scid=kb;en-us;171386


    --
    Best regards,
    Kevin D4 Dad Goodknecht Sr. [MVP]
    Hope This Helps
    ===================================
    When responding to posts, please "Reply to Group"
    via your newsreader so that others may learn and
    benefit from your issue, to respond directly to
    me remove the nospam. from my email address.
    ===================================
    http://www.lonestaramerica.com/
    ===================================
    Use Outlook Express?... Get OE_Quotefix:
    It will strip signature out and more
    http://home.in.tum.de/~jain/software/oe-quotefix/
    ===================================
    Keep a back up of your OE settings and folders
    with OEBackup:
    http://www.oehelp.com/OEBackup/Default.aspx
    ===================================
     
    Kevin D. Goodknecht Sr. [MVP], Jan 3, 2005
    #15
  16. In Kevin D. Goodknecht Sr. [MVP] <> made a post then I
    commented below

    :: Some XP member clients have exhibited this behavior, below are some
    :: of the articles that cover this.
    ::
    :: Try these:
    :: Group policies are not applied the way you expect; Event ID 1058 and
    :: Event ID 1030 errors in the application log:
    :: http://support.microsoft.com/default.aspx?scid=kb;en-us;314494
    ::
    :: You experience a delay when you use your Windows XP computer to log
    :: on to a domain or to connect to a network resource:
    :: http://support.microsoft.com/default.aspx?scid=kb;en-us;832161
    ::
    :: Connectivity Delay with Multiple Redirectors Installed:
    :: http://support.microsoft.com/default.aspx?scid=kb;en-us;171386


    I'm starting to think it's DFS related as well (as per article 314494).

    Ace
     
    Ace Fekay [MVP], Jan 4, 2005
    #16
  17. David Lewis

    David Lewis Guest

    ok my machine is a new xp installation and I have an older xp laptop
    Both work when browsing \\domain.com
    and neither have the DisableDFS registry entry as suggested

    1. Click Start, and then click Run.
    2. In the Open box, type regedt32, and then click OK.
    3. In the Registry Editor window, locate the following registry key:
    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Mup
    4. In the right details pane, double-click DisableDFS.

    The DFS client is turned off if the value in the Value data box is 1.
    The DFS client is turned on if the value in the Value data box is 0.
    5. In the Edit DWORD Value dialog box that appears, type 0 in the Value data box, and then click OK.


    On a workstation that cannot browse \\domain.com I had to manually add the DisableDFS
    as a type REG_DWORD and a Decimal value of 0.
    I rebooted the machine. Actually I did this last week and it still cannot browse \\domain.com.

    Any more sugestions?


    "Ace Fekay [MVP]" <PleaseSubstituteMyActualFirstName&>
    |>I'm starting to think it's DFS related as well (as per article 314494).
     
    David Lewis, Jan 4, 2005
    #17
  18. In David Lewis <> made a post then I commented below
    :: ok my machine is a new xp installation and I have an older xp laptop
    :: Both work when browsing \\domain.com
    :: and neither have the DisableDFS registry entry as suggested
    ::
    :: 1. Click Start, and then click Run.
    :: 2. In the Open box, type regedt32, and then click OK.
    :: 3. In the Registry Editor window, locate the following registry key:
    :: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Mup
    :: 4. In the right details pane, double-click DisableDFS.
    ::
    :: The DFS client is turned off if the value in the Value data box is 1.
    :: The DFS client is turned on if the value in the Value data box is 0.
    :: 5. In the Edit DWORD Value dialog box that appears, type 0 in the
    :: Value data box, and then click OK.
    ::
    ::
    :: On a workstation that cannot browse \\domain.com I had to manually
    :: add the DisableDFS
    :: as a type REG_DWORD and a Decimal value of 0.
    :: I rebooted the machine. Actually I did this last week and it still
    :: cannot browse \\domain.com.
    ::
    :: Any more sugestions?


    Running dry here. It doesn't work on mine, as I mentioned before, and I
    don't have the firewall on.

    Does it work by IP?

    Check the local security policies on both machines. I'm actually thinking
    if:
    "Microsoft network client: Digitally sign communications (alway)" is enabled
    Compare the two. There are a couple others as well. Ensure none of the
    "always" ones are enabled. Remember what you changed in case you have to
    change it back.

    Ace
     
    Ace Fekay [MVP], Jan 5, 2005
    #18
  19. David Lewis

    David Lewis Guest

    yes \\192.168.0.3\sysvol does browse.

    pinging domain.com returns 192.168.0.3

    Not sure what you mean about the digitally sign communications.
    All my machines I just image them, boot them, give them a new name and start using them.
    Just default as it comes from microsoft network settings with ip via my dhcp server.

    "Ace Fekay [MVP]" <PleaseSubstituteMyActualFirstName&>
    |>Running dry here. It doesn't work on mine, as I mentioned before, and I
    |>don't have the firewall on.
    |>
    |>Does it work by IP?
    |>
    |>Check the local security policies on both machines. I'm actually thinking
    |>if:
    |>"Microsoft network client: Digitally sign communications (alway)" is enabled
    |>Compare the two. There are a couple others as well. Ensure none of the
    |>"always" ones are enabled. Remember what you changed in case you have to
    |>change it back.
     
    David Lewis, Jan 7, 2005
    #19
  20. In David Lewis <> made a post then I commented below
    :: yes \\192.168.0.3\sysvol does browse.
    ::
    :: pinging domain.com returns 192.168.0.3
    ::
    :: Not sure what you mean about the digitally sign communications.
    :: All my machines I just image them, boot them, give them a new name
    :: and start using them. Just default as it comes from microsoft
    :: network settings with ip via my dhcp server.

    You are imaging them? Are you using Sysprep prior to imaging, or are they
    all identical SIDs?

    Ace
     
    Ace Fekay [MVP], Jan 7, 2005
    #20
    1. Advertisements

Ask a Question

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

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.