Solved

Domain Migration

Posted on 2007-11-21
9
291 Views
Last Modified: 2012-05-05
I have two Active Directory domains running on 2003 servers.

olddomain.org is on top floor of the building and the newdomain.org is on the bottom floor. I want to get rid of the olddomain and have already migrated all computers in that floor to authenticate to the new domain. Now everyone is added and authenticating to the new domain controller. However when i tried to shutdown the server that has the old AD., top floor users cannot access internet. They can logon (to the new domain) and even talk to fileservers internally. But for internet access, the old beast needs to be powered back on.  

Seems to me like a DNS issue. Any ideas?? Internet access is only through one cisco 2801 router.

0
Comment
Question by:rdvarghese
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
9 Comments
 
LVL 6

Assisted Solution

by:mickeyfan
mickeyfan earned 100 total points
ID: 20332781
It sounds like your dhcp setting for dns are still pointing to the old server. Try ipconfig / release, ipconfig /renew then ipconfig /flushdns.
0
 
LVL 7

Assisted Solution

by:mcse2007
mcse2007 earned 100 total points
ID: 20332789
your client default gateway should point to your internet router.

0
 
LVL 7

Accepted Solution

by:
djMundy earned 200 total points
ID: 20332832
Hi rdvarghese,

Check the DNS config on the PCs, maybe they are configured manually (even if the IP address is being assigned by DHCP). Also check the proxy setting in IE - is the old server running ISA?

Cheers,
Daniel
0
Free learning courses: Active Directory Deep Dive

Get a firm grasp on your IT environment when you learn Active Directory best practices with Veeam! Watch all, or choose any amount, of this three-part webinar series to improve your skills. From the basics to virtualization and backup, we got you covered.

 

Author Comment

by:rdvarghese
ID: 20333107
DNS on clients are automatic, so is the IP address. DHCP is good too.

still same problem !!
0
 
LVL 7

Expert Comment

by:djMundy
ID: 20336711
Try pinging an IP address when the old server is turned off - if this works you definitely have a DNS issue.

1. Ping google.com before turning off the old server - record the IP address it displays.
2. Turn off the old server.
3. Now try pinging google.com - it should fail?
4. Now try pinging the IP address you recorded in step 1 - does it work?

Cheers,
Daniel
0
 

Assisted Solution

by:oxburger
oxburger earned 100 total points
ID: 20337240
If none of the above provides a solution:  Do not just "shutdown" a domain controller...especially if it was the first one installed in a domain or forest (because the first domain controller installed with hold all the FSMO roles).  Rather, transfer FSMO roles to the new domain cotroller(s) and  demote the "old" domain controller using DCPROMO and then take it out of the domain or forest.

Does your Cisco router do any kind of filtering or does it let anyone access the internet?

HTH!
0
 
LVL 7

Expert Comment

by:djMundy
ID: 20337260
As oxburger says when you finally do want to remove the old domain controller (after you've sorted out these issues regarding Internet access) you'll want to transfer roles and demote it properly. There's a very good guide for this here: http://www.msresource.net/content/view/61/47/

Cheers,
Daniel
0
 

Author Comment

by:rdvarghese
ID: 20341869
Question:- Isnt the DHCP Server, the one that assigns clients default gateway??
i will look at the DHCP settings (on Monday) and i am guessing most likely the DHCP server might have set the clients to point to the Old DC as the default gateway. If this doesnt work, then probably its Cisco Router.

when the OLD DC was shutdown, i could ping the new DC by name - but anything outside like yahoo or google wasnt successful. !!

Happy Thanksgiving !
0
 
LVL 7

Expert Comment

by:djMundy
ID: 20346912
Usually the default gateway is set to the CISCO but the DNS server is set to the DC - so that you can resolve internal and external names.

You're right that the default gateway is set by DHCP, but it's the DNS server that will stop you from resolving names. Did you try pinging Google via IP address with the old server shut down? That will help determine whether it's the gateway or DNS that is having problems.

Cheers,
Daniel
0

Featured Post

Is Your AD Toolbox Looking More Like a Toybox?

Managing Active Directory can get complicated.  Often, the native tools for managing AD are just not up to the task.  The largest Active Directory installations in the world have relied on one tool to manage their day-to-day administration tasks: Hyena. Start your trial today.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

In this article, I am going to show you how to simulate a multi-site Lab environment on a single Hyper-V host. I use this method successfully in my own lab to simulate three fully routed global AD Sites on a Windows 10 Hyper-V host.
This article shows the method of using the Resultant Set of Policy Tool to locate Group Policy that applies a particular setting.
This Micro Tutorial hows how you can integrate  Mac OSX to a Windows Active Directory Domain. Apple has made it easy to allow users to bind their macs to a windows domain with relative ease. The following video show how to bind OSX Mavericks to …
Are you ready to implement Active Directory best practices without reading 300+ pages? You're in luck. In this webinar hosted by Skyport Systems, you gain insight into Microsoft's latest comprehensive guide, with tips on the best and easiest way…

726 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question