Before I start, a big thank you to everyone for any assistance.

I can normally RDP to a remote server. Occasionally, RDP stops
working. A restart of the server fixes it.

There are no errors in the logs, and no errors on the client I am
connecting from. I can telnet on port 3389 (well, I get a connection
instead of an 'unable to connect' message).

The RDP client says it's connecting, then closes - no errors, zip.

I've restarted a bunch of services on the server - Exchange and
databases to free up some RAM. I'm wondering if the amount of RAM
available to the system is getting low - it has 4GB in it though.

The server is 2003 R2, running Exchange, DC, F&P and various other
apps and a database. All up, about 3GB RAM in use.

If you've any ideas, please let me know - I'm all ears.

Thrasher, I had the same problem with an identical server in my environment.
I could not RDP, even though port scans stated 3389 was open, nothing
appeared in the event log, and I even did a repair mode reinstall of Windows
2003. For me, it appeared to be a corrupted install of .Net 1.1 (just other
events in the event log, my inability to install 1.1 service packs, and no
soap when trying to repair the 1.1 installation.) For me, nothing worked and
after two months of stalling I finally archived everything to another server
and wiped. Sorry that I cannot offer more, but the frustration was
incredible and I thought it would be an easy fix.

You could try Dameware or PC Anywhere in the meantime to connect remotely.

Patrick

"thrasher" <robert.tristram@gmail.com> wrote in message
news:1174899242.961561.153410@n76g2000hsh.googlegr oups.com...

Thanks Patrick

Ouch - that's a nasty fix!

I've configured some logging of memory as I suspect there may be an
issue with system memory resources getting low. If I can find what is
taking memory without releasing it, I may be able to fix it, however I
may also just run a reboot script and reboot every Sunday night. Not
very elegant!

I'll see what the logging shows and let you know.

Cheers

Robert

I just rejoined the groups for an RDP connectivity issue after noting a
number of others with RDP issues, we only see them when someone is
performing an automated reboot from a software install via RDP.

Here's our scenario:
Admin user installs software via RDP
The install prompts for a reboot and user selects "Yes" (reboot now).
The server disconnects the session.
The server never actually reboots (according to System Log). In fact, it
appears that shutdown is never invoked. Applications are working, the server
is pingable and can be logged into locally.
RDP connectivity is lost, both for regular sessions and console (-console
switch) sessions.
Log onto the system console and reboot manually...RDP functionality is
restored.

We see this on both gold and SP1 W2K3 systems, fully patched and otherwise
clean.


Any similarity in either of your cases?


Charlie

"thrasher" <robert.tristram@gmail.com> wrote in message
news:1174961697.061880.195710@d57g2000hsg.googlegr oups.com...