exchange will not start after having changed IP of SBS2003 (RPC server is unavailable)
Hi all, SBS2003 with exchange having problems Because of a change in Internet connection (cable vs ADSL) I had to change IP of the network to avoid conflicts with the internal network of the cable modem (trust me, I have dealt with this before). Old net work was 192.168.100.0/24, now I have changed it to 192.168.1.0/24. Exchange picks up incoming mail, but keeps it in the queue, because the Information Store does not start. Exchange services not running: - System Attendant - MTA stacks - Information Store Hve been looking around but have not found a working solution so far. DNS and DHCP seem to work OK, I can ping all servernames available. Someone have another idea? TIA Leen de Braal.
June 3rd, 2011 5:59pm

Did you change the IP address using the wizard, or did you do it manually? Either way, I would suggest that you run the Configure Internet and Email wizard (or whatever it is called). That will sort out a lot of the mess. Simon.Simon Butler, Exchange MVP Blog | Exchange Resources | In the UK? Hire Me.
Free Windows Admin Tool Kit Click here and download it now
June 3rd, 2011 8:59pm

I have been changing manually first. But then I did run the wizard, because that was a thougt crossing my mind too. Did not help. It boils down to the rpc service, when trying to restart Exchange System Attendant, I get this: Event ID 9143 Referral Interface cannot contact any Global Catalog that supports the NSPI Service. Clients making RFR requests will fail to connect until a Global Catalog becomes available again. After a Domain Controller is promoted to a Global Catalog, it must be rebooted to support MAPI Clients. Event ID 9317 Failed to register Service Principal Name for exchangeRFR; error code was c00706ba Event ID 1005 Unexpected error The RPC server is unavailable. Facility: Win32 ID no: c00706ba Microsoft Exchange System Attendant occurred. Event ID 9317 Failed to register Service Principal Name for exchangeMDB; error code was c00706ba. Earlier in the boot sequence I see this: Event ID Windows cannot determine the user or computer name. (The RPC server is unavailable. ). Group Policy processing aborted. I think that this is the cause of all the other troubles, but what to do about it? TIA Leen
June 3rd, 2011 9:20pm

Doing a netdiag test gives me this line: DC list test . . . . . . . . . . . : Failed [WARNING] Cannot call DsBind to my-sbs.mydomain.local (192.168.1.1). [RPC_S_SERVER_UNAVAILABLE] DNS seems to work ok. Other machines in the network can ping this one by name ok.
Free Windows Admin Tool Kit Click here and download it now
June 3rd, 2011 9:36pm

Always something stupidly simple. There was a hosts-file on the server, which had entries to the old IP-addresses. Removing the entries immediately gave me the correct answer when asking setspn -L servername. Starting the exchange services went OK after that. Problem solved, time for a coffee.Leen de Braal
June 4th, 2011 11:35am

Number one reason why I hate hosts files - they are easily forgotten, and then get in the way. Simon.Simon Butler, Exchange MVP Blog | Exchange Resources | In the UK? Hire Me.
Free Windows Admin Tool Kit Click here and download it now
June 4th, 2011 6:33pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics