BJG Posted October 22, 2008 Posted October 22, 2008 (edited) For some daft reason, someone in the past set up two of our school IT suites (Music and Media Studies) on different physical networks, with their own unique server and domain name. I'm wondering if I'm letting myself in for any problems if I connect them up to the main network by patching the relevant network switches. (These rooms aren't even on the Internet at the moment.) I've been warned that I should disable DHCP on these extra servers in order to stop them spreading IP addresses from their own strange ranges onto the rest of the school, but are there any other nasty side-effects I should be aware of...? (At some point I need to integrate them all properly, but at the moment I'm just looking for a quick fix to register some new music software via the Internet without repatching individual PCs. Everything's Windows Server 2003 / XP clients.) Edited October 22, 2008 by BJG
CHR1S Posted October 22, 2008 Posted October 22, 2008 What domains are they, i.e 2k3, 2000 or NT4 and what will be the primary domain?
CHR1S Posted October 22, 2008 Posted October 22, 2008 In theory it should be a case of removing the DHCP from the servers, adding them to the main domain as member servers, connecting them up and if they are all on the same subnet swapping the domains on the PCs to the primary. In practice its a little more difficult but it gives you the jist of what you have to do.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now