dfs and dns issues question.

  • Thread starter Thread starter Bill B
  • Start date Start date
B

Bill B

I have a DFS root set up in my envrionment, the environment is 1 domain, 2
subnets. I only have 2 dcs, both on the 1st subnet. Systems on the first
subnet can map the dfs root, see it, etc. But systems on the second cannot.
systems on the second subnet can get to / see all other domain
resources/shares/etc, including the shares that make up the dfs root, they
just cant map/see the root- they dont know it exists.

Any suggestions? I am thinking it might be because my dns isnt AD integrated
at the moment. But am looking for suggestions.


Thanks
 
Its a small private network. Dns servers are root. (with . zone) They do not
connect to the internet, and are the end of the line. the subnet i cannot
open the dfs root from has no dc.

I would think it was a dns issue, but for the fact that everything else that
depends on dns works fine from the systems on the "problem" subnet.
Additionally all systems on the second subnet are pointing to dns servers on
the first subnet. Im pretty confident dns is configured correctly...

any other suggestions...

thanks..

bill
 
In
Bill B said:
Its a small private network. Dns servers are root. (with . zone) They
do not connect to the internet, and are the end of the line. the
subnet i cannot open the dfs root from has no dc.

I would think it was a dns issue, but for the fact that everything
else that depends on dns works fine from the systems on the "problem"
subnet. Additionally all systems on the second subnet are pointing to
dns servers on the first subnet. Im pretty confident dns is
configured correctly...

any other suggestions...

thanks..

bill


"Ace Fekay [MVP]"
Click to expand...

Hmm, it sounds like your DNS is configured properly, from first glance. But
depending on the link speed between the subnets (if it's in a remote
location), that can be a contributing factor. Number of clients, link speed
and traffic shaping would dictate the requirement for a DC that is
configured to be a GC. Usualy the magic number is if you have more than 10
clients or the link speed is just too slow.

One question, how are the folks in the other subnet trying to get to the
Root?
This should work using DNS: \\domain.com\share, which shouldn't be a prob in
your scenario.

If using \\domain\share, then that requires WINS or LMHOSTS files on the
clients, since this is the NetBIOS connectivity method and NetBIOS does not
cross routers.

The only other thing I can say is to ensure the latest service pack is
installed. I'm also posting some links for DFS. Hopefully they'll help out.

Deploy DFS:
http://www.microsoft.com/technet/treeview/default.asp?url=/technet/prodtechn
ol/windows2000serv/deploy/walkthru/dfsguide.asp

Distributed File System (DFS) - Best Practices and Troubleshooting Guide:
http://www.microsoft.com/technet/treeview/default.asp?url=/technet/prodtechn
ol/windows2000serv/support/dfsbp.asp

Error Message Failed to Enumerate Volumes in Dfs... (Q177509):
http://support.microsoft.com/support/kb/articles/Q177/5/09.asp

How to Configure Dfs to Use Fully Qualified Domain Names in Referrals
(Q244380):
http://support.microsoft.com/support/kb/articles/Q244/3/80.asp

How to Map Root Using Microsoft Dfs (Q178631):
http://support.microsoft.com/support/kb/articles/Q178/6/31.asp

How to Troubleshoot the File Replication Service and the Distributed File
System (Q272279):
http://support.microsoft.com/support/kb/articles/Q272/2/79.asp

--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory
 
Back
Top