Exchange 2003 SP2 server is down on a Windows Server 2003 Std Ed R2 SP2 after last night's round of updates. Anything that uses RPC fails with messages in the event log "The endpoint cannot be created." Users cannot connect to Exchange Server with Outlook. Can't manage DNS or DHCP, although they are running and working. These services are running: Remote Procedure Call (RPC) Remote Procedure Call (RPC) Locator However, a check of "netstat -an" shows that the RPC endpoint mapper is only listening on UDP, not on TCP (port 135). On my Vista machine, which has not yet received the updates, the endpoint mapper is listening on both TCP and UDP. Using portqry.exe, the endpoint mapper responds from the server itself (only on UDP) with a little over 100 entries (nothing related to Exchange). From my Vista machine, portqry to the server, port 135, protocol UDP, produces "RPC query failed (6e4)." I am using Routing and Remote Access's Basic Firewall (no NAT), and this is a multihomed system, with WAN and LAN adapters. Most ports are blocked on the WAN side but are wide open on the LAN side. I have read these, but they just confirm that the RPC endpoint mapper isn't work as expected: [URL]http://support.microsoft.com/kb/839880/en-us[/URL] [URL]http://support.microsoft.com/kb/310298[/URL] I'm about to uninstall all of the updates, then install each one again to see what caused the problem. Greg Stewart