we are changing (correcting) IP address range in our AD domain. We currently have all Servers and PC’s in the range 142.1.10.xxx,2552552550 (yes I know!!) so I’m moving everything to a new address range of 10.0.0.xxx 2552552480 (ie 10.0.0-7.xxx) (all internal of course)
I have added say 10.0.0.7 as a secondary IP address on AD server(2003sp2) (so it still has 126.96.36.199 as the primary IP for the sake of all the other clients for now!) and my PC is 10.0.0.1(XPprosp3)….. I can ping 10.0.0.7 fine, and server can ping 10.0.0.1 fine.. but can’t join the domain (a domain controller for the domain ABC could not be contacted) I have reverse entries in the AD’s DNS for each range eg:10.0.0, 10.0.1, 10.0.2 and so on.
What else needs to be done before AD will accept my PC to it’s domain?
IF I change my pc to 188.8.131.52, and DNS to 184.108.40.206, allows me to join no probs, DNS 220.127.116.11 and PC 18.104.22.168 as secondary IP – no go.
seems that AD will only allow a PC to join if on the 142.1.10.xxx network and only if it’s a primary address. intend dropping 142.1.10.xxx off all together once everyone is over..
Don’t want to change the AD server to 10.0.0.7 as the primary address just yet for fear of breaking usage? if I do this for testing overnight? can I change it back without AD issues following it?
any perls of wisdom would help..
You must be logged in to reply to this topic.
Create a free account today to participate in forum conversations, comment on posts and more.