Cannot remote desktop my domain controller after windows updates

I can still connect to other servers on the network.
I tried rebooting my computer to see if it was an authentication problem but it didn't change anything.

Check Windows Firewall settings on DC. Maybe update turns on firewall...

I checked, the firewall wasn't accessible because the ICS was off. After checking the firewall and selecting remote desktop in it I can see that the port TCP 3389 is open.
I still can't connect after that, I get the same error message.

Can You chack all network settings (ip, Gateway etc.)?
Can You rollback updates that you installed? Then install updates one by one and check witchone doing problem.

Did you apply the updates via a RDP session and reboot or did you install locally on the server?  Is RDP enables still after the updates?

Kola12 :
This our domain controller and exchange server, I cannot reboot it often. I will try anything else before uninstalling the updates and then trying to install them one by one. I'm not sure anymore because I did a lot of updates but I think there was at least 10 updates, that means rebooting 10 times and that is way too much.

Harper :
I did it via remote desktop connection and it is still activated, I checked on the server. My use is still authorized to connect to the server.

kola12 :
I also checked the network settings and everything is as usual for that.

Hello,

So i've been looking  at the situation and it seems I'm missing some services. When I look at the services list, I cannot find remote desktop service. It seems it has disappeared. When I check on my windows seven computer, this service is there.

Is it another name in SBS2K3? Or maybe that is my problem, if I don't have the service active on my server, I won't be able to use remote desktop connection with it.

Thanks.

So I checked the registry, the port number for remote desktop is still 3389. When I use netstat -no, I don't see anything using port 3389. So it seems that remote desktop in not started.
How can I force it to start? Do I have to reinstall something?

Thanks.

So, finally it's ok.
The problem was far from urgent and I had a lot of other things to do.
I checked quite a few things, and finally I had time to do a reboot (main domain controller, I may not reboot it when I want).
The problem was solved after a reboot.
I think the service crashed at the previous reboot, and it had nothing to do with updates. I think I was unucky.

I don't really have a solution, and I can't really accept the solution of anyone who answered.
I think the question should be deleted since it is not something that will help anyone else.

Thanks Kola and Harper for your suggestions, but as it was not the right direction for the solution it's a bit hard to justify accepting your comments as solutions. So I created a comment with all the steps I used to solve my problem.