I couldn't use RDP to connect to a server even though port 3389 was open. After examining the server, edgetransport.exe had that open, not terminal services. I restarted the Edge Transport server and it stopped listening on that port, but so far, I have no explanation as to why it would listen there in the first place. It happened directly after installing Update Rollup 5 (KB2407132)

You can specify the port in the smtp connector. Perhaps someone accidently configured it to listen on this port. What did you do to determine edgetransport.exe was using the port? Is this an Edge Transport or Hub Transport server? Both use the same edgetransport.exe process. Can you post the output of: Get-ReceiveConnector | ft name, bindings Mike Crowley | MVP My Blog -- Planet Technologies

It's an SBS 2008 server, so it's hub transport. I used netstat /a /b /o to identify the process (which it identified as svchost.exe for some reason), then with the process ID, I used process explorer and found edgetransport.exe with that ID. No one changed any of the configuration, I'm the only one who touches that server. Looks like I was a little vague in my first post, I didn't restart the server, I restarted the service, the Microsoft Exchange Transport service. Once I did that, 3389 was closed and I started the Terminal Server service and RDP was functional.

Name Bindings ---- -------- Default SBS {192.168.1.11:25} Windows SBS Fax Sharepoint Receive SBS {127.0.0.1:25} Windows SBS Internet Receive SBS {192.168.1.11:25} Avimark {0.0.0.0:25} Via Trend Micro {0.0.0.0:25}

Sorry, that's very strange. I don't have any suggestions if it was a one time occurrence. Do be aware however that SP3 with RU7 is the current version of Exchange 2007. Mike Crowley | MVP My Blog -- Planet Technologies

Thanks, I plan to have SP3 installed soon anyway. I too thought it was strange and wanted to see if anyone else had that issue since I couldn't find anything on it.