Error connecting Cannot connect to host xxx.com. A connection attempt failed

[totalenginesupp]

Hi All,

I am running Virtual Center 2.5 and have 2 ESX Hosts managed. I can console without any issues on ESX Host 2, but when trying to console onto any Virtual Machine on ESX Host 1 I get the error message:

'Error connecting: Cannot connect to host xxx.com: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. Do you want to try again?

We have had no issues up to now, so seems strange why we suddenly cannot connect.

I have tried going onto the console of the Host and using the command service mgmt-vmware restart as suggested but this has not cured the problem.

I have tried a tracert and the IP address is resolved correctly.

Nothing has changed in terms of switch configs, NIC cards etc.

Any suggestions?

Andy

[athlon_crazy]

have you try to restart vmware-vmkauthd service?

VMware newbie..

Zen Systems Sdn Bhd

www.no-x.org

[totalenginesupp]

Hi,

thanks, do you do this on the console, would the command be service vmware-vmkauthd restart

Andy

[athlon_crazy]

yep or

/etc/init.d/vmware-vmkauthd restart

VMware newbie..

Zen Systems Sdn Bhd

www.no-x.org

[totalenginesupp]

Hi I have tried this command and still the problem exists. Thanks for trying with this option. Any other ideas?

Thanks,

Andy

[athlon_crazy]

Any error from /var/log/secure?

VMware newbie..

Zen Systems Sdn Bhd

www.no-x.org

[totalenginesupp]

How do I check this? Sorry I am a complete new bod this this, only been using it for 14 days.

[athlon_crazy]

cat /var/log/secure or

tail -n 100 /var/log/secure

VMware newbie..

Zen Systems Sdn Bhd

www.no-x.org

[totalenginesupp]

Here is a sample from the command cat /var/log/secure

e-e007-6db1-ac31e83ef6ea

Jun 18 15:43:56 tes-esx1 vmware-authd[3017]: Found vmkauthd: /usr/lib/vmware/bin /vmware-vmkauthd-start

Jun 18 15:43:56 tes-esx1 vmware-authd[3017]: Redirected mks to 10.0.0.205:903

Jun 18 15:44:27 tes-esx1 xinetd[2309]: START: vmware-authd pid=3049 from=10.0.0. 7

Jun 18 15:44:27 tes-esx1 vmware-authd[3049]: login from 10.0.0.7 as 525a52c2-49b 8-a077-3521-51bc3be551b4

Jun 18 15:44:27 tes-esx1 vmware-authd[3049]: Found vmkauthd: /usr/lib/vmware/bin /vmware-vmkauthd-start

Jun 18 15:44:27 tes-esx1 vmware-authd[3049]: Redirected mks to 10.0.0.205:903

Jun 18 15:44:58 tes-esx1 xinetd[2309]: START: vmware-authd pid=3082 from=10.0.0. 7

Jun 18 15:44:59 tes-esx1 vmware-authd[3082]: login from 10.0.0.7 as 52a098f7-f85 b-250c-4ca5-9a2e06b54ada

Jun 18 15:44:59 tes-esx1 vmware-authd[3082]: Found vmkauthd: /usr/lib/vmware/bin /vmware-vmkauthd-start

Jun 18 15:44:59 tes-esx1 vmware-authd[3082]: Redirected mks to 10.0.0.205:903

Jun 18 15:45:30 tes-esx1 xinetd[2309]: START: vmware-authd pid=3114 from=10.0.0. 7

Jun 18 15:45:30 tes-esx1 vmware-authd[3114]: login from 10.0.0.7 as 527d4a4d-b43 7-8520-6e03-23b56b0cecf2

Jun 18 15:45:30 tes-esx1 vmware-authd[3114]: Found vmkauthd: /usr/lib/vmware/bin /vmware-vmkauthd-start

Jun 18 15:45:30 tes-esx1 vmware-authd[3114]: Redirected mks to 10.0.0.205:903

Jun 18 15:46:01 tes-esx1 xinetd[2309]: START: vmware-authd pid=3146 from=10.0.0. 7

Jun 18 15:46:01 tes-esx1 vmware-authd[3146]: login from 10.0.0.7 as 52ef51b7-f9a 9-2974-f276-ea6307325eff

Jun 18 15:46:01 tes-esx1 vmware-authd[3146]: Found vmkauthd: /usr/lib/vmware/bin /vmware-vmkauthd-start

Jun 18 15:46:01 tes-esx1 vmware-authd[3146]: Redirected mks to 10.0.0.205:903

Jun 18 15:46:32 tes-esx1 xinetd[2309]: START: vmware-authd pid=3178 from=10.0.0. 7

Jun 18 15:46:33 tes-esx1 vmware-authd[3178]: login from 10.0.0.7 as 52a3631c-e90 d-d21e-fed7-a91cbc718c83

Jun 18 15:46:33 tes-esx1 vmware-authd[3178]: Found vmkauthd: /usr/lib/vmware/bin /vmware-vmkauthd-start

Jun 18 15:46:33 tes-esx1 vmware-authd[3178]: Redirected mks to 10.0.0.205:903

Jun 18 15:47:04 tes-esx1 xinetd[2309]: START: vmware-authd pid=3210 from=10.0.0. 7

Jun 18 15:47:04 tes-esx1 vmware-authd[3210]: login from 10.0.0.7 as 52098d38-35a 8-73e8-181e-f7a422a508b8

Jun 18 15:47:04 tes-esx1 vmware-authd[3210]: Found vmkauthd: /usr/lib/vmware/bin /vmware-vmkauthd-start

Jun 18 15:47:04 tes-esx1 vmware-authd[3210]: Redirected mks to 10.0.0.205:903

Jun 18 15:49:03 tes-esx1 xinetd[2309]: START: vmware-authd pid=3336 from=10.0.0. 7

Jun 18 15:49:03 tes-esx1 vmware-authd[3336]: login from 10.0.0.7 as 52c13169-ec7 b-6120-5685-2f5f7ddab2cf

Jun 18 15:49:04 tes-esx1 vmware-authd[3336]: Found vmkauthd: /usr/lib/vmware/bin /vmware-vmkauthd-start

Jun 18 15:49:04 tes-esx1 vmware-authd[3336]: Redirected mks to 10.0.0.205:903

Jun 18 15:49:25 tes-esx1 xinetd[2309]: START: vmware-authd pid=3337 from=10.0.0. 7

Jun 18 15:49:25 tes-esx1 vmware-authd[3337]: login from 10.0.0.7 as 5288b76d-041 f-3e42-1ad7-53a5b3514525

Jun 18 15:49:25 tes-esx1 vmware-authd[3337]: Found vmkauthd: /usr/lib/vmware/bin /vmware-vmkauthd-start

Jun 18 15:49:25 tes-esx1 vmware-authd[3337]: Redirected mks to 10.0.0.205:903

Jun 18 15:49:53 tes-esx1 xinetd[2309]: START: vmware-authd pid=3369 from=10.0.0. 7

Jun 18 15:49:53 tes-esx1 vmware-authd[3369]: login from 10.0.0.7 as 52fd2979-e98 e-610a-af8c-3fb24bc22ef5

Jun 18 15:49:53 tes-esx1 vmware-authd[3369]: Found vmkauthd: /usr/lib/vmware/bin /vmware-vmkauthd-start

Jun 18 15:49:53 tes-esx1 vmware-authd[3369]: Redirected mks to 10.0.0.205:903

Jun 18 15:51:20 tes-esx1 xinetd[2309]: START: vmware-authd pid=3464 from=10.0.0. 7

Jun 18 15:51:20 tes-esx1 vmware-authd[3464]: login from 10.0.0.7 as 52c9a6d9-230 7-b69c-b215-ea32d4516f6e

Jun 18 15:51:20 tes-esx1 vmware-authd[3464]: Found vmkauthd: /usr/lib/vmware/bin /vmware-vmkauthd-start

Jun 18 15:51:20 tes-esx1 vmware-authd[3464]: Redirected mks to 10.0.0.205:903

Jun 18 15:51:54 tes-esx1 xinetd[2309]: START: vmware-authd pid=3507 from=10.0.0. 7

Jun 18 15:51:54 tes-esx1 vmware-authd[3507]: login from 10.0.0.7 as 52bd3662-d66 b-5e78-a663-3e6ade4de7ed

Jun 18 15:51:54 tes-esx1 vmware-authd[3507]: Found vmkauthd: /usr/lib/vmware/bin /vmware-vmkauthd-start

Jun 18 15:51:54 tes-esx1 vmware-authd[3507]: Redirected mks to 10.0.0.205:903

Jun 18 15:52:25 tes-esx1 xinetd[2309]: START: vmware-authd pid=3539 from=10.0.0. 7

Jun 18 15:52:25 tes-esx1 vmware-authd[3539]: login from 10.0.0.7 as 520529ee-965 d-6565-a29f-09c65a3d5cf4

Jun 18 15:52:25 tes-esx1 vmware-authd[3539]: Found vmkauthd: /usr/lib/vmware/bin /vmware-vmkauthd-start

Jun 18 15:52:25 tes-esx1 vmware-authd[3539]: Redirected mks to 10.0.0.205:903

Jun 18 15:52:56 tes-esx1 xinetd[2309]: START: vmware-authd pid=3581 from=10.0.0. 7

Jun 18 15:52:57 tes-esx1 vmware-authd[3581]: login from 10.0.0.7 as 52534a3d-6a5 3-cb0a-51e3-2d2fb58863fe

Jun 18 15:52:57 tes-esx1 vmware-authd[3581]: Found vmkauthd: /usr/lib/vmware/bin /vmware-vmkauthd-start

Jun 18 15:52:57 tes-esx1 vmware-authd[3581]: Redirected mks to 10.0.0.205:903

Jun 18 15:53:28 tes-esx1 xinetd[2309]: START: vmware-authd pid=3613 from=10.0.0. 7

Jun 18 15:53:28 tes-esx1 vmware-authd[3613]: login from 10.0.0.7 as 525da8ce-6ca 5-58c4-b5b6-689812fee3b5

Jun 18 15:53:28 tes-esx1 vmware-authd[3613]: Found vmkauthd: /usr/lib/vmware/bin /vmware-vmkauthd-start

Jun 18 15:53:28 tes-esx1 vmware-authd[3613]: Redirected mks to 10.0.0.205:903

Jun 18 15:53:59 tes-esx1 xinetd[2309]: START: vmware-authd pid=3645 from=10.0.0. 7

Jun 18 15:53:59 tes-esx1 vmware-authd[3645]: login from 10.0.0.7 as 52aa304f-515 9-f9c1-f739-80c68eada0a9

Jun 18 15:53:59 tes-esx1 vmware-authd[3645]: Found vmkauthd: /usr/lib/vmware/bin /vmware-vmkauthd-start

Jun 18 15:53:59 tes-esx1 vmware-authd[3645]: Redirected mks to 10.0.0.205:903

Jun 18 15:54:30 tes-esx1 xinetd[2309]: START: vmware-authd pid=3677 from=10.0.0. 7

Jun 18 15:54:30 tes-esx1 vmware-authd[3677]: login from 10.0.0.7 as 520ce7ee-149 b-aa7b-b314-4071d8dd5257

Jun 18 15:54:30 tes-esx1 vmware-authd[3677]: Found vmkauthd: /usr/lib/vmware/bin /vmware-vmkauthd-start

Jun 18 15:54:30 tes-esx1 vmware-authd[3677]: Redirected mks to 10.0.0.205:903

Jun 18 15:55:49 tes-esx1 xinetd[2309]: START: vmware-authd pid=3772 from=10.0.0. 7

Jun 18 15:55:49 tes-esx1 vmware-authd[3772]: login from 10.0.0.7 as 521ad466-7f6 a-84a7-4a56-806e735bafd2

Jun 18 15:55:50 tes-esx1 vmware-authd[3772]: Found vmkauthd: /usr/lib/vmware/bin /vmware-vmkauthd-start

Jun 18 15:55:50 tes-esx1 vmware-authd[3772]: Redirected mks to 10.0.0.205:903

Jun 18 16:12:14 tes-esx1 xinetd[2309]: START: vmware-authd pid=4940 from=10.0.0. 7

Jun 18 16:12:14 tes-esx1 vmware-authd[4940]: login from 10.0.0.7 as 521b75d5-d25 f-0bbb-0ffe-1d6ef5911a55

Jun 18 16:12:14 tes-esx1 vmware-authd[4940]: Found vmkauthd: /usr/lib/vmware/bin /vmware-vmkauthd-start

Jun 18 16:12:14 tes-esx1 vmware-authd[4940]: Redirected mks to 10.0.0.205:903

# Jun 18 14:24:08 tes-esx1 vmware-authd[30161]: Redirected mks to 10.0.0.205:903

Jun 18 14:24:40 tes-esx1 vmware-authd[30194]: login from 10.0.0.7 as 5289ea97-dc 17-e126-f2a3-6f7454855329

Jun 18 14:24:40 tes-esx1 vmware-authd[30194]: Found vmkauthd: /usr/lib/vmware/bi n/vmware-vmkauthd-start

Jun 18 14:24:40 tes-esx1 vmware-authd[30194]: Redirected mks to 10.0.0.205:903

Jun 18 14:25:11 tes-esx1 xinetd[2309]: START: vmware-authd pid=30226 from=10.0.0 .7

Jun 18 14:25:11 tes-esx1 vmware-authd[30226]: login from 10.0.0.7 as 52c95730-67 fd-50e4-a546-32f0282c1415

Jun 18 14:25:11 tes-esx1 vmware-authd[30226]: Found vmkauthd: /usr/lib/vmware/bi n/vmware-vmkauthd-start

Jun 18 14:25:11 tes-esx1 vmware-authd[30226]: Redirected mks to 10.0.0.205:903

Jun 18 14:25:42 tes-esx1 xinetd[2309]: START: vmware-authd pid=30258 from=10.0.0 .7

Jun 18 14:25:42 tes-esx1 vmware-authd[30258]: login from 10.0.0.7 as 527775fb-8e 03-db20-bb4a-9d76e5375781

Jun 18 14:25:42 tes-esx1 vmware-authd[30258]: Found vmkauthd: /usr/lib/vmware/bi n/vmware-vmkauthd-start

Jun 18 14:25:42 tes-esx1 vmware-authd[30258]: Redirected mks to 10.0.0.205:903

Jun 18 15:37:42 tes-esx1 xinetd[2309]: START: vmware-authd pid=2278 from=10.0.0. 7

[athlon_crazy]

No error in your /var/log/secure but worth to try this :

http://www.rtfm-ed.co.uk/?p=388

add the line to your /etc/vmware/config

VMware newbie..

Zen Systems Sdn Bhd

www.no-x.org

[totalenginesupp]

Hi thanks for your help. I have found out the issue.

In a nutshell it seems that the esx server

was confused about which service console it was using. We had setup a backup service console in the event of an emergency but we could also connect to the

service console on the iSCSI interface in an emergency. Given this issue has

arisen I decided to remove the backup service console and have added the

now spare NIC on the esx servers into the “main” service console – i.e.

vswitch0. This now has 3 NICs.

This resolved the issue.

Thanks for your assistance and advice on what to look for, its appreciated.

Andy

[totalenginesupp]

Resolved myself, see last comment.

Andy