Home > OS >  Ask, I have three centos virtual machine, there is a can't SSH remote login
Ask, I have three centos virtual machine, there is a can't SSH remote login

Time:09-19

Two virtual machine is cloned, three of the 101102103, respectively, their IP is static, 101103 can xhell remote login, 102 IP is set to 192.168.1.102 can't remote login but can ping, set to the other can (e.g., 192.168.1.104,), if have to use the IP 102, how should be broken, firewalls determine have closed, after clone host name, network card has been modified, is really don't know what the IP made public anger!!!!!!

CodePudding user response:

Are you sure 102 address without conflict

CodePudding user response:

When you set to 102, restart the network service, IP add in the unit to see not get IP address

CodePudding user response:

reference 1st floor weixin_40290083 response:
are you sure the address of the 102 without conflict

I don't think so, can you ping 102, three virtual machine can SSH login to each other, this morning I open the computer, the network card custom into vmnat8, good, with NAT model has become, don't know what reason

CodePudding user response:

reference 1st floor weixin_40290083 response:
are you sure the address of the 102 without conflict

Thank you, three virtual machine configuration are the same, I don't know 102 machine is not good again now what happened

CodePudding user response:

Just try again once, wired connection there appeared auto eth0 and system eth0, I put the card uninstall reshipment, restart, the auto eth0 exactly what happened

CodePudding user response:

refer to the original poster Teddy_up response:
two virtual machine is cloned, three of the 101102103, respectively, their IP is static, 101103 can xhell remote login, 102 IP is set to 192.168.1.102 can't remote login but can ping, set to the other can (e.g., 192.168.1.104,), if have to use the 102 IP, how should be broken, firewalls determine have closed, after clone host name, network card has been modified, is really don't know what the IP made public anger!!!!!!

You see there is no other equipment in the local area network (LAN) with 102 IP, should be to the situation you described the IP conflict, reinstall the reason is you this virtual machine to another device IP covers, I also met this problem before

CodePudding user response:

refer to 6th floor response: hflxhn.com
Quote: refer to the original poster Teddy_up response:
two virtual machine is cloned, three of the 101102103, respectively, their IP is static, 101103 can xhell remote login, 102 IP is set to 192.168.1.102 can't remote login but can ping, set to the other can (e.g., 192.168.1.104,), if have to use the IP 102, how should be broken, firewalls determine have closed, after clone host name, network card has been modified, is really don't know what the IP made public anger!!!!!!

You see there is no other equipment in the local area network (LAN) with 102 IP, should be to the situation you described the IP conflict, reinstall the reason is you this virtual machine to another device IP covers, I also met this problem before

Thank you, I don't know why and wireless network card conflict over there,

CodePudding user response:

Thank you, my is wireless IP and the conflict of the virtual machine, when I first turn off the wireless again even now, if not, please change the virtual machine IP if there is no other way to solve the problem of conflict

CodePudding user response:

refer to 6th floor response: hflxhn.com
Quote: refer to the original poster Teddy_up response:
two virtual machine is cloned, three of the 101102103, respectively, their IP is static, 101103 can xhell remote login, 102 IP is set to 192.168.1.102 can't remote login but can ping, set to the other can (e.g., 192.168.1.104,), if have to use the IP 102, how should be broken, firewalls determine have closed, after clone host name, network card has been modified, is really don't know what the IP made public anger!!!!!!

You see there is no other equipment in the local area network (LAN) with 102 IP, should be to the situation you described the IP conflict, reinstall the reason is you this virtual machine to another device IP covers, I also met this problem before

Thank you, my is wireless IP and the conflict of the virtual machine, when I first turn off the wireless again even now, if not, please change the virtual machine IP if there is no other way to solve the problem of conflict?

CodePudding user response:

references 9 f Teddy_up response:
Quote: refer to the sixth floor response: hflxhn.com
Quote: refer to the original poster Teddy_up response:
two virtual machine is cloned, three of the 101102103, respectively, their IP is static, 101103 can xhell remote login, 102 IP is set to 192.168.1.102 can't remote login but can ping, set to the other can (e.g., 192.168.1.104,), if have to use the IP 102, how should be broken, firewalls determine have closed, after clone host name, network card has been modified, is really don't know what the IP made public anger!!!!!!

You see there is no other equipment in the local area network (LAN) with 102 IP, should be to the situation you described the IP conflict, reinstall the reason is you this virtual machine to another device IP covers, I also met this problem before

Thank you, my is wireless IP and the conflict of the virtual machine, when I first turn off the wireless again even now, if not, please change the virtual machine IP if there is no other way to solve the problem of conflict?

Notebook wireless card? The wireless network card IP to other

CodePudding user response:

references 9 f Teddy_up response:
Quote: refer to the sixth floor response: hflxhn.com
Quote: refer to the original poster Teddy_up response:
two virtual machine is cloned, three of the 101102103, respectively, their IP is static, 101103 can xhell remote login, 102 IP is set to 192.168.1.102 can't remote login but can ping, set to the other can (e.g., 192.168.1.104,), if have to use the IP 102, how should be broken, firewalls determine have closed, after clone host name, network card has been modified, is really don't know what the IP made public anger!!!!!!

You see there is no other equipment in the local area network (LAN) with 102 IP, should be to the situation you described the IP conflict, reinstall the reason is you this virtual machine to another device IP covers, I also met this problem before

Thank you, my is wireless IP and the conflict of the virtual machine, when I first turn off the wireless again even now, if not, please change the virtual machine IP if there is no other way to solve the problem of conflict?

And a method to modify the router's DHCP pool allocations, distributing the pool to the range of 120-200, anyhow don't and you common conflict is the net broken

CodePudding user response:

Uh huh, notebook wireless, can't change wow, changed will not be able to use, and I changed my fixed cannot use

CodePudding user response:

Hflxhn.com
reference 11 floor response:
Quote: references 9 f Teddy_up response:
Quote: refer to the sixth floor response: hflxhn.com
Quote: refer to the original poster Teddy_up response:
two virtual machine is cloned, three of the 101102103, respectively, their IP is static, 101103 can xhell remote login, 102 IP is set to 192.168.1.102 can't remote login but can ping, set to the other can (e.g., 192.168.1.104,), if have to use the IP 102, how should be broken, firewalls determine have closed, after clone host name, network card has been modified, is really don't know what the IP made public anger!!!!!!

You see there is no other equipment in the local area network (LAN) with 102 IP, should be to the situation you described the IP conflict, reinstall the reason is you this virtual machine to another device IP covers, I also met this problem before

nullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnull