Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations IamaSherpa on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Moving Server to Home 1

Status
Not open for further replies.

vich

Technical User
Sep 26, 2000
107
US
I have a Windows 2003 r2 server that has been in my small business that I am moving to my house. I don't know if this is too complicated to resolve over the forum but I would appreciate a try.

My dilema is the server was acting as a DHCP andDNS and Active directory. My Uverse router also provides DHCP.

How can I turn off the DHCP on the server to prevent it from assigning addresses. Do I need to turn anything else off; DNS, etc?

I also had it set up as a VPN but that is not needed for now.

Thanks
 
Look on this page - easy to do to turn off dhcp.


The computers at home don't care if the server is set to run DNS UNLESS they are pointing to the server for their DNS. If you leave the computers and home router as-is, they will continue to point to the UVerse router for their DNS and DHCP.

Turn off the DHCP on the server first while it's unplugged from the home network. Then reboot it and plug it into the home network.

The active directory shouldn't really matter if you don't join the home computers to the domain, though I don't if you were going to do that or not as you didn't provide nearly enough information, such as:

1. Why you wanted to move it.
2. Final goal (configuration) of moving it/having it home

Next time, try to kill us with as much info as you can. Less is less and more is more in this case.
 
Thanks goombawaho. I am not sure how I didn't see you post so quickly.

I kept messing around and did what you said. Turned off DHCP and DNS on the server and everything seems to be working.

Sorry for the lack of info. Interesting most of the computers at home I had set with the same domain name. Who know's what's really happening but things seem to be working. Haven't rebooted all systems.

I brought hte server home because we are shutting down the business we owned and it has all of our system and accounting data. So I wanted to keep it operational in the event I needed to access the info and to close out the books.

I was running a VPN through the other network port but did not connect it to anything nor have a need currently to VPN into the system.

The ultimate goal is to have the system available at home and have some of the computers at home access it (which are) and still have all the computers at home access printers either on the network or as previously shared by a computer that was already at home.

Thanks for the quick response.
 
Interesting most of the computers at home I had set with the same domain name.

This is confusing to me. You don't SET the domain name, you join a domain. If the PCs from the business are the same ones that you brought home, they would still be part of the domain. If these are your home PCs, you need to join the domain IF you want them part of it.

I don't see how the PCs that were at home could be part of the domain when the server was at the business, unless via the VPN you mentioned.
 
maybe the home PCs were in a workgroup that just happened to have the same name as the domain?

-------------------------------

If it doesn't leak oil it must be empty!!
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top