Re: Cannot RDP into 2003 Server DC
Sorry - that's what I meant. I have fixed it, however. We removed the
listener and rebooted. I open TS Configuration and noticed there wasn't
anything in the Connections folder. I added a new connection and now it
looks like we're all set!
Lanwench [MVP - Exchange] wrote:
> George Nussbaum <nuzzy@nuzzy.com> wrote:
>> Hi Matt,
>>
>> Yes - I couldn't telnet into 3389. I tried another server in the same
>> segment and could successfully telnet to it.
>
> What about on the server itself -
>
> telnet localhost 3389
>
>
>> George
>>
>>
>> Lanwench [MVP - Exchange] wrote:
>>> George Nussbaum <nuzzy@nuzzy.com> wrote:
>>>> Hi all,
>>>>
>>>> We think it's an issue with the RDP listener. Someone here said
>>>> that they have seen this behavior before and had to delete it and
>>>> reinstall it to fix the issue.
>>> Did you try the telnet, as I suggested?
>>>
>>>
>>>> George
>>>>
>>>> RemyMaza wrote:
>>>>> My PDC I have to put the IP address in and then follow it with
>>>>> :3390 to login. Not sure why but this is the only thing that ever
>>>>> worked. Example:
>>>>>
>>>>> 10.10.1.3:3390
>>>>>
>>>>> Regards,
>>>>> Matt
>>>>>
>>>>> "Lanwench [MVP - Exchange]" wrote:
>>>>>
>>>>>> nuzzy <me@you.com> wrote:
>>>>>>> On 2007-11-10 14:24:31 -0500, "Lanwench [MVP - Exchange]"
>>>>>>> <lanwench@heybuddy.donotsendme.unsolicitedmailatyahoo.com> said:
>>>>>>>
>>>>>>>> George <nuzzy@nuzzy.com> wrote:
>>>>>>>>> Hello,
>>>>>>>>>
>>>>>>>>> I'm trying to remote desktop into a 2003 server that serves as
>>>>>>>>> a domain controller. However, I get the "This computer cannot
>>>>>>>>> connect to the remote computer" message. I matched the policy
>>>>>>>>> settings to that of another dc that works and still nothing.
>>>>>>>>> Any ideas?
>>>>>>>> Is remote desktop enabled on that server?
>>>>>>>> Any firewall blocking the packets?
>>>>>>> Yes - RD is enabled and the server has RDP open on the FW.
>>>>>> What firewall? If this is a software firewall app, disable it and
>>>>>> test. On the TS box, try a telnet on 3389 to localhost -and try a
>>>>>> telnet on 3389 across the LAN to the server's name/IP.
>
>
>