General discussion

Locked

IP Change on DC and Exchange

By wroming ·
Ok here is the deal I have everything up and going just fine in my network but we are fixing to be subnetting everything out and Vlaning the network. This is my question, since some of the servers are DC and one is exchange if I change the IP on the servers would that effect the network meaning "Active Directory and/or Exchange 2000" If it does and/or does not if you could provide a KB article to the effect that would be wonderful. If you would like to ask me any direct questions please send them to wroming@ci.killeen.tx.us thanks and look forward to your answer(s)

Also all DC are running 2000 with sp4 and they will all be on the same subnet and vlan after the change just need to know if it would effect the network if the IP's were changed. I will make sure in DNS that the DNS has the correct information.

This conversation is currently closed to new comments.

8 total posts (Page 1 of 1)  
| Thread display: Collapse - | Expand +

All Comments

Collapse -

by CG IT In reply to IP Change on DC and Excha ...

umm I'm gonna be a jerk here and say that if your unsure of what changing IP addressing will do to your network, you shouldn't be mucking with it let alone trying to subnet and VLAN. There aren't Microsoft Help and Support articles dealing with "changing the IP addressing scheme for the network" and what consequences that has in relation to DNS, DHCP, and the lot simply because if your doing it you should know how to do it. There are troubleshooting articles dealing with "ooops damnit" changes that invariably happen [ operator error] but again, if you have to ask what happens when you do change it, you shouldn't be thinking of changing.

Collapse -

by CG IT In reply to

sorry but thats how I feel about it. If you don't know, get some of the MCSA MCSE training books from Microsoft Press and learn TCP/IP, DNS, DHCP, first before mucking around with your network and making the whole thing not work. Especially DNS which if you change your IP addressing scheme and don't properly configure your DNS and DHCP servers your Exchange Server isn't going to work and users will boo you in the hallway, throw paperwads at your, burn effegies of you in the parking lot and you'll end up taking a header off the roof top when you least want to.

Collapse -

by wroming In reply to

Poster rated this answer.

Collapse -

by wroming In reply to IP Change on DC and Excha ...

OK, maybe I need to re address my question. By changing the IP on domain controllers will it have any adverse effects. I really do not need any silly comments this site is designed to assist in helping other techies and to find out what things may happen. I know about Microsoft but, when it gets down to the nitty gritty I am a router switch guy. So please if you do not have something to suggest to assist me please do not answer the question.

Collapse -

by CG IT In reply to IP Change on DC and Excha ...

yes it does if you don't update all your DNS records.

Collapse -

by wroming In reply to

Poster rated this answer.

Collapse -

by wroming In reply to IP Change on DC and Excha ...

OK, naturally I know that the DNS needs to be taken care of otherwise the names will not be able to be resolved correctly. I guess what I am asking is if the DNS is correct for entries will it have any effect on the Exchange and/or DC's

Collapse -

by TechKid In reply to IP Change on DC and Excha ...

Generally DNS is set to dynamic update which means when you change the IP on the DC DNS will get the changes. We re-IP our boxes all the time as we use one site as a staging site and then when the DC is deployed we re-IP it to the correct network.

DNS does not always realize the change immediately. After you change the IP and a reboot is not necessary but will force itself to register it's new IP.

You could also fix up dns manually. Do this by deleting the old host record and then go to the server's command prompt and type IPCONFIG /REGISTERDNS. This will register the new address.

Unauthorize your DHCP server before you change the IP. Once DNS is squared away after the change, re-authorize the dhcp. DHCP is tricky though. If the other servers don't get the change of IP right away dhcp can deauthorize itself because the database gets corrupted. If this happens your dhcp mmc will stop responding. Go to another server, open the dhcp mmc, unauthorize the corrupted dhcp server.

Sorry no KB's, this is all from experience

Back to Windows Forum
8 total posts (Page 1 of 1)  

Related Discussions

Related Forums