Re: RDP connectivity to SBS2003 lost

see inline:


"Lanwench [MVP - Exchange]"
<lanwench@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:%23V9QnP2mFHA.1088@xxxxxxxxxxxxxxxxxxxxxxx
>
>
> In news:OQk%23uBqmFHA.3656@xxxxxxxxxxxxxxxxxxxx,
> Xavier <xminet@xxxxxxxxxxx> typed:
>> Hi,
>>
>> I have been using RDP to manage a SBS2003 box without problem for
>> over a year now. The box has been upgraded to SP1 last week and the
>> last issue I had to correct was a email alert being sent every 24
>> hours. This problem was fixed today by re-running the monitoring
>> wizard and by rebooting the server. While the issue is corrected, the
>> procedure seems to have introduced another one: RDP connection to the
>> box does not work anymore.
>> VPN connection works fine, so I can establish a connection to my
>> remote lan and use the admin tools (adminpak) against the server
>> without problem. However the port 3389 is not listening anymore.
>>
>> Does anyone know how I could re-establish the RDP on the server side
>> remotely (with regedit or some other tool) ? I would like to avoid to
>> travel to the box's console.
>>
>> Any suggestion would be appreciated.
>>
>> Thanks,
>>
>> Xavier
>
> If you can't get to the console at least once, this will be a royal pain,
> assuming it's even possible. Is there nobody on site who can do this? I'd
> have to think so (who did the SP1 upgrade?)
>


I performed the SP1 upgrade last week when I was onsite. And honestly
speaking, I prefer to be the only person working at the system's console.


> How about seeing if anyone on the LAN can do a telnet on port 3389 to the
> server by name?
>

I can establish a VPN connection to the remote network to perform some
tests:

telnet servername 3389 returns : Connecting To ServerName...Could not open
connection to the host, on port 3389: Connect
failed.

portqry -n ServerName -e 3389 returns: TCP port 3389 (unknown service): NOT
LISTENING

and event logs do not reveal errrors or any other hint... :-((


> Also, checking the event logs would be helpful.
>
>
>


.

Relevant Pages

  • RE: Windows Remote Desktop
    ... between the server and client in addition to RDP encryption. ... On the topic of securing RDP i was wondering if anyone can help.... ... connection is difficult. ... >We provide Ethical Hacking, Advanced Ethical Hacking, Intrusion ...
    (Security-Basics)
  • Re: MSKB 891957, VSS Update for Windows Server 2003
    ... I left the connection sit idle and checked back in an hour. ... server and browsed around for a few minutes. ... it would seem that there is still some issue with the V6 RDP ... I left the server with user Backup logged in when I left the ...
    (microsoft.public.windows.server.general)
  • Re: Storing Username/Password problem
    ... It's set on a per-server basis, so that any incoming RDP connection to that server is logged on with the credentials specified in Terminal Services Configuration. ...
    (microsoft.public.windows.terminal_services)
  • Re: MSKB 891957, VSS Update for Windows Server 2003
    ... Well, it turns out the RDP connection dropping issue won't go away, ... level to the server in the office may have an affect on the issue. ... I just remembered I also re-installed RDP Client V6 last night as ... I left the server with user Backup logged in when I left the ...
    (microsoft.public.windows.server.general)
  • Re: Does this sound like a bad nic?
    ... Run SBS BPA. ... or RDP fail to connect? ... After the server reboots, are all the ... the TS connection to use the built-in card, ...
    (microsoft.public.windows.server.sbs)