RPC Server is unavailable

WOW!  Where do I begin?

I have an Exchange 2003 Server running on Windows 2003 Server member server.  It was running very good, however, I noticed an error showing up my event viewer about the Browser service.  I have two Network cards, and one is disabled and one of the posts about fixing the browser error mentioned that having two network cards (one disabled) could cause this error, so I did the fix.  It mentioned removing all of the components for the disabled NIC.  I went to the properties for the disabled NIC and removed TCP/IP, Client for Microsoft Networks, and Network Load Balance.  I did that and then the server prompted me to reboot, so I did.  I first noticed a problem about 5 minutes later, when I tried to remote desktop to it.  I got the username and password screen on Remote Desktop, and when I put them in, I got a "RPC Server is unavailable" error message.  I went to the Exchange Server and tried to logon to the computer and was not able to log on to the domain, I could only log on locally (on the Exchange Server).  When I did logon locally, I found several errors in the event viewer.  Here are only some of them (other mentioned that certain services of Exchange could not start, etc):

Event Type:      Error
Event Source:      Userenv
Event Category:      None
Event ID:      1053
Date:            10/4/2004
Time:            11:44:14 AM
User:            NT AUTHORITY\SYSTEM
Computer:      EMAIL
Description:
Windows cannot determine the user or computer name. (Access is denied. ). Group
Policy processing aborted.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.


Event Type:      Warning
Event Source:      LSASRV
Event Category:      SPNEGO (Negotiator)
Event ID:      40960
Date:            10/4/2004
Time:            10:59:18 AM
User:            N/A
Computer:      EMAIL
Description:
The Security System detected an authentication error for the server
cifs/lakeside-server.meadeauto.local.  The failure code from authentication
protocol Kerberos was "The attempted logon is invalid. This is either due to a
bad username or authentication information.
 (0xc000006d)".

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 6d 00 00 c0               m..À    



Event Type:      Warning
Event Source:      LSASRV
Event Category:      SPNEGO (Negotiator)
Event ID:      40961
Date:            10/4/2004
Time:            10:59:18 AM
User:            N/A
Computer:      EMAIL
Description:
The Security System could not establish a secured connection with the server
cifs/lakeside-server.meadeauto.local.  No authentication protocol was
available.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 6d 00 00 c0               m..À    


Event Type:      Information
Event Source:      DnsApi
Event Category:      None
Event ID:      11160
Date:            10/4/2004
Time:            9:45:10 AM
User:            N/A
Computer:      EMAIL
Description:
The system failed to register pointer (PTR) resource records (RRs) for network
adapter
with settings:

   Adapter Name : {3525DCB6-BDF0-439A-8CAE-A26AF1AE674A}
   Host Name : email
   Adapter-specific Domain Suffix : meadeauto.local
   DNS server list :
           192.168.25.51, 192.168.17.51
   Sent update to server : 192.168.25.51
   IP Address : 192.168.25.84

 The reason that the system could not register these RRs was because of a
security related problem. The cause of this could be (a) your computer does not
have permissions to register and update the specific DNS domain name set for
this adapter, or (b) there might have been a problem negotiating valid
credentials with the DNS server during the processing of the update request.

 You can manually retry DNS registration of the network adapter and its
settings by typing "ipconfig /registerdns" at the command prompt. If problems
still persist, contact your DNS server or network systems administrator.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 39 23 00 00               9#..    

I tried to do use NETDOM /RESET or NETDOM /VERIFY on that computer and I get an error saying the RPC Server is unavailable.

I guess this sums up what went wrong, any help would be great.  I don't know if that "fix" for the Browser service error caused this or not.  Maybe something was already messed up on it, and it just needed the reboot to have the "screwed up settings" to take over.  Any help would be fantastic, especially a fix...