+ Post New Thread
Results 1 to 5 of 5
Windows Thread, Server 2003 RDP problem in Technical; since my ISA server died the other week and i had to reinstall i can no longer RDP onto that ...
  1. #1
    DSapseid's Avatar
    Join Date
    Feb 2007
    Location
    West Sussex
    Posts
    1,152
    Thank Post
    130
    Thanked 54 Times in 47 Posts
    Rep Power
    38

    Server 2003 RDP problem

    since my ISA server died the other week and i had to reinstall i can no longer RDP onto that server to manage it remotely, hence i still have it sitting on my desk .

    I can ping it from my machine and the domain controller by ip address' and host name, i can ping my machine and the the dc from the isa server so i know they can see each other. Firewall client can detect the isa server fine.

    Everytime i try and connect to it i get the is it turned on message which it is as i just pinged it! I also cant connect to another server from the isa server which is strange, it asks me for my credentials so i put them in and it errors and says its wrong but there not!

    I have checked the box that says allow remote desktop connections in system properties and added my self to the authorised users.

    Server is Server 2003 R2 with all updates available installed.

    Any ideas?

    Dan

  2. #2

    Michael's Avatar
    Join Date
    Dec 2005
    Location
    Birmingham
    Posts
    9,262
    Thank Post
    242
    Thanked 1,568 Times in 1,250 Posts
    Rep Power
    340
    Make sure port 3389 is unblocked, as this is what RDP uses. How are you connecting via Remote Desktop - Computer name or IP address?

    When you're asking for your credentials, try entering domain\username, then your password.

  3. #3
    DSapseid's Avatar
    Join Date
    Feb 2007
    Location
    West Sussex
    Posts
    1,152
    Thank Post
    130
    Thanked 54 Times in 47 Posts
    Rep Power
    38
    There is a rule in ISA firewall policy especially for 3389 RDP connections.

    Have been doing the domain\username for credentials as well!

  4. #4

    Michael's Avatar
    Join Date
    Dec 2005
    Location
    Birmingham
    Posts
    9,262
    Thank Post
    242
    Thanked 1,568 Times in 1,250 Posts
    Rep Power
    340
    Can you verify RDP is using port 3389?

    Code:
    HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\TerminalServer\WinStations\RDP-Tcp\PortNumber

  5. #5
    DSapseid's Avatar
    Join Date
    Feb 2007
    Location
    West Sussex
    Posts
    1,152
    Thank Post
    130
    Thanked 54 Times in 47 Posts
    Rep Power
    38
    Sorry for taking time to reply but my main file server died end of last week! Yep it using 3389 at that reg key.

    On another note its also not letting https requests through, could this be the same thing?

SHARE:
+ Post New Thread

Similar Threads

  1. Windows Server 2003 problem
    By denon101 in forum Windows Server 2000/2003
    Replies: 14
    Last Post: 4th February 2009, 09:57 AM
  2. Increase idle time for logon - RDP 2003
    By monkey_boy in forum Thin Client and Virtual Machines
    Replies: 1
    Last Post: 12th January 2009, 08:49 PM
  3. Windows Server 2003 Installaion Problem
    By faisalpandu in forum Windows Server 2000/2003
    Replies: 4
    Last Post: 25th October 2008, 11:38 PM
  4. Really stupid server 2003 problem
    By dezt in forum Windows Server 2000/2003
    Replies: 12
    Last Post: 6th August 2008, 09:24 AM
  5. Problem with server 2003 maping
    By goclone in forum Windows
    Replies: 2
    Last Post: 16th September 2007, 08:31 AM

Thread Information

Users Browsing this Thread

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

Posting Permissions

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