Results 1 to 10 of 10

Thread: W2K3 RDP mystery

  1. #1
    Senior Member
    Join Date
    Dec 2005
    Location
    ::1
    Posts
    204
    Thanks
    4
    Thanked
    9 times in 8 posts
    • chinny's system
      • Motherboard:
      • Asus P5Q-EM
      • CPU:
      • Intel E6300
      • Memory:
      • 4Gb Corsair XMS2
      • Operating System:
      • Win7 x64

    W2K3 RDP mystery

    Hi,

    I've got a W2K3 box which RDP has stopped working on. It's a bit strange in that netstat shows the port listening. I can telnet to 3389 both locally and remotely but I am unable to connect (I get "This computer can't connect to the remote computer. Try connecting again.").
    I can't net stop or start "termserver" either.
    Sigverif looks ok.
    Does anyone have any ideas where I should look next...

    PS. Forgot to say it's SP2.

  2. #2
    TiG
    TiG is offline
    Walk a mile in other peoples shoes...
    Join Date
    Jul 2003
    Location
    Questioning it all
    Posts
    6,213
    Thanks
    45
    Thanked
    48 times in 43 posts
    When you say you can't stop termserver either, why not?, whats the message you get to that?.

    Personally if a service isn't operational i'd want to get that sorted.

    The Event log got any errors ?, assuming you can see this as you say about the services.

    TiG

  3. #3
    Senior Member
    Join Date
    Dec 2005
    Location
    ::1
    Posts
    204
    Thanks
    4
    Thanked
    9 times in 8 posts
    • chinny's system
      • Motherboard:
      • Asus P5Q-EM
      • CPU:
      • Intel E6300
      • Memory:
      • 4Gb Corsair XMS2
      • Operating System:
      • Win7 x64
    RDP is enabled via GP so starting and stopping it are greyed out. Nothing of any relevance in the eventlogs either....

  4. #4
    Senior Member burble's Avatar
    Join Date
    May 2007
    Location
    Olney
    Posts
    1,138
    Thanks
    8
    Thanked
    90 times in 89 posts
    One of my 2K3 boxes in Phoenix and one in Stockholm occasionally have this same problem. The only way around if I've found is to reboot the boxes.

  5. #5
    Senior Member
    Join Date
    Dec 2005
    Location
    ::1
    Posts
    204
    Thanks
    4
    Thanked
    9 times in 8 posts
    • chinny's system
      • Motherboard:
      • Asus P5Q-EM
      • CPU:
      • Intel E6300
      • Memory:
      • 4Gb Corsair XMS2
      • Operating System:
      • Win7 x64
    Quote Originally Posted by burble View Post
    One of my 2K3 boxes in Phoenix and one in Stockholm occasionally have this same problem. The only way around if I've found is to reboot the boxes.
    That's looking like my first job tomorrow morning.....thanks.

  6. #6
    Ex-MSFT Paul Adams's Avatar
    Join Date
    Jul 2003
    Location
    %systemroot%
    Posts
    1,926
    Thanks
    29
    Thanked
    77 times in 59 posts
    • Paul Adams's system
      • Motherboard:
      • Asus Maximus VIII
      • CPU:
      • Intel Core i7-6700K
      • Memory:
      • 16GB
      • Storage:
      • 2x250GB SSD / 500GB SSD / 2TB HDD
      • Graphics card(s):
      • nVidia GeForce GTX1080
      • Operating System:
      • Windows 10 x64 Pro
      • Monitor(s):
      • Philips 40" 4K
      • Internet:
      • 500Mbps fiber
    Did the problem start after a reboot, maybe installing some software?
    If there are a bunch of pending file operations after a reboot, termdd might not load in time for termserv to use it, and you find that a second reboot fixes it.

    If you drill down to HKLM\SYSTEM\CurrentControlSet\Services\TermService and edit the DependOnService MULTI_SZ value, add termdd below the default line (RPCSS).
    This will make Terminal Services wait until termdd is running before it starts itself.

    Back up the registry key before making any changes, naturally

    FYI, you shouldn't be able to stop or start Terminal Services when the OS is up, it has boot-start components.
    ~ I have CDO. It's like OCD except the letters are in alphabetical order, as they should be. ~
    PC: Win10 x64 | Asus Maximus VIII | Core i7-6700K | 16GB DDR3 | 2x250GB SSD | 500GB SSD | 2TB SATA-300 | GeForce GTX1080
    Camera: Canon 60D | Sigma 10-20/4.0-5.6 | Canon 100/2.8 | Tamron 18-270/3.5-6.3

  7. #7
    Senior Member
    Join Date
    Dec 2005
    Location
    ::1
    Posts
    204
    Thanks
    4
    Thanked
    9 times in 8 posts
    • chinny's system
      • Motherboard:
      • Asus P5Q-EM
      • CPU:
      • Intel E6300
      • Memory:
      • 4Gb Corsair XMS2
      • Operating System:
      • Win7 x64
    The problem started after someone installed SRS 2005 on it. As you said the second reboot did fix it as well.
    Would you recommend adding termdd in only if you have a machine that is playing up or is it good practice anyway?

  8. #8
    Ex-MSFT Paul Adams's Avatar
    Join Date
    Jul 2003
    Location
    %systemroot%
    Posts
    1,926
    Thanks
    29
    Thanked
    77 times in 59 posts
    • Paul Adams's system
      • Motherboard:
      • Asus Maximus VIII
      • CPU:
      • Intel Core i7-6700K
      • Memory:
      • 16GB
      • Storage:
      • 2x250GB SSD / 500GB SSD / 2TB HDD
      • Graphics card(s):
      • nVidia GeForce GTX1080
      • Operating System:
      • Windows 10 x64 Pro
      • Monitor(s):
      • Philips 40" 4K
      • Internet:
      • 500Mbps fiber
    "If it ain't broke, don't fix it."
    ~ I have CDO. It's like OCD except the letters are in alphabetical order, as they should be. ~
    PC: Win10 x64 | Asus Maximus VIII | Core i7-6700K | 16GB DDR3 | 2x250GB SSD | 500GB SSD | 2TB SATA-300 | GeForce GTX1080
    Camera: Canon 60D | Sigma 10-20/4.0-5.6 | Canon 100/2.8 | Tamron 18-270/3.5-6.3

  9. #9
    Sublime HEXUS.net
    Join Date
    Jul 2003
    Location
    The Void.. Floating
    Posts
    11,819
    Thanks
    213
    Thanked
    233 times in 160 posts
    • Stoo's system
      • Motherboard:
      • Mac Pro
      • CPU:
      • 2*Xeon 5450 @ 2.8GHz, 12MB Cache
      • Memory:
      • 32GB 1600MHz FBDIMM
      • Storage:
      • ~ 2.5TB + 4TB external array
      • Graphics card(s):
      • ATI Radeon HD 4870
      • Case:
      • Mac Pro
      • Operating System:
      • OS X 10.7
      • Monitor(s):
      • 24" Samsung 244T Black
      • Internet:
      • Zen Max Pro
    The webserver (2003 R2) at work did the exact same thing, only no number of reboots fixes it..

    It seemed to happen after a windows update?

    I got around it by just putting vnc on it
    (\__/)
    (='.'=)
    (")_(")

  10. #10
    Senior Member
    Join Date
    Dec 2005
    Location
    ::1
    Posts
    204
    Thanks
    4
    Thanked
    9 times in 8 posts
    • chinny's system
      • Motherboard:
      • Asus P5Q-EM
      • CPU:
      • Intel E6300
      • Memory:
      • 4Gb Corsair XMS2
      • Operating System:
      • Win7 x64
    Quote Originally Posted by Paul Adams View Post
    "If it ain't broke, don't fix it."
    Sound advice....

    Quote Originally Posted by Stoo View Post
    The webserver (2003 R2) at work did the exact same thing, only no number of reboots fixes it..

    It seemed to happen after a windows update?

    I got around it by just putting vnc on it
    Yup - VNC was the short term solution for yesterday......

    Thanks for all the help.

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Similar Threads

  1. RDP Concurrent sessions - Memory or CPU ?
    By KW1816 in forum Software
    Replies: 8
    Last Post: 05-06-2007, 04:53 PM
  2. Mystery over roadside underwear
    By DR in forum General Discussion
    Replies: 23
    Last Post: 23-01-2007, 01:30 PM
  3. RDP Headache :(
    By latrosicarius in forum Networking and Broadband
    Replies: 0
    Last Post: 07-09-2006, 05:51 AM
  4. Mystery Shoopers
    By Workaholic in forum General Discussion
    Replies: 9
    Last Post: 20-10-2005, 03:04 PM
  5. Mystery file?!
    By Tomahawk in forum Software
    Replies: 2
    Last Post: 25-04-2004, 09:56 PM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •