Unless there exists a compelling reason to do otherwise, and you are confident the TCP/IP stack requires radical reconfiguration, I'd choose to switch off the server, seize FSMO roles onto another DC and cleanup metadata with ntdsutil, and reinstall from scratch.
On the other hand: do other TCP-based services work? Maybe your new setup is just blocking port 135 or is misrouting? --Steve On Thu, Dec 15, 2011 at 10:09 AM, Maglinger, Paul <[email protected]> wrote: > We upgraded our core switch and switches in a server room and for the > purposes of redundancy set up teaming on the server NICs. Most of the > teaming went well except for one Windows 2003 domain controller, which > happens to be the master for a number of roles (schema, etc.). Now it's > having problems with RPC in that when other servers try to connect we get a > "RPC server is unavailable". The RPC services are running on the DC. > Googling around leads me to believe that the TCP/IP stack may be corrupted > and need to be rebuilt. We have done this before on workstations and > application servers, but never on a DC. We first found Microsoft KB 317518 > which doesn't sound too bad, but more Googling indicates the process is a bit > more complicated on DCs, in that it involves editing the registry (KB > 325356). Has anyone out there done that? How successful was it? Any other > recommendations? > > Thanks, > > Paul ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to [email protected] with the body: unsubscribe ntsysadmin
