Re: RDP connectivity to SBS2003 lost



In news:OxZvZa5mFHA.764@xxxxxxxxxxxxxxxxxxxx,
Xavier <xminet@xxxxxxxxxxx> typed:
> 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.

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

Doubt that will work, given what you've said....
>>
>
> 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... :-((

Can you RD to a workstation via RWW, VPN, whatnot, and see if you can
remotely manage the server at all?
>
>
>> Also, checking the event logs would be helpful.


.

Relevant Pages

  • Re: How to connect to a remote server from a local studio manager
    ... My Linksys RVS4000 (the router that's used to connect my network to the ADSL network modem) is designed to host VPN connections. ... This can also be done with a dedicated ISA server, but that's not really necessary now that the routers have gotten so smart. ... Once you have this router in place, you can easily use any Windows client to establish a VPN connection to the network. ... I'd like to see my remote server as part of my Local Network ...
    (microsoft.public.sqlserver.connect)
  • Re: RDP Connectiod 721 / 800 Errors
    ... The VPN connection is used for a number of reasons: ... Server Side Reporting facility, ... it permits local printing without the need to specify that remote printers ...
    (microsoft.public.windows.server.sbs)
  • RE: Remote Access and ISA Server in SBS 2003?
    ... I understand that after you upgraded the SBS Server ... Error Message: VPN Connection Error 800: Unable to Establish Connection ... Then we need to run the "Remote Access Wizard" to enable the VPN Server ...
    (microsoft.public.windows.server.sbs)
  • RE: Need help setting up VPN access
    ... Thank you for posting to the SBS Newsgroup. ... I understand that you want to setup VPN connection for some remote clients. ... 2> For IP configuration on server and client workstations, ...
    (microsoft.public.windows.server.sbs)
  • SecurityFocus Microsoft Newsletter #152
    ... MICROSOFT VULNERABILITY SUMMARY ... Real Networks Helix Universal Server Remote Buffer Overflow ... ... NEW PRODUCTS FOR MICROSOFT PLATFORMS ...
    (Focus-Microsoft)
Loading