| Author |
Topic  |
|
|
mitachu
Honorable But Hopeless Addict
    
United Kingdom
1947 Posts
Status: offline |
Posted - 04/26/2012 : 04:36:45 AM
|
Hi,
We've had a couple of instances where a 2008 R2 server has decided to stop servicing remote desktop connections. Twice this has happened after a server crash (power failure).
Terminal server licencing has been removed and reinstalled, Remote Desktop Services has also been removed and reinstalled. We originally had licensing errors in the event log which a MS hotfix was meant to resolve. After applying the hotfix the errors went away but we the server still isn't accepting connections.
We've only managed to resolve this problem by doing an inplace install of the server - Something of a sledgehammer approach, I feel. I'd love to know what the heck is going on.
Doing a netstat -an shows that the server is listening on 3389 but for whatever reason inbound connections are being denied.
Anyone know what might be occuring here?
|
Tim |
|
|
wobble_wobble
Honorable But Hopeless Addict
    
Ireland
4517 Posts
Status: offline |
Posted - 04/26/2012 : 05:12:25 AM
|
Tim,
this goes into some detail on what happens. I'm looking for the full description, but don't have it handy.
http://technet.microsoft.com/en-us/library/cc755399(v=ws.10).aspx or http://url.ie/f723
There are any number of things that will stop a TS working, AV, Firewall, port re-direction etc. Best way to see is possibly to start with Netmon or Wireshark and see if the traffic is hitting the server. Then looking with Sysinternals tools at what is going on within the Server.
Joe
|
Joe
After everything that has happened during the month of Jan 07, I do believe that pigs fly backwards!
http://whatismyv6.com/ |
 |
|
|
mitachu
Honorable But Hopeless Addict
    
United Kingdom
1947 Posts
Status: offline |
Posted - 04/26/2012 : 06:00:20 AM
|
Thanks Joe.
|
Tim |
 |
|
|
Playwell
Honorable But Hopeless Addict
    
Netherlands
4822 Posts
Status: online |
Posted - 04/26/2012 : 07:35:31 AM
|
What does seem to help as well is to delete the listener, and recreate it.
delete HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp Then create the connection in tsconfig.msc
|
'People who think they know everything are a great annoyance to those of us who do. ' Quote by Isaac Asimov

|
 |
|
|
mitachu
Honorable But Hopeless Addict
    
United Kingdom
1947 Posts
Status: offline |
Posted - 04/27/2012 : 03:25:13 AM
|
We deleted the RDP-TCP listener in the UI but didn't delete the reg key....
|
Tim |
 |
|
|
aval
Honorable But Hopeless Addict
    
USA
3276 Posts
Status: offline |
Posted - 06/04/2012 : 10:12:24 AM
|
Since you mention it and since it seems to have had something to do with the problem at least twice,
quote: Twice this has happened after a server crash (power failure).
Shouldn't you have a UPS and related software in place to shut them down properly? |
 |
|
|
mitachu
Honorable But Hopeless Addict
    
United Kingdom
1947 Posts
Status: offline |
Posted - 06/11/2012 : 5:13:19 PM
|
Some customers like to fly by the seat of their pants.
|
Tim |
 |
|
| |
Topic  |
|