LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Enterprise (https://www.linuxquestions.org/questions/linux-enterprise-47/)
-   -   how to ssh rhel 6 after reboot (https://www.linuxquestions.org/questions/linux-enterprise-47/how-to-ssh-rhel-6-after-reboot-896477/)

piaakit 08-09-2011 11:23 PM

how to ssh rhel 6 after reboot
 
hi all

i have a rhel 6 machine, everything i reboot the machine from other computer, i can not remote it back even use ssh or vnc, also can not ping the machine's ip, i have to go to the rhel6 machine to login first, and the other computer could ssh and vnc the rhel 6 machine, anyway to prevent this by going to the rhel6 machine to login before other computer could ssh or vnc ? thx

keith

TB0ne 08-10-2011 09:51 AM

Quote:

Originally Posted by piaakit (Post 4438392)
hi all
i have a rhel 6 machine, everything i reboot the machine from other computer, i can not remote it back even use ssh or vnc, also can not ping the machine's ip, i have to go to the rhel6 machine to login first, and the other computer could ssh and vnc the rhel 6 machine, anyway to prevent this by going to the rhel6 machine to login before other computer could ssh or vnc ? thx
keith

Spell out your words, please.

And the way you've described your problem makes no sense. Are you saying that you just have to go to the RHEL6 console, log in, and do NOTHING ELSE, and all your network services then start working? If so, I've never heard of such a thing. Normally such problems are related to an incorrect/invalid network configuration (needing someone to bring up the interface manually), services not being started (again, having to start them manually), or a firewall issue.

What do you do after logging in at the console? And bear in mind that RHEL machines shouldn't have to be rebooted..they're servers, and are designed to run for VERY long periods. Also, RHEL is NOT FREE, and if you're using it, you should be paying for it..part of the benefit of that is you could contact RedHat support. Otherwise, consider loading CentOS instead.

Velenux 08-10-2011 11:17 AM

Is the network configured using NetworkManager?

If it is, you should either check the "available for all users" box on the connection (this will start the connection at boot time) or reconfigure the network with the usual configuration scripts in /etc/sysconfig/network-scripts/

chandhokshashank 09-02-2011 05:53 AM

Quote:

Originally Posted by Velenux (Post 4438859)
Is the network configured using NetworkManager?

If it is, you should either check the "available for all users" box on the connection (this will start the connection at boot time) or reconfigure the network with the usual configuration scripts in /etc/sysconfig/network-scripts/

Velenux

Can you please elaborate tell configuration of Network Manager for "available for all users"?

Thanks

Velenux 09-02-2011 08:54 AM

1 Attachment(s)
Quote:

Originally Posted by chandhokshashank (Post 4459538)
Velenux

Can you please elaborate tell configuration of Network Manager for "available for all users"?

Thanks

There's no much to elaborate :)
See the attachment for a screenshot from Fedora 15 (but RHEL/CentOS/SL config interfaces are quite similar)

attoiu 09-08-2011 06:41 AM

Quote:

Originally Posted by Velenux (Post 4459673)
There's no much to elaborate :)
See the attachment for a screenshot from Fedora 15 (but RHEL/CentOS/SL config interfaces are quite similar)

Hi,

I was on a machine running CentOS 6.0 and checking "Available for all users" didn't help me. It was the "Connect automatically" button that made the difference in my case.

Cheers..

Velenux 09-08-2011 06:14 PM

Quote:

Originally Posted by attoiu (Post 4465789)
Hi,

I was on a machine running CentOS 6.0 and checking "Available for all users" didn't help me. It was the "Connect automatically" button that made the difference in my case.

Cheers..

Oh... ok. I didn't think of that because it's on by default iirc. Anyway, solved :)

netbull 12-29-2011 10:06 AM

Thanks, this worked for me like a charm :)


All times are GMT -5. The time now is 03:49 PM.