VMware Cloud Community
habibalby
Hot Shot
Hot Shot
Jump to solution

Unable to access the specified host, it either does not exist, the server is not responding or there is a network problem

Hi,

I'm using ESX 3.0 EVAL with VC and VIC installed on the same Client XP2 Machine. When I login to the VIC by using the LOCAL Adminstrator Username of the VC and it's password and try to add the ESX Host to the Datacenter, I got the "Unable to access the specified host, it either does not exist, the server is not responding or there is a network problem".

But, when i Login to the VIC by using the ESX root and it's password, it directly access the VIC.

Currently, I have no DNS Server installed.

Any Idea?

BR,

Habibalby

Best Regards, Hussain Al Sayed Consider awarding points for "correct" or "helpful".
Reply
0 Kudos
1 Solution

Accepted Solutions
Santhosh_vmware
Jump to solution

Second option will work for you.To add dns in esx -> connect to esx using vi client configuration->DNS and routing add the entry.

View solution in original post

Reply
0 Kudos
35 Replies
ExCon
Enthusiast
Enthusiast
Jump to solution

Have you tried putting in hosts entries on both boxes?

Santhosh_vmware
Jump to solution

Hi,

Make sure you resolve hostnames to ip's (for windows add entries in c:\windows\system32\etc\drivers\hosts file )and Please try restarting vmware-vpxa and mgmt-vmware services.

regards

santhosh

habibalby
Hot Shot
Hot Shot
Jump to solution

Alright, will do that, but how can i add the DNS in the ESX Host? also, which DNS Server i should use to add it? Or just adding the Hostnames of both the ESX Server and VC Client to be resolved the Names to an IP and vice versa?

Best Regards, Hussain Al Sayed Consider awarding points for "correct" or "helpful".
Reply
0 Kudos
Santhosh_vmware
Jump to solution

Second option will work for you.To add dns in esx -> connect to esx using vi client configuration->DNS and routing add the entry.

Reply
0 Kudos
habibalby
Hot Shot
Hot Shot
Jump to solution

Accessing the VIC to the ESX Server by the Root and it's password?

BR,

Habibalby

Best Regards, Hussain Al Sayed Consider awarding points for "correct" or "helpful".
Reply
0 Kudos
Santhosh_vmware
Jump to solution

yes

regards

santhosh

Reply
0 Kudos
habibalby
Hot Shot
Hot Shot
Jump to solution

HI,

I have added the entries into the Client for the ESX Host and corrented the ESX DNS Entries in the VIC, restarted both the machiens "With no Luck".

Any further help?

Thanks,

Habibalby

Best Regards, Hussain Al Sayed Consider awarding points for "correct" or "helpful".
Reply
0 Kudos
ExCon
Enthusiast
Enthusiast
Jump to solution

From the VirtualCenter server, can you ping the ESX host by name and IP address? How about from the ESX host to the VirtualCenter machine?

Reply
0 Kudos
habibalby
Hot Shot
Hot Shot
Jump to solution

HI,

From the VC Client, i can ping the ESX host becuase i have added the name entry into the Host file. but from the ESX host, i'm unable to do so. In addition, i have added the DNS Name into the DNS Tab from the VIC.

I have ran the netstat -a to see the Active ports "Connection" while the VC tries to access the ESX Host, and here's the result.

Active Connections

Proto Local Address Foreign Address State

TCP Client01:ftp Client01:0 LISTENING

TCP Client01:http Client01:0 LISTENING

TCP Client01:epmap Client01:0 LISTENING

TCP Client01:https Client01:0 LISTENING

TCP Client01:microsoft-ds Client01:0 LISTENING

TCP Client01:902 Client01:0 LISTENING

TCP Client01:3389 Client01:0 LISTENING

TCP Client01:27000 Client01:0 LISTENING

TCP Client01:1921 localhost:8083 ESTABLISHED

TCP Client01:8083 Client01:0 LISTENING

TCP Client01:8083 localhost:1921 ESTABLISHED

TCP Client01:8085 Client01:0 LISTENING

TCP Client01:8087 Client01:0 LISTENING

TCP Client01:14147 Client01:0 LISTENING

TCP Client01:http Client01.habibalby.local:1920 ESTABLISHED

TCP Client01:netbios-ssn Client01:0 LISTENING

TCP Client01:902 Client01.habibalby.local:1922 ESTABLISHED

TCP Client01:1270 esx.habibalby.local:902 CLOSE_WAIT

TCP Client01:1920 Client01.habibalby.local:http ESTABLISHED

TCP Client01:1922 Client01.habibalby.local:902 ESTABLISHED

TCP Client01:1924 esx.habibalby.local:902 CLOSE_WAIT

TCP Client01:1926 esx.habibalby.local:902 TIME_WAIT

TCP Client01:1927 Client01.habibalby.local:27000 TIME_WAIT

TCP Client01:1928 esx.habibalby.local:902 ESTABLISHED

TCP Client01:1930 esx.habibalby.local:902 TIME_WAIT

TCP Client01:1933 89.202.157.136:http SYN_SENT

TCP Client01:27000 Client01.habibalby.local:1076 CLOSE_WAIT

TCP Client01:27000 Client01.habibalby.local:1083 CLOSE_WAIT

TCP Client01:27000 Client01.habibalby.local:1139 CLOSE_WAIT

TCP Client01:27000 Client01.habibalby.local:1148 CLOSE_WAIT

TCP Client01:27000 Client01.habibalby.local:1155 CLOSE_WAIT

TCP Client01:27000 Client01.habibalby.local:1222 CLOSE_WAIT

TCP Client01:27000 Client01.habibalby.local:1229 CLOSE_WAIT

TCP Client01:27000 Client01.habibalby.local:1232 CLOSE_WAIT

TCP Client01:27000 Client01.habibalby.local:1239 CLOSE_WAIT

TCP Client01:27000 Client01.habibalby.local:1299 CLOSE_WAIT

TCP Client01:27000 Client01.habibalby.local:1308 CLOSE_WAIT

TCP Client01:27000 Client01.habibalby.local:1329 CLOSE_WAIT

TCP Client01:27000 Client01.habibalby.local:1384 CLOSE_WAIT

TCP Client01:27000 Client01.habibalby.local:1391 CLOSE_WAIT

TCP Client01:27000 Client01.habibalby.local:1396 CLOSE_WAIT

TCP Client01:27000 Client01.habibalby.local:1452 CLOSE_WAIT

TCP Client01:27000 Client01.habibalby.local:1459 CLOSE_WAIT

TCP Client01:27000 Client01.habibalby.local:1470 CLOSE_WAIT

TCP Client01:27000 Client01.habibalby.local:1521 CLOSE_WAIT

TCP Client01:27000 Client01.habibalby.local:1544 CLOSE_WAIT

TCP Client01:27000 Client01.habibalby.local:1582 CLOSE_WAIT

TCP Client01:27000 Client01.habibalby.local:1589 CLOSE_WAIT

TCP Client01:27000 Client01.habibalby.local:1618 CLOSE_WAIT

TCP Client01:27000 Client01.habibalby.local:1776 CLOSE_WAIT

TCP Client01:27000 Client01.habibalby.local:1924 CLOSE_WAIT

TCP Client01:27000 Client01.habibalby.local:1931 CLOSE_WAIT

TCP Client01:27000 Client01.habibalby.local:1998 CLOSE_WAIT

TCP Client01:27000 Client01.habibalby.local:2005 CLOSE_WAIT

TCP Client01:27000 Client01.habibalby.local:2072 CLOSE_WAIT

TCP Client01:27000 Client01.habibalby.local:2079 CLOSE_WAIT

TCP Client01:27000 Client01.habibalby.local:2146 CLOSE_WAIT

TCP Client01:27000 Client01.habibalby.local:2153 CLOSE_WAIT

TCP Client01:27000 Client01.habibalby.local:2220 CLOSE_WAIT

TCP Client01:27000 Client01.habibalby.local:2227 CLOSE_WAIT

TCP Client01:27000 Client01.habibalby.local:2294 CLOSE_WAIT

TCP Client01:27000 Client01.habibalby.local:2301 CLOSE_WAIT

TCP Client01:27000 Client01.habibalby.local:2368 CLOSE_WAIT

TCP Client01:27000 Client01.habibalby.local:2375 CLOSE_WAIT

TCP Client01:27000 Client01.habibalby.local:2442 CLOSE_WAIT

TCP Client01:27000 Client01.habibalby.local:2449 CLOSE_WAIT

TCP Client01:27000 Client01.habibalby.local:2516 CLOSE_WAIT

TCP Client01:27000 Client01.habibalby.local:2523 CLOSE_WAIT

TCP Client01:27000 Client01.habibalby.local:2590 CLOSE_WAIT

TCP Client01:27000 Client01.habibalby.local:2597 CLOSE_WAIT

TCP Client01:27000 Client01.habibalby.local:2666 CLOSE_WAIT

TCP Client01:27000 Client01.habibalby.local:2673 CLOSE_WAIT

TCP Client01:27000 Client01.habibalby.local:2743 CLOSE_WAIT

TCP Client01:27000 Client01.habibalby.local:2750 CLOSE_WAIT

TCP Client01:27000 Client01.habibalby.local:2817 CLOSE_WAIT

TCP Client01:27000 Client01.habibalby.local:2824 CLOSE_WAIT

TCP Client01:27000 Client01.habibalby.local:2891 CLOSE_WAIT

TCP Client01:27000 Client01.habibalby.local:2898 CLOSE_WAIT

TCP Client01:27000 Client01.habibalby.local:2965 CLOSE_WAIT

TCP Client01:27000 Client01.habibalby.local:2972 CLOSE_WAIT

TCP Client01:27000 Client01.habibalby.local:3039 CLOSE_WAIT

TCP Client01:27000 Client01.habibalby.local:3046 CLOSE_WAIT

TCP Client01:27000 Client01.habibalby.local:3113 CLOSE_WAIT

TCP Client01:27000 Client01.habibalby.local:3120 CLOSE_WAIT

TCP Client01:27000 Client01.habibalby.local:3187 CLOSE_WAIT

TCP Client01:27000 Client01.habibalby.local:3194 CLOSE_WAIT

TCP Client01:27000 Client01.habibalby.local:3261 CLOSE_WAIT

TCP Client01:27000 Client01.habibalby.local:3268 CLOSE_WAIT

TCP Client01:27000 Client01.habibalby.local:3335 CLOSE_WAIT

TCP Client01:27000 Client01.habibalby.local:3342 CLOSE_WAIT

TCP Client01:27000 Client01.habibalby.local:3409 CLOSE_WAIT

TCP Client01:27000 Client01.habibalby.local:3416 CLOSE_WAIT

TCP Client01:27000 Client01.habibalby.local:3485 CLOSE_WAIT

TCP Client01:27000 Client01.habibalby.local:3492 CLOSE_WAIT

TCP Client01:27000 Client01.habibalby.local:3561 CLOSE_WAIT

TCP Client01:27000 Client01.habibalby.local:3568 CLOSE_WAIT

TCP Client01:27000 Client01.habibalby.local:3636 CLOSE_WAIT

TCP Client01:27000 Client01.habibalby.local:3643 CLOSE_WAIT

TCP Client01:27000 Client01.habibalby.local:3710 CLOSE_WAIT

TCP Client01:27000 Client01.habibalby.local:3717 CLOSE_WAIT

TCP Client01:27000 Client01.habibalby.local:3784 CLOSE_WAIT

TCP Client01:27000 Client01.habibalby.local:3791 CLOSE_WAIT

TCP Client01:27000 Client01.habibalby.local:3858 CLOSE_WAIT

TCP Client01:27000 Client01.habibalby.local:3865 CLOSE_WAIT

TCP Client01:27000 Client01.habibalby.local:3932 CLOSE_WAIT

TCP Client01:27000 Client01.habibalby.local:3939 CLOSE_WAIT

TCP Client01:27000 Client01.habibalby.local:4006 CLOSE_WAIT

TCP Client01:27000 Client01.habibalby.local:4013 CLOSE_WAIT

TCP Client01:27000 Client01.habibalby.local:4080 CLOSE_WAIT

TCP Client01:27000 Client01.habibalby.local:4087 CLOSE_WAIT

TCP Client01:27000 Client01.habibalby.local:4154 CLOSE_WAIT

TCP Client01:27000 Client01.habibalby.local:4161 CLOSE_WAIT

TCP Client01:27000 Client01.habibalby.local:4228 CLOSE_WAIT

TCP Client01:27000 Client01.habibalby.local:4235 CLOSE_WAIT

TCP Client01:27000 Client01.habibalby.local:4302 CLOSE_WAIT

TCP Client01:27000 Client01.habibalby.local:4309 CLOSE_WAIT

TCP Client01:27000 Client01.habibalby.local:4377 CLOSE_WAIT

TCP Client01:27000 Client01.habibalby.local:4384 CLOSE_WAIT

TCP Client01:27000 Client01.habibalby.local:4453 CLOSE_WAIT

TCP Client01:27000 Client01.habibalby.local:4460 CLOSE_WAIT

TCP Client01:27000 Client01.habibalby.local:4530 CLOSE_WAIT

TCP Client01:27000 Client01.habibalby.local:4537 CLOSE_WAIT

TCP Client01:27000 Client01.habibalby.local:4604 CLOSE_WAIT

TCP Client01:27000 Client01.habibalby.local:4611 CLOSE_WAIT

TCP Client01:27000 Client01.habibalby.local:4678 CLOSE_WAIT

TCP Client01:27000 Client01.habibalby.local:4685 CLOSE_WAIT

TCP Client01:27000 Client01.habibalby.local:4752 CLOSE_WAIT

TCP Client01:27000 Client01.habibalby.local:4759 CLOSE_WAIT

TCP Client01:27000 Client01.habibalby.local:4826 CLOSE_WAIT

TCP Client01:27000 Client01.habibalby.local:4833 CLOSE_WAIT

TCP Client01:27000 Client01.habibalby.local:4900 CLOSE_WAIT

TCP Client01:27000 Client01.habibalby.local:4907 CLOSE_WAIT

TCP Client01:27000 Client01.habibalby.local:4974 CLOSE_WAIT

TCP Client01:27000 Client01.habibalby.local:4981 CLOSE_WAIT

UDP Client01:microsoft-ds :

UDP Client01:isakmp :

UDP Client01:902 :

UDP Client01:1722 :

UDP Client01:1789 :

UDP Client01:4500 :

UDP Client01:ntp :

UDP Client01:1026 :

UDP Client01:1028 :

UDP Client01:1030 :

UDP Client01:1032 :

UDP Client01:1039 :

UDP Client01:1041 :

UDP Client01:1057 :

UDP Client01:1116 :

UDP Client01:1121 :

UDP Client01:1719 :

UDP Client01:1721 :

UDP Client01:1900 :

UDP Client01:1919 :

UDP Client01:1935 :

UDP Client01:ntp :

UDP Client01:netbios-ns :

UDP Client01:netbios-dgm :

UDP Client01:1900 :

Any help?

Message was edited by: habibalby

Best Regards, Hussain Al Sayed Consider awarding points for "correct" or "helpful".
Reply
0 Kudos
Santhosh_vmware
Jump to solution

Hi,

its looks like license server problem,can you check if licenses are available in vc->admin-> licenses

regards

santhosh

Reply
0 Kudos
habibalby
Hot Shot
Hot Shot
Jump to solution

HI, Yes the license is available there. Have alook at the attached screen shot.

Best Regards, Hussain Al Sayed Consider awarding points for "correct" or "helpful".
Reply
0 Kudos
Santhosh_vmware
Jump to solution

Hi,

Make sure time is same on vc and esx host,

remove vc agent on server

rpm -e VMware-vpxa-2.0.x.xxxxx(get the full packaged name by typing command "rpm -qa | grep -i vmware-vpxa)

then readd from vc.

regards

santhosh

Reply
0 Kudos
habibalby
Hot Shot
Hot Shot
Jump to solution

Hi, i got an error when i try to find the package. I have tried to see the time, the time is shows is Asia/Bahrain but my VC the time is Kuwait/Ryadh. Does that make sense? Also, the tim ein the ESX is 3 hurs different that the VC.

Any help?

Best Regards, Hussain Al Sayed Consider awarding points for "correct" or "helpful".
Reply
0 Kudos
Santhosh_vmware
Jump to solution

what is the error you are getting while finding the package.

Reply
0 Kudos
ExCon
Enthusiast
Enthusiast
Jump to solution

I would start with the simple stuff... Log into your ESX console and do the following:

1. nano /etc/hosts

2. Add in the IP and FQDN of the VC server

3. -Ctrl- X, y, -Enter-

4. ping VCServer_IP_Address

5. ping VCServer.domain.xxx

Reply
0 Kudos
Santhosh_vmware
Jump to solution

Hi ,

check the contents of license file on the host

cat /etc/vmware/vmware.lic

once there has been issue with the eval license see the following thread

http://communities.vmware.com/message/805449

regards

santhosh

Reply
0 Kudos
habibalby
Hot Shot
Hot Shot
Jump to solution

HI, I have added the VC entry into the host file, plus i have setup a DNS Server on WIN2K3. ESX and VC can be pingable by Name and IP.

After setup the DNS host entryies i have restarted the service mgmt-vmware restart. the Service vmware-vpxa i cannot find it.

Santosh,

The error is syntax error.

I'm gonna restart both the VC and ESX and try again.

Best Regards, Hussain Al Sayed Consider awarding points for "correct" or "helpful".
Reply
0 Kudos
habibalby
Hot Shot
Hot Shot
Jump to solution

I dont think as I have issued the License Yesterday!

HOSTID=ANY ISSUED=09-Dec-2007 \

NOTICE="FulfillmentId=861705;name=Name of the Company"

Next Troubleshooting is to connect the ESX and VC via a cross cable "If possible" and try. If not, then I'm suspecting the ESX Version and it;s compatibility with the Licnese which they have sent. If this is the case, i wll install the version of 3.0.1-32039 and i will see.

Any suggetion?

Best Regards, Hussain Al Sayed Consider awarding points for "correct" or "helpful".
Reply
0 Kudos
admin
Immortal
Immortal
Jump to solution

What errors do you see in the VC server (vpxd-*.log) files?

Reply
0 Kudos