C
cksj
Our parent company owns two companies. These companies are using
applications developed by the IT dept of the parent company. Each company
has 1 SQL Server and for simplicity sake both companies named their server
"zeus". A few years later, the parent company decided to merge these two
companies together. The network admin guys, installed Active Directory and
created a root domain and two child domains. Each child domain is for each
company. Now that we're all in the same domain, we get a lot of 4319 errors
(duplicate name on the network).
Is our only solution to rename one of the servers? In our applications, can
we qualify the servers with child domain name to avoid confusion?
Thanks for any ideas!
applications developed by the IT dept of the parent company. Each company
has 1 SQL Server and for simplicity sake both companies named their server
"zeus". A few years later, the parent company decided to merge these two
companies together. The network admin guys, installed Active Directory and
created a root domain and two child domains. Each child domain is for each
company. Now that we're all in the same domain, we get a lot of 4319 errors
(duplicate name on the network).
Is our only solution to rename one of the servers? In our applications, can
we qualify the servers with child domain name to avoid confusion?
Thanks for any ideas!