VMware Cloud Community
moonbutterfly
Contributor
Contributor
Jump to solution

vmware vsphere client is in 'loading inventory' for a long time ,then got a 'time out' message

We have two type network connection in my lab, one is internal net, all computers in this type network can not access internet themself, but they could access internet via a proxy server ; one is external net, all computers in this type network can access internet themself.

If my computer connection is in internal net,the client is loading inventory for a long time when I use VMware sphere client  to log into the VMware server, and  give a message 'Error connecting'. below two screen shots is for error description. but if my computer connection is in external net, I can log into vmware server successfully.

Capture.PNGCapture1.PNG

Below is the description for my VMware server infrastructure:

My vmware server have two NICs, vmnic1 and vmnic0. vmnic1 is used for internal net,vmnic0 is used for external net. I set up serval hosts in my vmware server,one of them is used for proxy, all computers in my lab can access internet by this proxy host via vmnic1.

In proxy host, I add two configurations for iptables like below:

     iptables --table nat --append POSTROUTING --out-interface eth0 -j MASQUERADE

     iptables --append FORWARD --in-interface eth1 -j ACCEPT

Additional, I have another vmware server, I also can log into vmware server successful if my computer connection is internal net. and network for this two server are the same.

How can I debug this issue ? Thank you very much!

Reply
0 Kudos
1 Solution

Accepted Solutions
spravtek
Expert
Expert
Jump to solution

Is management needed for both networks separately?

Because if not, you can move the management port-group to the internal network on vmnic1..

Create a vmkernel port and enable it for management, give it an IP-address and it should be possible to connect to the internal network.

View solution in original post

Reply
0 Kudos
4 Replies
spravtek
Expert
Expert
Jump to solution

Hi,

Welcome to the community ...

Are your vmnic0 and vmnic1 both configured for management?

I guess you're not using port groups and VLANs?

Are you using the same users, on these different networks, or just using root?

Perhaps some screenshots of the network setup can help...

Reply
0 Kudos
moonbutterfly
Contributor
Contributor
Jump to solution

Thanks spravtek.

Vmnic0 is configured for management.

I am not using VLANS.

I just using root user to log into these different networks.

Below screenshots is Networking and Network Adapters settings...

Capture5.PNG

Capture4.PNG

In the first picture, Redhat is my virtual host for proxy server, below is Redhat settings...

Capture6.PNG

Thanks.

Reply
0 Kudos
spravtek
Expert
Expert
Jump to solution

Is management needed for both networks separately?

Because if not, you can move the management port-group to the internal network on vmnic1..

Create a vmkernel port and enable it for management, give it an IP-address and it should be possible to connect to the internal network.

Reply
0 Kudos
moonbutterfly
Contributor
Contributor
Jump to solution

Got it.

I create a vmkernel port for management, and give it IP address, I can log into vmware server successfully. Thank you very much.

But I think that the root cause for that issue is not resolved. I doubt that it may be a bug for vmware sphere, I am not sure......

Your network cannot in a internal net to access internet via a proxy server which was setup at a vmware server, and at this time you log into this vmware server by vsphere client when your network is in a internal net. it may be a bug of route....

Anyway, I can log into vmware server successfully. Thank you very much.

Reply
0 Kudos