Remote Desktop connection not working

Hi,

I've been trying to get Remote Desktop client to connect to my Windows 2003 Server (standard edition) but it fails with:

"Remote Desktop Disconnected"
This computer can't connect to the remote computer.

Try connecting agian. If the problem continues, contact the owner of the remote computer or your network administrator."

I'm over the other side of the world from my server so having to ask inexperienced staff to check and test things for me. They can't connect via the LAN either using different accounts. Got them to check that it is enabled on the server and that the correct users are allowed access and are members of the remote access groups etc. The RDP services are running on the box too.

Was running out of ideas and not finding any errors messages to go by until i read on this newsgroup about trying the "Port query" tool. So I downloaded that and got it to query port 3389 on the IP address of the box and it returned some clues:

"querying...

TCP port 3389 (ms-wbt-server service): NOT LISTENING
portqry.exe -n www.mydomaintest.nz -e 3389 -p TCP exits with return code 0x00000001."

Says it is not listening? and returns 0x00000001 which I presume is an error code.

On the box I'm running ISA Server 2004 SP2 and have rules to allow RDP access (Copied them from my SBS03 rules which work).

I'm no means an expect on firewalls, but is this telling me that my firewall rule is blocking 3389? or that my web server is not listening?

Help :)
Thanks
Tristan

.

Relevant Pages

  • SecurityFocus Microsoft Newsletter #152
    ... MICROSOFT VULNERABILITY SUMMARY ... Real Networks Helix Universal Server Remote Buffer Overflow ... ... NEW PRODUCTS FOR MICROSOFT PLATFORMS ...
    (Focus-Microsoft)
  • Re: Users can only login to one TS server
    ... I also checked that the remote desktop user group was in the the rdp-tcp connection on the local computer. ... What I didn't realise till coming here was that the desktop user group on the server was local to that machine and not the AD group. ... The *only* thing you have to do is to make the users members of the local Remote Desktop Users group on the TS. ...
    (microsoft.public.windows.terminal_services)
  • SecurityFocus Microsoft Newsletter #140
    ... Cafelog b2 Remote File Include Vulnerability ... Webfroot Shoutbox Remote Command Execution Vulnerability ... Pablo Software Solutions Baby POP3 Server Multiple Connection... ... Microsoft Windows XP Nested Directory Denial of Service... ...
    (Focus-Microsoft)
  • Re: Users can only login to one TS server
    ... were members of the remote login group in AD and that their AD profile didn't ... group on the server was local to that machine and not the AD group. ... did was add my users to the remote desktop group on the local machine and now ...
    (microsoft.public.windows.terminal_services)
  • RE: Remote Desktop Connection does not work
    ... returned to the local desktop screen that I initiated the remote connection ... connected remote desktop session. ... >>I have just recently setup a new server using SBS 2003. ...
    (microsoft.public.windows.server.sbs)