I am currently having issues changing the IP address with a Exchange 2007 running Win2K8 that is a GC. I am moving it from one site to another and need to change the IP address from 192.168.2.10 to 192.168.0.10. When I change the IP to the 192.168.0.10, Active Directory stops working. I did the same thing with a Win2K8 running AD and also a GC but did not have any IP issues or DNS issues. Any idea why I am getting this with Exchange 2007? The exact error after changing the IP and launching AD is "The directory schema is not accessible because: An invalid directory pathname was passed.

I forgot to mention that after it stops working with the new IP address, I can change it back to the old IP which is 192.168.2.10 and works fine.

I forgot to mention that after it stops working with the new IP address, I can change it back to the old IP which is 192.168.2.10 and works fine. Changing the exchange server's IP is rather easy. Just make sure the dns records are updated properly. RegardsLaeeq Qazi|Team Lead(Exchange + Sharepoint + BES + DynamicsCRM) www.HostingController.com

In addition to what Laeeq wrote: And also don't forget to point the rules and policys in the firewall to the new ipJonas Andersson MCTS: Microsoft Exchange Server 2010, Configuration | MCITP: EMA | MCSE/MCSA Blog: http://www.testlabs.se/blog

Hi Laeeq, I have tried checking the DNS entries to make sure there is a A record host for the new IP (192.168.0.10) and also a Reverse Lookup Zone (2.168.192.in-addr.arpa). I have also tried stopping the netlogon and have done a ipconfig /registerdns but nothing seems to work. Is there something else that I am missing? Thanks in advance for any help. Just seems weird to me that out of 2 servers, 1 server was totally ok with no issues and didn't have to make any DNS changes and the 2nd Server (Exchange) is giving this problem.

Hi Jonas, I have looked into the Windows Firewall with Advance Security section but there is nothing that specifes that Local IP of 192.168.10.2. If anything it just says "Any" Local Address for either Private/Domain/Public. I have tried just shutting of the firewall completely to see if that makes a difference but no. But I think I am missing something else in DNS but can't figure out what.

Hi Jonas, I have looked into the Windows Firewall with Advance Security section but there is nothing that specifes that Local IP of 192.168.10.2. If anything it just says "Any" Local Address for either Private/Domain/Public. I have tried just shutting of the firewall completely to see if that makes a difference but no. But I think I am missing something else in DNS but can't figure out what. I was referring to the corporate firewall :) Jonas Andersson MCTS: Microsoft Exchange Server 2010, Configuration | MCITP: EMA | MCSE/MCSA Blog: http://www.testlabs.se/blog

Thanks for the suggestion Jonas, yes I have made appriopriate changes on the Cisco ASA to reflect the new IP.

What do mean Active Directory stops working? Any errors in the event logs? This doesnt sound lke an Exchange issue.

One of the errors that I see in the DNS log is Event ID 408 The DNS server could not open socket for address 192.168.2.10. Verify that this is a valid IP address for the server computer. If it is NOT valid use the Interfaces dialog under Server Properties in the DNS Manager to remove it from the list of IP interfaces. Then stop and restart the DNS server. (If this was the only IP interface on this machine and the DNS server may not have started as a result of this error. In that case remove the DNS\Parameters\ ListenAddress value in the services section of the registry and restart.) or The DNS server could not bind a Transmission Control Protocol (TCP) socket to address 192.168.2.10. The event data is the error code. An IP address of 0.0.0.0 can indicate a valid "any address" configuration in which all configured IP addresses on the computer are available for use. Restart the DNS server or reboot the computer. or The DNS server could not bind a User Datagram Protocol (UDP) socket to 192.168.2.10. The event data is the error code. Restart the DNS server or reboot your computer

Have you changed the DNS servers this server uses for DNS? Sounds like it was using itself and that ip is no longer valid.

Yes I have changed the IP for DNS to be 192.168.0.10. It is just weird that when I remove the old IP that Active directory does not open up any more. What I mean by AD stops working is that I can no longer access Active Directory Users and Computers but when I put the 192.168.2.10 it opens up right away. I think there is something in either DNS or registry that is referecing the 192.168.2.10 IP Address. It's driving me crazy.

I would go through these 2 articles and make sure you have followed all the steps: http://technet.microsoft.com/en-us/library/cc758579(WS.10).aspx Change the static IP address of a domain controller and http://technet.microsoft.com/en-us/library/cc739015(WS.10).aspx Moving a Domain Controller to a Different Site If it still doesnt work, I would post this question in the Windows Forums as it appears to be a Windows issue and more related to the fact that these server are also DCs http://social.technet.microsoft.com/Forums/en/category/windowsserver

Hi Andy, I have looked at Active Directory Sites and Services but I have never had any subnet IP information before i changed the IP and was working ok. I am starting to think it is maybe something with it being a DC as well.

On Sat, 22 May 2010 17:34:00 +0000, Manny Ramirez wrote: > > >One of the errors that I see in the DNS log is Event ID 408 > > > >The DNS server could not open socket for address 192.168.2.10. Do you have the DNS server configured to listen on ANY IP address or just on 192.168.2.10? If you changed the machine's IP address you also have to change anything that explicitly refers to the old IP address to use the new IP address. --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP

Firstly, did you configure your DNS to bind to a specific IP address? That might explain the error that you get since it can no longer bind to the IP (as it no longer exists). Just check your config and change it to "all available interfaces" and that should resolve your first issue. Secondly, moving an Exchange server between AD sites is not a good idea. The issue comes in with ADSite keyword that is registered within AD that is used for finding the correct CAS server to use when using the Autodiscover, EWS, Proxy etc. If you do want to move between AD sites, I would recommend you uninstall the CAS and HT server roles first (your mail will stop working during the interim) and then reinstall them after the move. If you dont, you will pick up all sorts of funny issues in your Exchang going forward.Casper Pieterse, Principle Consultant - UC, Dimension Data South Africa, Microsoft Certified Master: Exchange 2007

Hi Rich, thanks for replying. I have the DNS configured to list to All IP Addresses which is 192.168.10 and 192.168.2.10. If I remove the old IP Address 192.168.2.10/Subnet/Gateway/DNS nothing will work properly just using the 192.168.0.10 (New IP).

Hi Casper, Yesterday it had gotten to the point to where even the internet stopped working on the Exchange Server after messing around with IP's to much. These are the steps that I took to somewhat resolve a issue. Step 1. I ended up doing a restore backup of the registry and AD from 2 days ago when it had the Ip address of 192.168.2.10 & restarted server. Step 2. I confirmed AD and DNS were working ok. Step 3. I found a article on steps to change and IP on Domain Controllers. Basically the procedure is to not remove the old IP at first until you have the new ip listening and advertising. http://www.totalnetsolutions.net/2007/07/29/how-to-change-a-domain-controller-ip/ Step 4. After following the instructions, I got everything to work except the fact that the server actually needs the old IP address (192.168.2.10) So right now, AD / DNS / Exchange Mail Flow is working on the 192.168.0.10. Would there be any reason as to why the server needs 192.168.2.10 to work when everything is working perfectly on the 192.168.0.10? I really want to remove the old IP but if it works will it hurt me in the future? I have done alot of testing to make sure everything in DNS thru nslookup is working properly, AD and mail is ok. Thanks for everyones help by the way.

Just to clarify, everything is working with 2 IP's but if I remove the old one (192.168.2.10) everything stops working.

On Sun, 23 May 2010 15:06:07 +0000, Manny Ramirez wrote: >Hi Rich, thanks for replying. I have the DNS configured to list to All IP Addresses which is 192.168.10 and 192.168.2.10. If I remove the old IP Address 192.168.2.10/Subnet/Gateway/DNS nothing will work properly just using the 192.168.0.10 (New IP). Okay . . . so rather than starting at the top and working down, how about starting with some basic tests? When the machine has only the new IP address in the IP stack, can you (from the machine itself) ping it on 127.0.0.1 and 192.168.0.10? Can you ping other machines on the 192.168.0.0/24 network? Can other machines on the 192.168.0.0/24 network ping the 192.169.0.10 address? Can machines on the 192.168.2.0/24 network ping 192.168.0.10? Does "route print" show up any "persistant" routes? --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP

When the machine has only the new IP address in the IP stack, can you (from the machine itself) ping it on 127.0.0.1 and 192.168.0.10? Yes Canyou ping other machines on the 192.168.0.0/24 network? Yes Can other machines on the 192.168.0.0/24 network ping the 192.169.0.10 address? I think you mean 192.168.0.10. Yes Can machines on the 192.168.2.0/24 network ping 192.168.0.10? No

On Sun, 23 May 2010 16:05:31 +0000, Manny Ramirez wrote: >When the machine has only the new IP address in the IP stack, can you (from the machine itself) ping it on 127.0.0.1 and 192.168.0.10? Yes >Canyou ping other machines on the 192.168.0.0/24 network? Yes >Can other machines on the 192.168.0.0/24 network ping the 192.169.0.10 address? I think you mean 192.168.0.10. Yes Yes. Either the 8 key is too close to the 9 key or my finger's too wide. :-) >Can machines on the 192.168.2.0/24 network ping 192.168.0.10? No Machines on the same network (192.168.0.0/24) can ping the 192.168.0.10 because they don't have to use any router. Machines NOT in the 192.168.0.0/10 network have to use a router to get to the 192.168.2.0/24 network and the machines on the 192.168.2.0/24 have to use a router to get to the 192.168.0.0/24 network. So, what's missing is the answer to the question I asked before -- when you run "route print" on the 192.168.0.10 machine, are there any "persistant routes"? If there are, what are they? If there are none, what's the default gateway address you use when you change the NIC's IP address to 192.168.0.10? It should be an IP address in the 192.168.0.0/24 network (assuming you're using /24 networks). --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP