Windows Server TechCenter > Windows Server Forums > General > Unable to browse share in a sub domain
Ask a questionAsk a question
 

AnswerUnable to browse share in a sub domain

  • Wednesday, November 04, 2009 8:26 AMStrunk Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Hi all,

    Running on a AD based on Windows 2003 R2 servers.

    We have a forest with several sub domains connected through MPLS.
    When running in the Top level domain you are not able to browse for shares in the sub domains. We have enabled NetBios over TCP/IP on the file servers in the sub domain but we are still unable to browse for share.
    If we map a drive direct using the FQDN it works without any issue.

    Does anyone have a clue what could be wrong ?

    /Strunk
    Strunk

Answers

  • Thursday, November 05, 2009 1:09 AMSainath IRP_MJ_CREATEMVP, ModeratorUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     Answer
    Hi Strunk ,

    As mkleij mentioned , broadcasts are not supported across the subnets , so you can use LMHOST file in order perform name resolution across the subnets.

    Prior to using name resolution techniques i would first test if the IPaddress resoluution is happening, and then move to name resolution [wins / DNS ]

All Replies

  • Wednesday, November 04, 2009 9:39 AMmkleij Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    If I remember correctly netbios names are not resolved cross subnets by default. You need to implement something like a wins server to make that possible. Another possibility would be using DNS (single label DNS names). Single label DNS is to proposed successor of netbios.
  • Thursday, November 05, 2009 1:09 AMSainath IRP_MJ_CREATEMVP, ModeratorUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     Answer
    Hi Strunk ,

    As mkleij mentioned , broadcasts are not supported across the subnets , so you can use LMHOST file in order perform name resolution across the subnets.

    Prior to using name resolution techniques i would first test if the IPaddress resoluution is happening, and then move to name resolution [wins / DNS ]

  • Thursday, November 05, 2009 12:49 PMStrunk Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Thanks for your help.
    The LMHOSTS file did the trick.


    Strunk