Re: Remote Desktop Fails on Server 2K3 After Every Restart

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

I was able to ping both ways but I haven't tried the Telnet option yet. I'll
report back when I do. However, I did notice that after this happens, the
Terminal Services service options are grayed out both via remote computer
management (I can do this, I just can't remote desktop into the server) and
sitting in front of the machine itself. Someone mentioned that it's because
I might not have sufficient priveleges but I'm logged in as the admin. Any
other thoughts?

(The options for the RPC service are also grayed out but I suspected that it
was because the TS service was in whatever state it's in now.)

"Pegasus (MVP)" wrote:

When I see this message then I invariably do this:
- I ping the RD host by its IP address to ensure that it is correct.
- I ping the RD host by its name to ensure that it can be resolved.
- I run telnet to check if the RD port is open, e.g.
telnet MyServer 3389
And no, I have never seen this phenomenon.

"Jason H." <JasonH@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:0A0B855E-59AF-44D1-885A-B323E81C4649@xxxxxxxxxxxxxxxx
Thanks for the prompt reply. Unfortunately, the logs show nothing
relating
to Terminal Services at the time of reboot - in fact, nothing relating to
anything pertinent.

I can implement the script you've provided (many thanks for that) but it's
definitely not the ideal solution. Have you never heard of anything like
this?

Anyways, to answer your question, the message I get when I try to connect
to
the server is: "The computer can't connect to the remote computer. Try
connecting again. If the problem continues, contact the owner of the
remote
computer or your network administrator."

Thanks again for that script.

- JH

"Pegasus (MVP)" wrote:


"Jason H." <JasonH@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:D9D788AD-3FFC-4493-83F7-8097EA2B589A@xxxxxxxxxxxxxxxx
For about 6 months now, our 2K3 servers have had the same issue:
Remote
Desktop stops working after a restart (be it for patches or just
maintenance.) Every single time, we have to log on to the machine at
the
console and restart it again. This fixes the problem - EVERY SINGLE
TIME -
and we're able to remote desktop into the servers again after this
server
restart. This issue does NOT apply to our Win2K servers. We have no
problem
connecting to those via Remote Desktop after they are restarted.
Anyone
have
any idea what may be going on? Restarting a server that's hosting
critical
services can be taxing enough - have to reboot it twice is just
frustrating...for us and our users.

You should examine the Event Log on these servers and check specifically
for messages about the Terminal Server service.

What exactly is the message you see when you attempt to launch an RD
session?

Until you find the cause of your problem, you should implement an
automatic second reboot. Manually create a file c:\windows\reboot.txt,
then use the Task Scheduler to run this batch file at boot time:

@echo off
if not exist c:\windows\reboot.txt goto :eof
del c:\windows\reboot.txt
shutdown /.. /.. /..

Select the appropriate switches to reboot the machine within
five minutes.






.

Relevant Pages

  • Re: /etc/hosts - how does that file work?? - was weird nfs issues.
    ... anything besides ping - but it only ping hits the 172 address... ... client# grep server /etc/hosts ... telnet: connect to address 172.20.6.1: Connection refused ...
    (freebsd-questions)
  • RE: VPN
    ... on SBS, however, you can not RDP to the server and ping SBS from remote ... install Windows Server 2003 Service Pack 1 on a computer that is running ...
    (microsoft.public.windows.server.sbs)
  • Re: RDP access to SBS 2003 - HELP please
    ... Try the remote desktop connection to see if it works. ... This occurs from home and also from within the LAN where the server is ... I tried telnet and it hangs perhaps indefinitely, ... I can't tell whether port 3389 is open, ...
    (microsoft.public.windows.server.sbs)
  • Re: Hogwasher offline newsreader issues
    ... I can both ping and telnet to the ... waynedputer:~ wayned$ telnet news.panix.com 119 ... Try another news server, eg one of the free ones, with Hogwasher to see ...
    (comp.sys.mac.apps)
  • Re: Error on 64 bit systems...
    ... If it drops ping requests, ... Confirm whether the system is just an average server, ... is the account you are using to connect to the remote ... as soon as I use this same script to run on64 ...
    (microsoft.public.scripting.vbscript)