Ubuntu Networking :: Setting Up Desktop (9.04) Behind Router For Remote Access By Latptop (9.10)?
Jan 8, 2010
Setting up desktop (9.04) behind router for remote access by latptop (9.10) I am setting up desktop (9.04) behind router for remote access by latptop (9.10). Rationale: All of my files are on my desktop HD, but I am often out of my home needing to work on my files. It is becoming labour intensive to keep track of the files I make/change and try to copy them on my non-connected desktop/laptop.
Dream: Able to remote access and modify my desktop files from my laptop (while the files remain on the desktop). Request: A simple, GUI, basic, non-technical guide how to set it up!
What I know: 1.I was going to use the 'Remote Desktop' VNC connection under System->Preferences. However, if I understand this correctly, this only secures my computer (i.e. Locks the front door of my desktop) and the data streamed between them is not encrypted.[URL]..
2.Then I need to set up my router to accept the connection from my laptop.
3.Then I will need to use SSH to secure the info sent between them. This is the bit I don't really have a good grip on.
My home linux box is behind a Linksys WRT110 router. I have enabled the Remote Desktop from System-->Preferences-->Remote Desktop. I then run TightVNC from my WinXP box. As I wish to run a secure connection, my first obstacle comes from PuTTY. In PuTTY, my settings are as follows:
Host Name(or IP address) Port xxx.xxx.xxx.xxx 22 SSH-->Tunnels:
[code]....
I recieve "Network error: Connection refused" I have gleened all of this information from other boards and tutorials. I know there is something critical that I am missing.
I'm trying to set up the Remote Desktop and am not getting anywhere. No matter what I do it seems that I'm only able to set it up to be viewable locally, over the local intranet. Do I need to open specific ports on a router? If so, what ports? Is there anything else I need to configure?
Running Ubuntu 9.10. In the Remote Desktop config dialog I get: "Your desktop is only reachable over the local network. Others can access your computer using the address 127.0.0.1 or tabatha.local." I understand this means only the loopback ip address is available. All my other machines show their true local ip address (e.g., 192.168.1.104) in this dialog. Thus I cannot log on to this desktop from other machines.
When I try to do a remote logon from another Ubuntu 9.10 box (or from an XP box using a VNC viewer), I get: "Connection to 192.168.1.102 has been closed." What steps are needed to make this machine show its actual ip address? All file sharing between the various machines is working properly and all windows shares back and forth between XP and 'nix, and among the the vaious XP boxes and linux boxes are available as designed.
I just set up Remmina the other day to be able to access my desktop remotely. However, I can only do this when I am connected to my home network. Is there a way to set up Remmina so that I can connect to my desktop remotely from outside my home network?
my g/f was able to access her jobs computers from home in Windows. she'd go start->program->access->connect to remote desktop... (or something like that) in any event, i've found some programs in Fedora 14 that say they'd do the same, however i can't get it to work. in "remote desktop viewer" i'm trying to use 'VNC' protocol,and trying to put the ip in the first of the "Host" lines.
now, there might be another issue, is it possible she need more info than the ones she got in order to use LINUX remote desktop? she has (what she has written down as) Computer # 111.111.111.11 and then ';' and 4 additional numbers, so (for the sake of the example) computer#: 111.111.111.11;2222 she has a 'username' and a 'password'.
I have 4 boxes on a local network: 2 with XP only, 1 with Ubuntu 9.10 only, and 1 with both. All boxes can share folders, set up with share-admin instead of using Nautilus right-click properties for each folder. I can see and control the remote desktops on all boxes, to all other boxes, from all other boxes,with one exception: I can only access the XP desktop on the dual boot box, not the Ubuntu desktop. When I try I get: "Connection to host 192.168.1.102 was closed." I am refused access to the Ubuntu desktop in this manner from both the other Ubuntu machine, and from both XP machines.
My setups are basically plain vanilla with routine installs of Ubuntu 9.10. On the XP machines I am using TightVNC on the XP machines to view both other XP desktops, and the Ubuntu desktop that is accessible. On both Ubuntu setups I am using (I suppose) vino and vinagre, and have completely re-installed what I think is the relevant software. There is no firewall running on the Ubuntu dual boot, when I check ufw. For reasons I cannot determine the inaccessible Ubuntu desktop is not providing its own address but instead in the Remote Desktop config dialogue it identifies itself as 27.0.0.1 which I think is the loopback id. I know so little about this sort of networking that I am not giving all relevant info, but I still thought I'd try.
New Fedora 13 Install. I have Remote Desktop Enabled. I can access the machine from itself but not others on the network. I stopped the firewall, that did not work. I looked in hosts.allow and hosts.deny, no entries there. The vino server is running. There is nothing in /varlog/messages, dmesg or /var/log/secure, at least nothing I could find related to vino. What else can I check? The conf file in my home folder looks exactly like one on another machine where it is working. forgot to add the message I get when I try it from a remote machine is "The connection to host 192.168.1.100 was closed". So it appears something is actively rejecting the login.
They are running Kubuntu. How to access their desktop from my home or office using Internet. Logically I remembered about kfrb and X11-vnc. But both of them need some approach to provide security. I'd like if someone could give me some pieces of advice on choosing the simplest and better approach:
To secure kfrb or x11-vnc is simpler or better to mount a vpn or to use an ssh tunnel? Is there any other solution? My pearents ISP use DHCP, so I think it would require some service like dyndns or similar...
Alright so i just wanted to try and get remote desktop connections running so i can access files on the other computers in my house. For my first try i went after my laptop. I'm using rdesktop.
First couple times i tried i typed in
Code:
After about 15 seconds it would pop back with
Code:
I realized that my laptop's firewall was blocking the packets, so i created a custom rule that allows all TCP packets on port 3389. So i fired up rdesktop again. Now it pops back with:
Code:
But instantaneously, not after 15 seconds (not sure if thats significant or not.) I checked my firewall's log and it allowed the tcp packets.
I am at a loss. I can not access my work remote desktop via the terminal server client on my wired box running Ubuntu 10.10. My wireless laptop is able to connect right away once I established the VPN connection. The VPN connection is established on both boxes with no problems.
When I tried the Terminal Server Client on my wired boxed, it says it can not establish a connection. Yet my wireless box gets connected immediately!
I check the /etc/dhcp3/dhclient.conf and the /etc/resolv.conf to see if there were any differences, but they are essentially the same. When I have the vpnc connection, they both recognize it and I am able to ping the IP address shown when I do a "ifconfig" on the terminal.
What can be the problem? Anything I need to configure on a wired computer versus a wireless one? What else can I check?
I want to set up a Linux box as a wireless router to replace our existing Netgear WNR1000 router, as I believe the Netgear does not support the coming IPv6 protocol. Unfortunately, it is not flashable with OpenWRT or DD-WRT presently.
As we have Comcast, our cable modem acts as a dumb modem according to the customer support guy I talked to, and our router is the one that asks for the IP address from DHCP. Thus, when Comcast switches over to IPv6, I don't believe my existing router would work, correct?
My idea is to take a Linux box and put two NICs and a wireless adapter in it, using IPCop or Smoothwall to set up a router. I could then enable IPv6 support for when we have IPv6 with Comcast. Is that possible? Would there be a way to get BIND to hand out private IP addresses in the same subnet on the both the LAN NIC and the wireless card?
I recently got a new router (and new isp). On my old isp and router it seemed quite simple to remote desktop to my linux box from any of my windows xp machines using vnc.
After I got my new router(WRT54GS2) and pretty much at the same time upgraded to 10.04 I had went back to reconfigure it. I simply cannot find a way to make this work. On the old version of ubuntu the remote desktop settings had a choice to change the port which seemed like the key ingredient to make it work when I was having troubles before. This new version seems verrry dumbed down to me and I can't seem to get anything to work.
I read some tutorials and all I've seen is to change port forwarding settings on my router(i'll include a picture of what that looks like)
My dell notebook runs Ubuntu (Karmic Koala). I want to be able to remote access my mom's Mac notebook (I believe it's an Airbook?), so that I can assist her with problems on her computer.What would I need to do on my computer (and how?)What would I need to do on her computer (and how?) to set this up?
I've done apt-get install kde-full on a server, and would like to know how to set up remote desktop control for it. As I've never done something like this before through a console, I'm rather stumped and can't seem to find any information on this matter.
We're in the final process of building a home, and I had them setup a wiring box where all the coax and cat5 terminates into one closet, which will also house my server. Once we get moved in I'd also like to add speakers in each room to have house-wide music, and ideally I'd like the audio to also run into this box with the master input coming from the server as well.My thought was to setup the server with some basic desktop manager like Fluxbox and use that to drive audio throughout the house, whether it be Pandora, Sirius Radio, or whatever. Since the server will be headless I'll need it setup so we can remote into it from our laptops, but I wasn't sure if VNC or some other RDP variant would work. Ideally we'll need to access a unified desktop so traditional terminal services where each users gets their own desktop might not be ideal
I have just installed linux 10.10, I want to use vnc on my another computer to access my desktop using remote access. When I navigate to Remote esktop Preferences. Your desktop is only reachable over the local network. Others can access your computer using the address localhost, no ip address. this is not working.
I was sitting watching a TV show on the internet (streaming from channel 4) and all of a sudden I get a request from an unknown IP address, outside of my local network attempting to access my ubuntu desktop, I obviously declined straight away and stupidly didn't take note of the IP I've checked my firewall settings and no ports are being forwarded, everything is as it should be. I am running Ubuntu 11.04, and a little bit concerned. As of now I have completely disabled remote desktop on my laptop.
I am having the following problems:I have tried installing vnctightserver on Ubuntu and then installing the viewer on my windows machine but when I try to connect it rejects the connection....I need to remotely access the ubuntu-desktopn my ubuntu server LTS 10.04..... I have tried a number of guides but none are working for me....I have a firewall installed (iptables) but the neccesary ports have been opened up but my server still rejects incoming vnc connections.On a side note I do not have physical access to the server so all setup needs to be done via SSH...
Weird thing going on on my headless lenny box. The shared desktop won't let me in.I am trying to connect with my Mac, ssh is ok. I can connect, start vino-preferences, change everything I want to change, and still it won't let me in. both Mac Ctrl-k to vnc://lenny and Chicken of the VNC won't connect.
so it's been a while [a long while!] since I needed any desktop access to my suse server.... what are my options for an RDP server these days? VNC and.....? is there anything else? anything better?
I use a hosted machine for work which has vnc and apache servers running. To work on a shell, I connect to the VNC server, and to access files I host them using apache and open them from my browser. It would be great if I can access my shells via my browser itself instead of using VNC or command prompt.
I am looking for an end result like this: [URL].. What are my options? PS: I already tried [URL]..but this uses a java applet to run and does not do it in browser itself.
I've just been tasked with making our company's workstations available from remote locations over our internet connection. While it seems simple in concept, I know there will be several issues I'll have to deal with. What I'd like to know is if anyone has recommendations as far as software to use and methods for securing connections. I'd like to have communications encrypted, which last I heard OpenVNC couldn't do (maybe that's not the case?). Also, I'm not really sure how the interactions between windows clients vs. my linux server and the remote connections should be handled. Would I need a separate instance of say, OpenVNC, on each client that I wanted to be allowed remote access?
How can I get remote desktop access ignoring firewalls and NATs? I succeeded in creating a remote desktop session within my home LAN.
Though I configured my router to pass through port 5900, and learned the correct external IP, I am unable to create a remote desktop session inbound to my machine, nor outbound to a machine on a remote network (with static IP).
This is caused by various network complications like NATs and firewalls.
Fogcreek's Copilot or Skype on Windows manage to connect with no network reconfiguration.
Is there some remote desktop alternative that "just works"?
I have an Ubuntu server that I need to access remotely while I am at school. The server's internet connection comes first through a DI-604 broadband router and then through a Netgear Wireless router:
ethernet wall jack --> Broadband Router --> Wireless Router --> Server's ethernet port
I can manage to get the SSH to work with the current IP address (dynamic) by connecting the server directly to the broadband router, but I cannot set up DNS (ddclient on the server, Namecheap for domain registrar and nameserver) with it. I can set up DNS on the router with no issue, as it has the DNS client built in, but I cannot get the SHH to connect through both the modem and the router as mentioned above. Best case scenario, this can be fixed without having to get anything new, but if that is the case, recommendations of a new setup
Other reference info - ISP at server is Verizon Fios, broadband router set to PPPoE.