Re: Remote Desktop no configuration diskette workaround?

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

artzoop wrote: 
Thank you, Joe and Lanwench, for your helpful responses.
Yes, Joe, you're right!  On a different, remote PC I hadn't done
anything to with XP I discovered I can use the built-in Remote Desktop
Connection (Start -> All Programs -> Accessories -> Communications ->
Remote Desktop Connection) -- without configuring with any Remote
Connection Disk, or using Connection Manager.  I simply entered my SBS
gateway IP and logged in.  On my router (gateway) I had done port
forwarding for 3389 to go to a particular workstation (and not my
server).  This works fine.

It would be nice, however, to have the option of remote desktop to
either my server or any of the workstations -- rather than the one
workstation I have port forwarded to.  Joe, can you elaborate upon "a
site VPN to open a path to the LAN and use RDP into the workstation
that way."  Is it possible to use Remote Desktop to chose whether to go
to the server or a workstation, or is it limited to the one computer
I've port forwarded to on my router gateway?


A site-to-site VPN connects the remote and SBS LANs together, more
or less, and the RDP client then connects to each machine by LAN
FQDN name (e.g. workstation1.local). As long as the remote machine
is using the SBS for DNS (many things won't work otherwise) the name
will be resolved to the workstation correctly.

Site-to-site is easiest to do with routers at both ends which can do
the job, when the SBS is in 1-NIC mode. SBS and Windows workstations
can create a site-to-site VPN but there's a fair bit of configuration
to do (i.e. I've done it once after a lot of research and effort, and
without documenting it). As I said, this isn't what Microsoft intended
and it's like pushing on a piece of string. Also, this kind of VPN
opens the SBS LAN to attack via the remote LAN, with much more risk
than an ordinary remote-workstation-to-SBS VPN brings.

I don't think either the XP RDP client or server can use different
port numbers, and I'm fairly sure the Active-X client can't, which
is a bit of a shame as that would be the easy way to do it. Unless
someone knows otherwise...
.

Relevant Pages

  • Re: Remote desktop to PC behing ADSL Router ?
    ... I want to Remote desktop from my SBS workstation ... > forwarded to the SBS server. ... > select the workstation you want to control with RDP. ...
    (microsoft.public.windows.server.sbs)
  • Re: Preventing logon to local accounts
    ... Otherwise I would've suggested adding "Domain Users" to the "Remote Desktop ... if there's a problem with their workstation at 3AM on Saturday). ... I restrict what *users* can do, ... VPN is of course far more of a security concern than is RDP itself, ...
    (microsoft.public.windows.server.active_directory)
  • Re: Terminal services
    ... He's changed the listening port for each workstation from the default ... You don't have to do this when you have RWW - you get ... > directly to their workstation using the Remote Desktop Connection. ... >> Terminal server requires TS licenses whereas RWW access is included ...
    (microsoft.public.windows.server.sbs)
  • Re: Getting back SBS TS access
    ... the functionality of the sbs desktop gateway is hard to duplicate at any ... a ssl vpn is the best solution, fortinet have a ssl remote desktop client ... On the server that has the Terminal Server running .. ... to connect to the Server or a Workstation attached to the LAN.. ...
    (microsoft.public.windows.terminal_services)
  • Re: Remote workspace issue
    ... Never tried to run RWW/RDP to a super high res monitor, but you might try lowering the res for a test. ... are there any errors in the event logs of either the server or the workstation that would give you any more info? ... The security logs on the server, in particular, will grow quickly, although I don't think the problem is there. ... When accessing via the web work place or direct via remote desktop from the ...
    (microsoft.public.windows.server.sbs)