Linux - Networking This forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game. |
Notices |
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
|
 |
|
03-18-2007, 06:28 AM
|
#16
|
Member
Registered: Jan 2005
Location: Budapest/Hungary
Distribution: knoppix-hdd/debian
Posts: 56
Rep:
|
resolution
...at me, the same problem occured in a freshly installed linux. The solution was to configure the /etc/hosts.deny because it had by default an
ALL: PARANOID
line in it which prevented me to log in from my notebook (which actually was not having a reverse lookup-enabled domain name - ip address pair).
Anyway, this was the simple problem with it.
For a workaround, when you can't get into your system from a previous DHCP enabled machine try logging onto another server having a fixed IP-DNS pair and try logging onto your server from there possible with much higher success ratio and you can fine tune your /etc/hosts.deny file from there...
BBK
|
|
|
09-18-2007, 07:13 AM
|
#17
|
LQ Newbie
Registered: Sep 2007
Posts: 2
Rep:
|
solution for ssh_exchange_identification problem
I solved this problem. This occured because of changing permissions in /var/ folder.This may be one reseason for you.
so now change permissions to
chmod -R 755 /var/
Now i got resolved this problem.
-Thanks
|
|
|
09-18-2007, 09:29 AM
|
#18
|
Member
Registered: Jul 2007
Distribution: mandrake Mandriva Redhat CentOS Slackware
Posts: 221
Rep:
|
sorry wrong posting.
Last edited by soroccoheaven; 09-18-2007 at 09:30 AM.
|
|
|
09-26-2007, 06:34 PM
|
#19
|
LQ Newbie
Registered: Sep 2007
Posts: 1
Rep:
|
Be careful the /var can has /var/www or other folders that probably will have other permissions.
For get ssh working in my case I just did:
chmod 775 /var/run/sshd
chown root:root /var/run/sshd
/etc/init.d/ssh restart
In my Debian Etch.
|
|
|
09-27-2007, 01:38 AM
|
#20
|
Member
Registered: May 2005
Location: India
Distribution: FC11, Debian/Ubuntu, RHEL, Solaris, AIX, HP-UX
Posts: 161
Rep:
|
ssh login takes time
Some of my RHEL servers tends to respond very slow as we connect through ssh and take longer time to give login prompt. When I get authenticated and log in, it works as usual. Is there any reason for this ?
|
|
|
01-16-2008, 04:58 AM
|
#21
|
LQ Newbie
Registered: Jan 2008
Posts: 1
Rep:
|
Hi!
I had the same problem, then I foun that my /etc/inetd.conf had the following line:
ssh stream tcp nowait root /usr/sbin/tcpd /usr/bin/ssh
I commented the the line, restarted inetd and then it got ok.
|
|
|
05-21-2008, 12:20 PM
|
#22
|
Member
Registered: Nov 2004
Location: india/tamil nadu/chennai
Distribution: Linux 8.0
Posts: 37
Rep:
|
Are you able to login to the server locally using ssh.?
|
|
|
06-08-2008, 02:43 AM
|
#23
|
LQ Newbie
Registered: Jun 2008
Posts: 1
Rep:
|
ALL: PARANOID in /etc/hosts.deny
look and see if ALL: PARANOID in /etc/hosts.deny is uncommented.
|
|
|
06-24-2008, 11:21 AM
|
#24
|
LQ Newbie
Registered: Jun 2008
Posts: 1
Rep:
|
hosts.allow
My configuration had
ALL : PARANOID : deny
in hosts.allow . Removing this line fixed the problem
|
|
|
11-11-2008, 12:34 PM
|
#26
|
LQ Newbie
Registered: Nov 2008
Posts: 1
Rep:
|
Can't SSH to remote machine...
If you can log into the server via console. Try editing the /etc/hosts.allow file and adding:
ALL: 10.
or try adding:
ALL: <your subnet>
as the last line in the file.
|
|
|
07-09-2009, 05:39 AM
|
#27
|
Member
Registered: Dec 2006
Location: NOIDA, India
Distribution: Debian, SUSE, Fedora
Posts: 334
Rep:
|
Cannot set up an ssh tunnel from my localhost to a remote machine.
Hi all:
I am trying to set up an ssh tunnel from my machine (in India) to a server (in US). How do I do it? The problem is: I have to first create a tunnel to Server-1 and then another from Server-1 to Server-2. The point here is: I have to establish a tunnel from my machine to Server-2. Can you please help me establish one?
|
|
|
10-26-2009, 09:58 AM
|
#28
|
LQ Newbie
Registered: Nov 2005
Posts: 4
Rep:
|
Hi avijitp.
The reason it takes a long time to get the login prompt is usually that the host cannot resolve the DNS name of the client, so it waits until to reslove attempt times out and then proceeds. Solve this by making sure the client is resolvable by the DNS that the server connects to, or just manually add the client to the /etc/hosts file - it usually fixes things.
Guess the sshd tryes to resolve the name of the clients for logging purposes or something...
- Karsten
|
|
|
10-26-2009, 10:01 AM
|
#29
|
Member
Registered: May 2005
Location: India
Distribution: FC11, Debian/Ubuntu, RHEL, Solaris, AIX, HP-UX
Posts: 161
Rep:
|
I too had that idea and to test that I have also added the corresponding entry in the /etc/hosts file and it did not help. I tried and verbose option and it waits unusually long at the authorization phase.
|
|
|
11-02-2009, 02:35 PM
|
#30
|
Member
Registered: May 2007
Distribution: RHEL 5, Ubuntu 9.10, Fedora 12
Posts: 85
Rep:
|
Quote:
Originally Posted by bastard23
What's in the logs on the server? It should give a reason.
Check /etc/hosts.allow and /etc/hosts.deny.
|
THANK YOU. Switching subnets and networks in the office and for days couldn't figure out why certain servers were pingable but just dropping ssh packets.
|
|
|
All times are GMT -5. The time now is 10:58 PM.
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|