| *SOLVED* Cant login to VE via SSH [message #6302] |
Wed, 13 September 2006 20:23  |
dreamwiz
Messages: 11
Registered: September 2006
|
Junior Member |
|
|
Hi!
I have installed OpenVZ recently and I have now created few VE's and given them public IP. Everything has went well, except that I can not login to VE via SSH. I make connection it asks for username and password, after entering it says "access denied". I have checked SSH config, I have doublechecked the passwords...
Other funny thing is that I cant use internet (not even ping anything) from the VE, but I can still try to SSH into it from outside?
I have checked that my hardware node has a different IP address. Any ideas?
[Updated on: Mon, 18 September 2006 07:33] by Moderator Report message to a moderator |
|
|
|
|
|
|
|
|
|
| Re: Cant login to VE via SSH [message #6312 is a reply to message #6309] |
Wed, 13 September 2006 22:35  |
dreamwiz
Messages: 11
Registered: September 2006
|
Junior Member |
|
|
| Chris.S wrote on Thu, 14 September 2006 01:23 |
did you change your sysctl config file like it says to do?
|
Yep, here's 2 different that I have tried (2 different because I wasnt sure if the existing one was supposed to be modified or replaced with the one in the installation manual):
---
# Kernel sysctl configuration file for Red Hat Linux
#
# For binary values, 0 is disabled, 1 is enabled. See sysctl( and
# sysctl.conf(5) for more details.
# Controls IP packet forwarding
net.ipv4.ip_forward = 1
net.ipv4.conf.default.proxy_arp = 0
# Controls source route verification
net.ipv4.conf.default.rp_filter = 1
# Do not accept source routing
net.ipv4.conf.default.accept_source_route = 0
# Controls the System Request debugging functionality of the kernel
kernel.sysrq = 1
# Controls whether core dumps will append the PID to the core filename.
# Useful for debugging multi-threaded applications.
kernel.core_uses_pid = 1
net.ipv4.conf.default.send_redirects = 1
net.ipv4.conf.all.send_redirects = 0
-------
and
-------
# Kernel sysctl configuration file for Red Hat Linux
#
# For binary values, 0 is disabled, 1 is enabled. See sysctl( and
# sysctl.conf(5) for more details.
# Controls IP packet forwarding
net.ipv4.ip_forward = 1
net.ipv4.conf.default.proxy_arp = 0
# Controls source route verification
net.ipv4.conf.default.rp_filter = 1
# Do not accept source routing
net.ipv4.conf.default.accept_source_route = 0
# Controls the System Request debugging functionality of the kernel
kernel.sysrq = 1
# Controls whether core dumps will append the PID to the core filename.
# Useful for debugging multi-threaded applications.
kernel.core_uses_pid = 1
net.ipv4.conf.default.send_redirects = 1
net.ipv4.conf.all.send_redirects = 0
# Kernel sysctl configuration file for Red Hat Linux
#
# For binary values, 0 is disabled, 1 is enabled. See sysctl( and
# sysctl.conf(5) for more details.
# Controls IP packet forwarding
net.ipv4.ip_forward = 1
net.ipv4.conf.default.proxy_arp
# Controls source route verification
net.ipv4.conf.default.rp_filter = 1
# Enables source route verification
net.ipv4.conf.all.rp_filter = 1
# Do not accept source routing
net.ipv4.conf.default.accept_source_route = 0
# Controls the System Request debugging functionality of the kernel
kernel.sysrq = 1
# Controls whether core dumps will append the PID to the core filename.
# Useful for debugging multi-threaded applications.
kernel.core_uses_pid = 1
net.ipv4.tcp_syncookies = 1
net.ipv4.tcp_synack_retries = 2
net.ipv4.conf.default.send_redirects = 1
net.ipv4.conf.all.send_redirects = 0
[Updated on: Wed, 13 September 2006 22:36] Report message to a moderator |
|
|
|
|
|
|
|
|
|
|
|
| Re: Cant login to VE via SSH [message #6442 is a reply to message #6346] |
Mon, 18 September 2006 07:33 |
Vasily Tarasov
Messages: 1345
Registered: January 2006
|
Senior Member |
|
|
during PMing the problem was solved. Reason: some node in the net had the same IP address. From dreamwiz:
| Quote: |
I figured it out - my dc had assigned the ip's to the server automatically. To make a quick fix, I just ordered new set of unassigned ip's and now I can login through SSH just fine. Thanks for your assistance!
|
|
|
|
|
OpenVZ Forum
Members
Search
Help
Register
Login
Home
