Debian Configuration :: Remote Connection Timeout Error After 10 15 Second Hang
Jan 18, 2011
I have a windows 7 box and a debian 5.0 box connected to a linksys wrt300n router. I can access the linux box from windows 7 through ssh. I used to be able to access the linux box from outside the LAN, but when I was messing with the ssh port configuration (at least I think this was what happened), i lost my ability to connect. I tried writing a new sshd_config file so that it is much simpler:
Protocol 2
PasswordAuthentication no
UsePAM yes
I tried directly connecting the linux box to the internet to rule out a router firewall issue that i was missing. iptables -L yields nothing, as I have since rebooted the machine since messing with iptables rules. But still, when I try to ssh in from outside the LAN, I get a connection timeout error after a 10-15 second hang.
I have a Debian VPS running Lenny and I'm trying to setup a way to run remote desktop sessions from it. I went with FreeNX, NX client for windows from nomachine, XDM and xfce4. All seems to have installed well, but I can't start an NX session on my box. I can connect to the server and authenticate, but the client hangs on "Downloading the session information," eventually timing out. The log output is below - I'm not even seeing an error message. Any ideas?
[Code]...
The only thing I noticed during install, which was about 400 packages since this was a barebones VPS, was that I should consider recompiling the kernel with CONFIG_SOFTWARE_SUSPEND=y. I don't know if this has any impact on session information, however, since this is a new session, not one I'm trying to resume.
im on node1 when i type the command ssh node2@ip the terminal hangs up a bit then an error message stating that connection timeout but here is a thing: i cant ping to node2 but i can terminate the ping manually using ctrl+c when i terminate the ping usual message appears stating 10 packets transmitted, 100% loss
ps: when i go to node3 and ssh to node2 it works fine and also i can ping from node3 to node2 very fine. and the firewalls are down at all nodes -all wired connection over a switch
I have a PC104 running debian. I have 3 hard drives (in addition to the one booting) mounted in fstab by UUID. I use the options defaults,error=remount-ro. However, this means that when I boot with the hard drives not attached, I have to press Ctrl-D to bypass when the boot discovers the drives are missing. Is there a timeout commandoption I can add to fstab so that it automatically continues booting even if the hard drives are not attached? I could not find anything on a timeout command. (I tried adding timeout=1000 but no-random guess)
type the command ssh node2@ip the terminal hangs up a bit then an error message stating that connection timeout but here is a thing: i cant ping to node2 but i can terminate the ping manually using ctrl+c when i terminate the ping usual message appears stating 10 packets transmitted, 100% loss ps: when i go to node3 and ssh to node2 it works fine and also i can ping from node3 to node2 very fine. and the firewalls are down at all nodes
I am running debian 8 stable version (which I starting to think not that "Stable") and when i surf web pages its ok except the fact that I am too often get connection timeouts then i need to press "enter" in the ur box to try again and then its maybe work if not I am going to press another "enter" on the url box until i have connection to the site its important to say its not a isp or hardware problem. I run the web with no problems in that other operating system which I am not getting back to.....
If I shutdown from X the system hangs and I have to yank out the power cord. Same on logout.
ctrl+alt+f1 hangs for a few minutes and then starts a terminal; which does not respond to the keyboard.
There are no tty.conf files in /etc/init .
But inittab looks normal to me and includes tty (1-6)
Executing init 6 from a terminal in X will reboot the system
I was thinking this might be a dbus issue, but I am not sure. I also understand some recent issues exist with SysRq sequences. May be a video card issue,,,
Other than normal package upgrades the only changes were a recent change from a VGA to HDMI cable. I can't see why that would matter
Linux Lugh 3.2.0-4-amd64 #1 SMP Debian 3.2.68-1+deb7u2 x86_64 GNU/Linux
I'm using Debian 8.2 from a very recent download of the latest NetInst (less than 2 weeks). I'm sort of new to Linux - More accurately, I've used Unix and Linux extensively in the past, so most of my knowledge is dated. In particular, the whole systemd / systemctl paradigm is completely new to me.
Problem: I've added an entry to /etc/fstab to mount a NAS drive as CIFS. When I do a system shutdown or reboot, the system hangs for 90 seconds trying to unmount the NAS. If I manually umount the NAS prior to shutdown / reboot everything works fine.
I've done a fair amount of investigation and web searches, but haven't found a fix yet. Apparently several people were encountering similar problems about a year back, and it seems pretty clear that the root cause what ordering of steps in the shutdown process, e.g., WLAN being turned off before unmounting filesystems. This seems to have been resolved for most users (no one is discussing it any more), but I'm now running into the same issue. Ugh.
I tried to add a shell script to /etc/rc0.d to umount the NAS first in the shutdown process. This had no effect. I assume this is because the new systemd / systemctl paradigm supplants the old /etc/rc model of runlevel control, though it is rather baffling (to me, at least) as to why /etc/rc* still exists if the system is no longer using it...?
Here's some things I'd like to try, but how to proceed:
1. In the new systemd / systemctl paradigm, how do I examine and change the ordering of steps in the shutdown process? I've seen a lot of documentation on systemd, but nothing tells me how to do what I used to be able to do with /etc/rc with a simple rename of a symlink. If I knew how to look at the order of shutdown and change that ordering, I'm fairly certain I could identify and resolve this issue.
2. Is there some other way to mount my CIFS NAS other than editing /etc/fstab? Is it possible that my manual edit to /etc/fstab is the cause of this issue? My research into systemd indicates that it IS supposed to be compatible with /etc/fstab. I have not yet found documentation describing how to mount a filesystem at boot WITHOUT editing /etc/fstab ...
My system is hanging on screen suspension... And its not the usual hang on "sleep" or others similars, it will happen by only having the screen on stand-by ( eg xset +dpms)...
If I leave for a while the screen will shutdown as expected but computer will completely hang after an indefinite time, it will not respond to outside connections and the will be spinning faster than usual...
Only workaround is to have the screen power save option disabled, in my case, on the KDE settings...
I have tried the most common solution to have "nomodeset" as a kernel option to disable mode setting, but this doesn't seem to work...
Also tried to forcebly reproduce the issue with Code: Select allxset force dpms standby/suspend/off but nothing happens like that...
This issue also only appears with the fglrx driver, open-source works well.
1 linksys router: gets the net from PPPOE and give the network DHCP. The router IP is 192.168.1.1. 1 windows laptop that work wireless and wired. 1 debian desktop that work wired and not working wireless. THe problem with the debian desktop is like this: I have a TP-Link TL-WN321G installed and found by lsusb command. I make a wireless connection WPA Personal (just like the router settings) it says i am connected to the wl network but no internet connection. the route command give me this:
[code]....
I tryed with wicd who said that the connection is WEP (and it's not, it is setup to WPA on the router and the network-manager conncetion) and when i try to connect i get bad password. I tryed with network-manager uninstalled and no chance.
The situation: The office has a WiFi network on one DSL line, which is used for our VoIP call center, and a wired network for our internal network and the majority of web surfing/traffic . Part of the office must be temperature controlled/monitored - we have a rather nice digital thermometer which is WiFi enabled.I have a Debian Wheezy box with a WiFi card and ethernet connection
What I'm trying to accomplish:Connect wifi enabled thermometer to WiFi network so it can automatically send temp updates (currently I have to do it manually via USB)Have the Wheezy box accept the downloaded file then send it to a back up server in the wired network
Side things that may be useful : Prefer to use wired connection for internet and apt and suchWiFi connection will really just be used for connecting to the thermometer
This [URL] .... topic got me thinking that there might be a way to bring the two networks together, but I don't know if that will wreak havoc on things. I know, the Windows and Mac OS don't like having ethernet and wifi at the same time, might Linux be better for this?
v&n had this to offer in the prior thread [URL] .... which I'll be doing more research on.
I have local and remote networks that have various printers. I can add any printer (local or remote) to any PC, except for one PC that's refusing to allow remote connection (it used to, but doesn't now!). The problem PC has two printers connected and work OK as a local printer, but both display same problem when attempting to connect from any remote PC via YaST. Using 'Connection Wizard> CUPS Server' connection method requires IP address of remote PC and printer name. But if I correctly select either of the two printers I get an error message:
"PING 192.168.1.149 (192.168.1.149) 56(84) bytes of data. 64 bytes from 192.168.1.149: icmp_seq=1 ttl=64 time=1.12 ms
Both printers are set to 'Accept Print Jobs' and 'Share Printers> Allow remote access' permits all networks to connect. why this PC is requiring the root password?
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?
I'm trying to connect with my server via telnet, but when i sent the command (telnet xxx.xxx.xxx.xxx Port) doesn't works and shows then follow error: Unable to connect to remote host: Connection refused, It happens with any port. Is strange but my telnet services works (telnet xxx.xxx.xxx.xxx), In addition, i tried with firewall enabled and disabled and the problem still happens. My centOS run on virtualbox.
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.
I have a bit of an odd network setup, shown in the pic here:I am trying to remote desktop from the XP boxes on the side to the one on the bottom, behind a Debian box/firestarter firewall. Is this possible to do without changing my network (IE wiring/topology) setup? If I had my druthers, I would put the router behind the Linux box, before the XP box, but my work laptop does not allow me to connect in that fashion as I can't change the internet settings.
I am certain the setup is correct on both the Windows clients and host, so it has to be something with my firestarter firewall, or something else I'm completely missing. I have the RDP port opened on firestarter, but whenever I try to connect to the XP box, whether it's by computer name or LAN IP address, it is unable to connect. I had thought about setting up a VPN server on my Debian box, and then VPN'ing to it, and then in turn RDC'ing to my Windows machine. Is this possible? If all else fails, I may just plug the Windows box directly into the router and deal with the lower security or get a second wireless router just for my work pc.
I want to connect to my Linux debian server, via Remote desktop connection, but when I give IP of my server and click connect, it fail, it says can't connect to the remote computer and below 3 reason.
Upgraded webserver to Jessie as an upgrade to Wheezy produced errors, and before reboot everything was up and running, but as all upgrade docs and info I read, I rebooted the server. However it never came back. I have the original backup files before I did the Wheezy upgrade. I also have access by Rescue to the server.Made a back up of critical files and have a 24GB tar file and I can connect by SFTP.
how to check the Debian files... Grub etc.. I would prefer to find the issue than start again.I am not able to sudo from Putty. I cannot run apt-get update. I did go to chroot, but then I get unable to resolve host errors and Could not open lock file because Permission denied errors and asking if I am root.There is information by googling for start up issues, but as I am working remotely with a Rescue set up, a lot of the commands I see and have tied do not work.
I'm trying to get an laptop running more or less like a headless server, my reasons are not all that serious. Mostly I want to leave the laptop running as a seed box when my main PC is turned off, also want to setup it up as a media top, common place for media files and playback on Tv. So essentially I want to be able to access the remote machine, preferably sharing the same session and persisting while I log out from remote.
What I've done: setup keys for ssh to connect automatically between machines, so I can login via terminal, access the file system without issues, which is already a great step. enabled remote access on remote machine lightdm manager setup deluge for daemon torrenting, which enables almost seamlessly client to connect remotely (though deluge is not the best with speed)
What I've tried so far: Connect directly with a new X session Code: Select allX -query your_server_ip :1
Works alright, creates a new display (:1) which is oddly in F2 tty instead F8 as is expected. Works alright, not much lag, audio is not routed.
But an issue! whenever I decide to log out X will simply shutdown, screen goes black and I can't resume on my regular session on my local machine.Connect X with nested Xephyr session
This works too and might be the best solution yet, a windows is created and the remote session is nested in your current X session. Visual and performance is ok. Only real issue is that session is not shared, eg, application will not remain running...Connect via VNC
So it seems only solution for shared sessions is VNC.
With the remote desktop apps from KDE (which is the DE for both), I can connect buzz around and etc, but its kinda cumbersome and laggy, password always resets and I usually need to accept on the remote machine.
I've tried setting up lightdm to allow a vncserver at logon, but this is erratic at best, took a long time to get the Xvnc command correct enough for me to login remotely, and even then got a garbled screen and the X session wasn't even the same...
So that's it... Isn't there a way of regular X session sharing in the remote computer? Or a better solution for lightdm vnc invoke?
I have two remote systems which I have fstab entries for on the local system. I have them set to noauto, because mount fails during boot for some reason, but that's not the problem. For years I've mounted them in rc.local.
The problem is after I recently reinstalled Debian, when I mount them manually it always asks for my user's password. I've copied my user's pub key from the local to the remote system and put it in the user authorized_keys file (not root), like I always have. But it still asks for a password, and so fails to mount in rc.local.
I have just setup a debian box, and I want to be able to login to the machine remotely.Currently I have the following setup:Cable Modem -> Netgear Router (DHCP to outside world) -> Debian Box (DHCP for internal network)As I under stand it I have to set my Debian Box to use a static IP, but from there I di not know where to go.Also since my cable modem IP is dynamic, is there some way to have that the debian box get the IP address for the outside world, and e-mail it to my gmail account when it changes, or least every X hours?
If i got gnome i may go to the top-panel: choose system, choose preferences and go to "remote desktop" and make my settings (allow, ask for allow, password, and other stuff). I don't want to be bound to gnome (though i like it, thats not the problem).Which config-files are the ones i am looking for?
I did search the web, but i can't find useful how-to's, explanations, etc.Cause what i find is related to the path i described above (gnome: top-panel, preferences...)Which is the app/tool which pops up and says:"someone wants to access, you want to allow it, yes or no?". The performance of VNC is lousy comopared to NX. Lousy is the friendly version. What might i be doing wrong?i usually do it from a Debian-host to a VirtualBox-guest.I am mainly asking for how-to's/docus and stuff like that. Links. Explanations are welcome too. Of course.
I've gotten VNC setup and working well on our LAN. The next step we want to do is making it acessible from the web, so we can remotely do things with the office files.Unfortunately, I have no idea how to go about this.Our current setup is a router which connects to the phone line, and into which other devices are connected. We're in one room of a big office building which may complicate matters somewhat.Can anyone provide a bit of general info on this topic. Give me somewhere to start ?Ultimately we want to be able to connect to the vnc port from anywhere in the world.
I've got a fresh Wheezy/Xfce install.I'm trying to access a remote samba share the gigolo way. It is an external USB hard drive connected to my router. I can access it read only using the following URL with Icedove: smb://bbox/
Anyway, this is just to try and give might-be-useful information, but ultimately, I don't really want to use fusesmb. I would rather have the gigolo way working, allowing local network shares browsing, auto-connect, etc.
I am trying to set up an ssh server on my Debian squeeze box so that I can access it remotely when I'm not at home. I connect to the internet through an at&t 2wire modem/router. First off, I *can* ssh into the machine from inside the local network, e.g.
[Code]...
Nmap done: 1 IP address (1 host up) scanned in 2.12 seconds Playing around with Nmap, I also found that it only sees port 50001 as open.
I am using samba 3.0 on rhel-4, it works fine i am getting the share folder in linux and windows xp as well with username and password for first time only then for next time it will not ask me the username and password for samba user. Actually i want to fix idle-timeout and password authentication for user every time the user want to access the samba share folder.
Kernel: Linux 2.6.26-2-686 (i686) Compiled: #1 SMP Thu Nov 25 01:53:57 UTC 2010 C Library: GNU C Library version 2.7 (stable) Distribution: Debian GNU/Linux 5.0.8 Desktop Environment: GNOME 2.20
Gnome comes with Vino Remote Desktop as part of it's package. I want Vino to run at boot so that I can login remotely.I am using VNC-4.1.3 for remote viewing. However, I can only view remotely once I have logged-in locally
