I have two domains in different cities connected via site to site VPN. I created a Forest wide transitive trust between the two domains and it all seemed to go through fine. But when I go to one of the domains and type a netbios name for a server in the other domain it will not find the machine. I have to type the FQDN i.e. \\myserver.mydomain.llc to be able to browse to the server. This isn't really a big deal for me but we have an Access DB that is extremely old and it references the machine name only. I don't manage the DB and the guy that does says he cannot change the way the reference is without totally rebuilding the synch relationship.
Is this normal behavior for a domain trust or am I missing something really dumb? I am pretty good with AD but I am by know means an AD guru. I only have a couple of clients that have AD and as such I don't deal with it on a daily or weekly basis. If this is not normal what do I need to do to make netbios work properly between the two domains without having to use FQDN's? Thanks for any help anyone is willing to provide.
Michael Mayo IT Support Engineer Soft Designs Inc.
The traditional solution is to add a DNS Suffix for the other domain, for instance using a GPO. But the DNS Global Name Zone will do the trick as well (better, in fact). As will WINS :-)
Make it as simple as you can, but not simpler -- Albert Einstein
Thank you gentleman I think I got it figured out. Now we have to figure out why they can't synchronize the Access 97 DB from one location to the other which did work previously when this person was using a Windows XP machine but it dies and I replaced it with a Win7 Pro machine and now it won't sync the DB? They have full access to the files in the other domain I tested it so who knows I am leaving it to the DB admin guy to figure it out I have done my thing.
Michael Mayo IT Support Engineer Soft Designs Inc.
I thought about mentioning that but shouldn't we avoid disturbing the dead?
Geriatric but not dead I'm afraid. About 50% of the enterprises still seem to have it. Had one funny case last month. I was inspecting their AD and was asked to have a look at WINS. I discovered that it was configured completely wrong: not replicating, and wrong IP addresses. It was not being used at all! At that point we just turned it off :-)
Make it as simple as you can, but not simpler -- Albert Einstein