Fedora Networking :: Cannot Remote Desktop / Connection To Machine Name Was Closed
Nov 7, 2010
I have recently installed fedora 14 and configured vpn to access my work network. I need to access some windows machines which although I can ping I cannot remote desktop into. When I go to Applications>Internet> Remote Desktop Viewer and put in the machine name (either just the machine name or the FQDN including the domain name) I get an error "Connection to <machinename> was closed".
i try to connect to a specific ip address with ssh i have installed the ssh server and client. i also try it by connecting with localhost without any problem. But i keep taking this message if to try to connect to the ip address. i checked my hosts.allow and hosts.deny files and all are commented in there (i think tha this should not be the problem).
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:
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 have my main box, Ubuntu 10.04lts, and I am trying to use remote desktop viewer to see the desktop on a Windows XP machine. The machines are side by side The Ubuntu box is hardwired to my network router, and the XP machine is connected via wireless. Both get to the internet fine, and I can ping the Ubuntu box from the XP box. But, I cannot ping the XP box from the Ubuntu box, and Remote Desktop Viewer won't establish a connection to the VNC server I have running on the XP box.
Saying that the problem is only with ssh would be wrong as I can't seem to telnet or ftp it either. But I can ping it fine.When I try to login to that VM through console, it won't even let me login. The screen would flash for a sec and the same login prompt would reappear. I am not sure what exactly happened as it was working fine before.
I have installed Fedora 13 and updated it. I simply cant use ssh to connect to this Fedora, not even locally. I have enabled port22 in firewall settings and nothing. Tried to disable firewall completely and nothing. I have disabled SELinux (not sure if it has something to do with this, but... ) and nothing. Entered "ALL: ALL" in /etc/hosts.allow and still nothing. Dont know what to do anymore.
Here is what happens when I try to ssh to this machine, even from it: [flibio@surf ~]$ ssh localhost warning: Need basic cursor movement capability, using vt100 flibio's password: Authentication successful. Disconnected; connection lost (Connection closed.). Connection to localhost closed. [flibio@surf ~]$
Looking into Services > sshd and it says "This service is dead." So I tried: [root@surf etc]# service sshd restart Stopping sshd: [FAILED] Starting sshd: : OpenSSH_5.4p1 on : FATAL: Creating listener failed: port 22 probably already in use! .....
And still I get disconnected whenever I try to ssh to this machine from anywhere. Services says that sshd is allways dead, even restarting it but I can only restart it by doing a pkill sshd before.
Friday night I was working on some networking stuff between my two Fedora 14 boxes. I have my laptop and my desktop. on both machines I have "system-config-firewall 1.2.27" and "iptables" (i believe both come standard on F14?) I kept getting the same message as seen below before realizing perhaps I should check my firewall!
I added a rule for incoming and outgoing traffic on port 22 and was able to get in with no problems at all! however today I can't ssh into anything... I can't use "Remote Desktop Viewer 2.31.4" to vnc into the machine anymore. I can't remember the exact error message at this time, it's something close to "Connection was terminated" or "Unable to connect" I can update this message later.
last night I foolishly uninstalled the system-config-firewall and then uninstalled iptables to see if it was a simple firewall issue.... totally hosed my system <insert smiley!>
After reinstalling and realizing I didn't backup my documents <insert smiley!...again...> I started reinstalling all of my applications. I'm still unable to use ssh and I've tried to ssh my own computer.
Is this possible?
# ssh 127.0.0.1 ssh: connect to host 127.0.0.1 port 22: Connection refused
I want to use a headless (no monitor) and armless (no keyboard/mouse) PC as a Linux box that I can remotely access from my other machines. That is I want to make it look like I'm sitting at the console on the Linux box with a monitor/keyboard/mouse.
I've tried that via the instructions at [URL]
but, the moment I disconnect the monitor and reboot, the remote desktop connection fails as apparently X fails to start for lack of a "screen". Removing the keyboard/mouse does not seem to be a problem.
Is there a workaround?
I guess what I'm looking for is the remote desktop behavior from Windows XP/Vista:
1. Connect -> Get logon screen
2. Disconnect -> Session remains active on remote machine and can be reconnected to
I am trying to connect to my Company network through VPN. I use a Lynksys router which is most likely not the problem, as I can get the VPN and Remote Desktop to work from a WinXP Pro laptop connected to the same router. I have tried several RDC clients, none of them establish a connection. The VPN connection is active, I can ping and Traceroute to it , but I cannot get the RDC to work. The RDC should connect to 220.127.116.11 on the company network.
Does anyone know what could be causing a Remote Desktop connection to a 10.04 box to be closing after some period of time? I have three systems all running 10.04 with Remote Desktop enabled. I'm using UltraVNC on Windows 7 to connect to them. If I open a connection and leave it open for a long time (like overnight, for example), when I come back in the morning, I still see the VNC window but as soon as I click on it, it closes. I can immediately open a new connection to the box but it now shows two active connections. At first I was thinking maybe there's an idle timeout value but given that Ubuntu still seems to think that the original connection is active, maybe the problem isn't on the Ubuntu side but on the UltraVNC side?
Is there a way gnome can allow a remote desktop / VNC connection if no user is logged in? If the server gets rebooted I can't access it (remote desktop / VNC). Someone physically has to go there and log in. Surely there must be a way as gnome is running just waiting for a login.
I am using VNC to login to remote machine (vncserver). My question is; How can I login to remote machine (vncserver) through VNC client, without having to login to vncserver first physical. For better explanation here is an example: If john wnat to login to vncserver remotely first he has to login the vncserver physically then he can login remotely.
I have a VPS by my host running on a linux server, and they have given me SSH access. Is it possible to remote desktop into the server, like you can on Windows, so that I can physcially click on things rather than having to use SSH commands?
Surely this must be running on Fedora or Ubuntu etc. so there is some type of OS. You would probably have to install something on the servers end I suppose but just want to know if its possible and what the options are.
I cannot remote desktop to the Debian machine from anywhere,hether within the same network, or on a different network elsewhere. Also, the personal wiki I set up on it to be viewed via a normal web browser cannot be accessed, either. Both time out when attempting to connect to them. I can still ping the Debian machine when on the same network, though.
This started some time ago when we had a failure occur on our main server.had to powercycle everything in order to restore things back to normal, the Debian machine included. Since that time, this problem started to occur. This is a major thorn in my side in attempting to prepare for our website to move,I've been unable to figure out how to fix it.Originally, I thought it would be something in between the Debian machine and anything else, which would mean something like our firewall box or our hardware switch was the problem. But the tech support people who maintain those for us confirm that there is nothing wrong with them, so now I'm not certain anymore.
We have ubuntu server and bind9 installed and setup.When I issue rndc reload or /etc/init.d/bind9 reload I got this:rndc: connection to remote host closedThis may indicate that* the remote server is using an older version of the command protocol,* this host is not authorized to connect,* the clocks are not syncronized, or* the key is invalid.If I issue named-checkconf /etc/bind/named.conf I got this:/etc/bind/named.conf.local:165: unknown key 'rndc-key'I got the key files in the right location but I'm not sure if we even need to use them.
I've been able to use connect to my home laptop from school using VNC (and the Remote Desktop Connection program in f10), but since the graphics take forever to stream, it's almost pointless to use it.Is there any way to connect to my home computer, and ONLY get a Terminal?I've googled around and haven't found a concise way to do this... i'm so confused about how this stuff works (esp how it relates to SSH)
Several of our servers that do not have direct exposure to the Internet have the following entry appearing in their respective /var/log/secure files.Are these messages harmless? If so, is there any way or reason to suppress their appearing in the log files?
I may have to work in another state for some time, and I'd like to access my home machine desktop remotely, like this: Server - home machine, oS 11.4 64-bit, KDE 4.7, 1920 x 1200 screen (currently set to 24-bit color depth), 1 Mbps upload speed, behind a Dlink DL-524 router I manage.
Client: laptop, oS 11.4 64-bit, KDE 4.6.5, 1280 x 800 screen (also 24-bit color depth), unknown up/down speed - probably huge at work, crappy at apart hotel. I'd like to keep the server resolution, if possible, even if the client's is smaller. I want to be able to star/stop KDE apps in the server, move files between folders, and fix the issues that only happen when my wife is at the keyboard (it's a machine conspiracy, she says ). So I'd need to connect to the server's current session/user (which is myself, i.e., same login/password).
What do you recommend for this? I've read Swerdna's tutorial for 11.2/11.2 (a million seen malcomlewis xrdp 0.6 packages for 11.4 (you rock, malcomlewis!), as well as this thread: RDP into OpenSUSE 11.2, however most seem concerned with rdp between windows and linux boxes. Is there something better/faster/simpler for oS-to-oS RDP or should I use xrdp all the same?
how to connect fedora 10 using remote desktop? i have a notebook and a desktop. both machine is in same LAN. and Both machines are using fedora 10. i would like to access my desktop from my notebook. how to do this? i have installed the remote desktop. and vnc viewer. but couldn't get thorugh it...
i have done this. 1. sudo yum install vino 2. intall vnc viewer.
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.
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?
I need to work with other computer. How could i make it? Should I use SSH over VNC, or?... There is a lot of information about it, but, maybe, too much information. I just need to connect to my other desktop. In win i've used TeamViewer. What should i use here?