|
server
newsgroups
|
|||||||||||||||||||||||
|
|||||||||||||||||||||||
DNS/DHCP problem while migrating computers using ADMTHi all,
We recently merged with another company and we are trying to merge their users and computers into our forest using the Active Directory Migration Tool. So far the testing has mostly gone smoothly, but I had one problem with my test of migrating a workstation. The source domain uses Active Directory DHCP. The target domain uses a DHCP server on a Cisco router. When I migrated the computer, it continued to get a DHCP address from the source domain's DC, along with the source domain's DNS servers. Therefore it didn't register itself properly with the target domain's DNS servers; the workstation appeared in both domains but was inaccessible from either. We had to manually set the IP, gateway, and DNS. Can anyone give me any advice on how we can handle this problem? Thanks, - Steve Hello Steve,
See my reply to microsoft.public.windows.server.migration and avoid multiposting, use crossposting with a newsreader like outlook express. http://www.blakjak.demon.co.uk/mul_crss.htm Best regards Meinolf Weber Disclaimer: This posting is provided "AS IS" with no warranties, and confers no rights. ** Please do NOT email, only reply to Newsgroups ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm Show quoteHide quote > Hi all, > > We recently merged with another company and we are trying to merge > their users and computers into our forest using the Active Directory > Migration Tool. So far the testing has mostly gone smoothly, but I > had one problem with my test of migrating a workstation. > > The source domain uses Active Directory DHCP. The target domain uses > a DHCP server on a Cisco router. When I migrated the computer, it > continued to get a DHCP address from the source domain's DC, along > with the source domain's DNS servers. Therefore it didn't register > itself properly with the target domain's DNS servers; the workstation > appeared in both domains but was inaccessible from either. We had to > manually set the IP, gateway, and DNS. > > Can anyone give me any advice on how we can handle this problem? > > Thanks, > - Steve Hi Steve
Di you update the IP helpers for the pc's being migrated, as they will still contact the orignial DHCP servers until their IP helper is updated (Cisco), or they are moved to new VLANS pre configured with the correct settings during migration as a secondary task during the admt process Regards -- Show quoteHide quoteGarry Starck MCITP, MCTS AD, MCSE 2003 Messaging, MCDBA "Steve Kadish" wrote: > Hi all, > > We recently merged with another company and we are trying to merge their > users and computers into our forest using the Active Directory Migration > Tool. So far the testing has mostly gone smoothly, but I had one problem > with my test of migrating a workstation. > > The source domain uses Active Directory DHCP. The target domain uses a DHCP > server on a Cisco router. When I migrated the computer, it continued to get > a DHCP address from the source domain's DC, along with the source domain's > DNS servers. Therefore it didn't register itself properly with the target > domain's DNS servers; the workstation appeared in both domains but was > inaccessible from either. We had to manually set the IP, gateway, and DNS. > > Can anyone give me any advice on how we can handle this problem? > > Thanks, > - Steve > Meinolf - my apologies for the multipost. Bad "netiquette" on my part.
Although I believe what you meant to say was "PLEASE avoid multiposting." After all, a little courtesy goes a long way. :-) Thanks for that great link, as well. Nothing like a good throw-back to the days when we all thought animated GIFs on our pages were cool. Garry - thanks for the suggestions. I'm looking at the VLAN option. I inherited some Dell switches with the new company that I don't know much about, and I'm researching to see if they support VLAN trunking. The reason we are using Cisco DHCP instead of MS DHCP is because we don't have Windows servers at every location, and, back in 2003 when we migrated from NT4, I frankly didn't know about the Cisco ip helper commands. So, all we could think of was to have a DHCP server on every subnet, and the Cisco routers were all we had at some sites. Thanks, - Steve Show quoteHide quote "Garry Starck - MCITP" wrote: > Hi Steve > > Di you update the IP helpers for the pc's being migrated, as they will still > contact the orignial DHCP servers until their IP helper is updated (Cisco), > or they are moved to new VLANS pre configured with the correct settings > during migration as a secondary task during the admt process > > Regards > -- > Garry Starck > MCITP, MCTS AD, MCSE 2003 Messaging, MCDBA > > > "Steve Kadish" wrote: > > > Hi all, > > > > We recently merged with another company and we are trying to merge their > > users and computers into our forest using the Active Directory Migration > > Tool. So far the testing has mostly gone smoothly, but I had one problem > > with my test of migrating a workstation. > > > > The source domain uses Active Directory DHCP. The target domain uses a DHCP > > server on a Cisco router. When I migrated the computer, it continued to get > > a DHCP address from the source domain's DC, along with the source domain's > > DNS servers. Therefore it didn't register itself properly with the target > > domain's DNS servers; the workstation appeared in both domains but was > > inaccessible from either. We had to manually set the IP, gateway, and DNS. > > > > Can anyone give me any advice on how we can handle this problem? > > > > Thanks, > > - Steve > > Hi Steve
I take it that you testing so you have probably not updated that IP helpers on the Cisco side, Why not try creating a test VLAN config'd with they correct DHCP servers on the IP helper setting and change the test PC to be migrated to the new VLAN. This will not effect all they other PC's on the same VLAN. Question, why you using Cisco DHCP as opposed the MS DHCP? After all this said, I usually migrated a select amount of pc's during a migrationm phase according to VLANS, the entire range/s. What's the matter if they still on the old IP, just enable DNS forwarding from old Domain to new Domain DNS zones Regards -- Show quoteHide quoteGarry Starck MCITP, MCTS AD, MCSE 2003 Messaging, MCDBA "Steve Kadish" wrote: > Hi all, > > We recently merged with another company and we are trying to merge their > users and computers into our forest using the Active Directory Migration > Tool. So far the testing has mostly gone smoothly, but I had one problem > with my test of migrating a workstation. > > The source domain uses Active Directory DHCP. The target domain uses a DHCP > server on a Cisco router. When I migrated the computer, it continued to get > a DHCP address from the source domain's DC, along with the source domain's > DNS servers. Therefore it didn't register itself properly with the target > domain's DNS servers; the workstation appeared in both domains but was > inaccessible from either. We had to manually set the IP, gateway, and DNS. > > Can anyone give me any advice on how we can handle this problem? > > Thanks, > - Steve > 
Other interesting topics
What am I missing?
Domain Trust issue problem reading gpt.ini Kerberos Tickets Renewal How to Switch domains without having admin rights? Group Domain Admins cannot be found Logon issue in a 2 domain trust - Win 2003 DC fails when isolated from network GPO Version mismatch in Sysvol Folder Redirection Run Amok |
|||||||||||||||||||||||
