Different AD locations "honing" incorrectly?

[irbk]

As I understand it (and I'm not saying that I understand it correctly) by running \\DomainName.com you should see all the shares on the DC in the local location. That way you can have Namespace shares and DFS replication so that a user in, say Atlanta going to \\DomainName.com\Projects is pulling files from the local server in Atlanta while a user in Chicago going to \\DomainName.com\Projects is pulling files from the local server in Chicago.

Now assuming that my previous statement is true, I've got a problem. From most of my DC's, when I run \\DomainName.com it's bringing up a server that's in Madison (rather than the local location, unless your in Madison). Not sure what the heck is going on. Suggestions?

 

[58sniper]

Let's start with the basics. Are your AD Sites and Services defined correctly, including all subnets?

Do you have your Tek-Tips.com Swag? I've got mine!

Stop by the new Tek-Tips group at LinkedIn.

 

[irbk]

Yes.

 

[ShackDaddy]

Instead of trying that from your DC's, try it from workstations instead and see if you get the same results. The same rules may not be applied to DC's since they don't really have a %logonserver% property.

Dave Shackelford
ThirdTier.net
TrainSignal.com