'Domain' is not accessible error. Can't browse network

Discussion in 'Windows Server' started by Victoria Bolton, Sep 28, 2006.

  1. We have 3 Windows 2003 Servers.

    1) PDC - Domain controller, DNS server, DHCP and Wins server.
    3Gig Xeon Processor, 1gig Memory, 2 Nics.

    2) Exchange Server
    Same hardware as above

    3) FileServer - MS Sql.
    3 Gig Xeon, 2 gig memory, 2 nics.

    All 3 servers have had all MS updates applied.

    The 70ish workstations are a mix of WinXp, Win2k and 1 NT4 machine.

    Also on the network is our old NT4 Domain controller and Fileserver. It is
    still up as we haven't quite finished transferring all apps and files over
    to the new domain. We have a trust set up between the 2 domains thats seems
    to work for the most part.

    On any workstation that is a member of the new domain (local.4jdc.com)
    cannot browse the domain from with network neighborhood. We get a message
    that says "Local is not accessible. The list of servers for this workgroup
    is not currently available." I have seen another message in the past that
    says something akin to You do not have permission to browse. I can't
    immediately say where I have seen that though.

    The one 2k workstation we have left that is still a member of the old JDC
    domain can browse the LOCAL domain just fine.

    My 3 servers can also browse the LOCAL domain just fine but a Win2k Server
    that I have cannot.

    To test out some theories we shut down the old domain servers for about week
    or so but it made no difference.

    If you type in a computer name from any workstation it accesses them just
    fine so we can map drives etc without any problem but it is causing me
    issues with our McAfee Protection Pilot server which tries to scan the
    domain for new machines that join. Since it can't it it is not doing it's
    job very well.

    We have another problem which I don't know if is connected or not. Our DNS
    server is very slow to respond. At first we thought our internet connection
    was just very slow but on talking to the techs there were started playing
    around with some things to try and find the problem. It turns out if you put
    our ISP's DNS server addresses into a machine the internet is lightning fast
    so we know it's not our ISP. Our DNS server is setup to forward all unknown
    domain requests to our ISP's DNS servers.

    I am a programmer who got dropped into Network administration so please bear
    with me.
     
    Victoria Bolton, Sep 28, 2006
    #1
    1. Advertisements

  2. It turns out if you put
    Make sure all your AD clients point to your DNS server and make sure the DNS
    server is pointed to itself for DNS in the properties of TCP/IP.


    hth
    DDS W 2k MVP MCSE
     
    Danny Sanders, Sep 28, 2006
    #2
    1. Advertisements

  3. Running IPConfig on any workstation shows the correct DNS addresses
    Looking on the DNS server it is pointed to it's own static IP addresses.
    Should it be 127.0.0.1 instead?
     
    Victoria Bolton, Sep 28, 2006
    #3
  4. Running IPConfig on any workstation shows the correct DNS addresses
    Do not set it to 127.0.0.1.

    Make sure it has created the SRV records in the DNS zone it houses.
    See:
    http://support.microsoft.com/kb/816587/en-us

    If so, on the client run ipconfig /flushdns then check access.


    hth
    DDS
     
    Danny Sanders, Sep 28, 2006
    #4
  5. Under Forward Lookup Zones I have two folders:
    _msdcs.local.4jdc.com
    &
    local.4jdc.com

    The KB artical said to look at:
    Forward Lookup
    Zones/Domain_Name/_msdcs/dc/_sites/Default-First-Site-Name/_tcp
    &
    Forward Lookup Zones/Domain_Name/_msdcs/dc/_tcp

    however under
    Forward Lookup Zones/Domain_Name/_msdcs (which has an icon showing a grey
    folder with a note in front)
    there is one record that says Name: (Same as parent folder) Type: Name
    Server Data: pdc.loca.4jdc.com

    I can find the _kerberos and _ldap records under:
    Forward Lookup
    Zones/_msdcs.local.4jdc.com/dc/_sites/Default-First-Site-Name/_tcp

    There is no dc folder under local.4jdc.com but there is a _sites folder
    which I can find the two srv records under.
    I did this as well, it had no effect on the network browsing. Internet
    doesn't seem to be any different either, it's not been too bad this morning
    though. My collegue said he has tried this command in the past and it didn't
    make any difference.
     
    Victoria Bolton, Sep 28, 2006
    #5
    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.