http://support.microsoft.c
Could be the RSS (Receive side scaling) issue that is hitting a number of users currently.
Keith
Main Topics
Browse All TopicsCustomer moved SBS box, reconfigured new IP settings (single network, just changed to a new network).
Now Exchange, Sharepoint and some other services fail to load with 1722 "The RPC server is unavailable" whenever the NIC is enabled (Intel Pro/1000 integrated into a Dell 600SC). Group Policy fails to process with "unable to determine user or computer name".
Oddly, setting the server and domain name to point to 127.0.0.1 in the hosts file or disabling the NIC solves the situation.
Rebooting with the modified hosts file, or the NIC disabled allows exchange to run and group policy to process, etc.
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
http://support.microsoft.c
Could be the RSS (Receive side scaling) issue that is hitting a number of users currently.
Keith
I changed the IP address manually, then ran CEICW. Going back and trying to run the change IP address wizard fails on IIS.
I don't think skipping the wizard is the root of the issue here though. These RPC errors go down to Active Directory, and I know AD doesn't take any special wizard to handle IP address changes.
>>"I don't think skipping the wizard is the root of the issue here though."
Perhaps not, but I have had to rebuild SBS's from scratch before, after doing so. You end up trying to repair by manually changing Sharepoint configs, IIS, RRAS, Firewall, etc.
Fair enough. I formated the array, installed from disc, installed relevant SP's and restored from backup. Now IIS is running, the Change IP address wizard runs without error, and everything seems peachy except Exchange won't start and just like before I'm getting RPC errors.
OK - wasn't sure if you had ISA installed or rras configured.
Presumably there are no rogue entries remaining in the dns, AD or wins databases? No local hosts files etc that were restored from the old system? CEICW configures the systems well but doesn't take out exisiting records that may be conflicting anywhere.
Anthing from dcdiag etc?
ipconfig looks fine. DCDIAG speaks for itself.
Do you want to run the additional tests listed here?
http://technet2.microsoft.
I've run DCDIAG every which way, all the errors point to RPC Server unavailable.
RPC is not listening on the public interface. I've tried with two differnet network cards, reinstalled TCP/IP and restored from bare metal, but something in the system state is screwing up RPC. AFAIK, The server worked fine until I restored.
Is there an actual loopback adapter installed in "Network Connections"? Not referring to the 127.0.0.1 address but an actual "device". This would not normally be used, but can be added. If present it may be taking priority.
Also check the binding order in Network connections, on the menu bar under advanced | Advanced settings | adapters and bindings.
Just grasping at straws <G>.
No loopback adapter and the physical NIC is bound first.
Microsoft Support fixed the issue, it took two layers of techs and about 3 hours, but the end result was this.
Apparently the RPC key in the registry was modified to change the adapter RPC binds to, but I'm not sure how or why and neither does Microsoft so far.I have no idea how this key could have changed suddenly on a working server, or what exactly that entry did.
Deleting HKEY_LOCAL_MACHINE\SYSTEM\
The removed key is here.
Very odd. Wonder if a NIC driver update could have made some changes. Good call to get in touch with MS, doubt we would have isolated that here.
Thanks you for posting your findings glennpratt. Always good to know, and may help someone else in the future.
Glad to hear your problem is resolved.
Cheers !
--Rob
Business Accounts
Answer for Membership
by: RobWillPosted on 2007-12-17 at 04:36:42ID: 20484283
How did they "reconfigured new IP settings "?
With SBS this MUST be done with the wizards, if not you will break services such as Sharepoint".
To change the server IP use the "Change Server IP" Wizard located in the Server Management Console" under Internet and E-mail, and then run the CEICW (Configure E-mail and Internet Connection Wizard), located on the same page and labeled "Connect to the Internet".