• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Active Directory browsing+subnets

Rogue

Banned
We recently migrated to Active Directory on a very large network (6000+ hosts, 300+ Class C subnets) and now when we try to browse Network Neighborhood from any of our clients (Win2k or WinXP), they only see machines on the same subnet (Class C). The server techs are saying it's a networking problem (I'm the network manager) but I insist that they didn't setup AD correctly. We could browse every single PC on our old NT4 domain just fine and we haven't changed anything on the network.

Could someone tell me what direction I should point them in to resolve this issue? I searched on support.microsoft.com for assistance but found little. I'm not sure I'm using the correct keywords though, but usually I am pretty good about finding fixes there or using Google. Can anyone assist?
 
It's not a network issue, it's most likely a DNS issue. AD uses DNS for service location, if DNS isn't perfect AD will have all kinds of strange problems.
 
Can you hit the pcs on the other subnet(s) via. the UNC path?

I agree with Nothingman's observation, at this point it sounds like a DNS issue.
 
Your DNS on the PDC are out of snyc with the BDC, which causes the AD to have problems routing through the OCP. I hope that makes everything ABC.



nevermind me, I'm just bored.
 
Back
Top