locked
See Desktop of Home Server computer during remote access RRS feed

  • Question

  • Is anyone know how I can see my home server computer desktop while I connect remotely with the

    https://<server>.homeserver.com link ?

    I want to install Web Cam and see the video feed while I out of Home.

     

    Monday, August 1, 2011 8:11 AM

All replies

  • Hi, Roire

    the remote-desktop-view belongs to the port 3389 (firewall) - the url  https://<server>.homeserver.com has only something to do with the remote access - but NOT with RDP! ;) this things are independent.

     

    Best regards,

    Hudre

    Monday, August 1, 2011 8:38 AM
  • thx,

    but, other computer on my network (like my wife laptop) , i can connect to it and see here desktop.

    when i press connect to the server it only lunch the dashbord and not the desktop.

    Can i see the desktop in the server ?

    Roi

     

    Monday, August 1, 2011 8:58 AM
  • Yes, you must diff the dashboard and the remote desktop. The dashboard is a remote application called from the server (remote session), the remote desktop (run mstsc.exe) shows you the whole desktop of the server, not only one window ;)

    So run mstsc.exe - type in the servername and sign in with administrative credentials and you can launch the servers desktop.

     

    Hudré

    Monday, August 1, 2011 9:45 AM
  • Can you help me with more detail instructions ?

    I’m outside me home and using Laptop computer running Win 7.  i run mstsc.exe and on the remote desktop connection terminal there is a line on "computer". what should i put there ? (https://<servername>.homeserver.com ; IP ? ) if you can write to me what should i put.

    thx !

     

    Tuesday, August 2, 2011 8:33 AM
  • Hey,

    You must not type in the protocol https:// - only the fqdn (fully qualified domain name) ( computername.domainname.tld such as server.homeserver.com ) is required there - the port i wrote above is for your router! you have to allow incoming connections on this port because normally the routers firewall blocks all incoming traffic and this is why you can't connect to your home.

    So go to your router:

    - make sure that the port 3389 is allowed for incoming connections (port 443 or 80 should be allowed if you can browse your servers website)

    - make sure that the router knows to which endpoint (server) the packets should be forwarded (so the fqdn has to be set to your server as endpiont)

    On your client:

    - test the connection with ping-trials (ping to the fqdn) for instance on port 80

    - run mstsc.exe and type in the fqdn and visit your servers desktop and make sure that you password is strong ;) - you can even modify it in the dashboard (it is a task in the computer and backup section)


    Best regards hudré
    Tuesday, August 2, 2011 8:46 AM
  • Hey,

    You must not type in the protocol https:// - only the fqdn (fully qualified domain name) ( computername.domainname.tld such as server.homeserver.com ) is required there - the port i wrote above is for your router! you have to allow incoming connections on this port because normally the routers firewall blocks all incoming traffic and this is why you can't connect to your home.

    So go to your router:

    - make sure that the port 3389 is allowed for incoming connections (port 443 or 80 should be allowed if you can browse your servers website)

    - make sure that the router knows to which endpoint (server) the packets should be forwarded (so the fqdn has to be set to your server as endpiont)

    On your client:

    - test the connection with ping-trials (ping to the fqdn) for instance on port 80

    - run mstsc.exe and type in the fqdn and visit your servers desktop and make sure that you password is strong ;) - you can even modify it in the dashboard (it is a task in the computer and backup section)


    Best regards hudré

    Your question regarding the IP - you can also try to connect with the ip (that your server is assigned to) - but this is the sense of DNS (or DynDNS), so you will not need it normally ;)

    Best regards hudré
    • Proposed as answer by hudré Tuesday, August 2, 2011 8:49 AM
    Tuesday, August 2, 2011 8:49 AM
  • A much less complicated way is to use Live Mesh, part of the windows live collection of services.  Install it on both your server and laptop, and you'll be able to launch a RDP session from the Mesh dashboard.  No configuring of router needed.  These are the directions I followed:

    http://usingwindowshomeserver.com/2011/03/04/windows-live-mesh-2011-on-windows-home-server-2011-video-edition/

     

    Matt

    • Proposed as answer by hudré Monday, August 8, 2011 7:59 AM
    Sunday, August 7, 2011 8:18 PM