?
Solved

Server not responding vSphere Mobile Watchlist

Posted on 2014-02-27
3
Medium Priority
?
1,756 Views
Last Modified: 2014-03-05
I have three vCenter clusters setup in vSphere. The way I have configured access via web browser is to use load balancers to send client request connections from vsphere.domain.com to any of the three vcenters. There's no priority on which real server gets the client request. Source IP Persistence (stickiness) is set to 1 hour and the load balancers are configured to redirect to port 9443 from 80. This all has worked well both on our local network as well as outside our local network using a web browser. Now we're trying to use the Android vSphere Mobile Watchlist app to access and manage vSphere. On our network if I use the real server IP addresses bypassing my load balancer setup the android app works however, when using the FQDN (vsphere.domain.com) I immediately get "server not responding". What could the app be requesting or using that I need to account for? Different port or protocol? Thank you in advance for any information.
0
Comment
Question by:Jason B
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 2
3 Comments
 
LVL 13

Expert Comment

by:Abhilash
ID: 39894445
Is this FQDN publicly resolvable? May be its happening because the watchlist can talk only to VMware environment directly and cannot identify a load balancer.
0
 

Accepted Solution

by:
Jason B earned 0 total points
ID: 39895169
This was resolved after figuring out that the vSphere Mobile Watchlist app uses port 443 not 9443. A new access rule in the firewall and another port redirect on the load balancer virtual IP resolved "Server not responding".
0
 

Author Closing Comment

by:Jason B
ID: 39905917
I troubleshot and found the issue and the solution.
0

Featured Post

Threat Trends for MSPs to Watch

See the findings.
Despite its humble beginnings, phishing has come a long way since those first crudely constructed emails. Today, phishing sites can appear and disappear in the length of a coffee break, and it takes more than a little know-how to keep your clients secure.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

When rebooting a vCenters 6.0 and try to connect using vSphere Client we get this issue "Invalid URL: The hostname could not parsed." When we get this error we need to do some changes in the vCenter advanced settings to fix the issue.
This article outlines why you need to choose a backup solution that protects your entire environment – including your VMware ESXi and Microsoft Hyper-V virtualization hosts – not just your virtual machines.
Teach the user how to configure vSphere clusters to support the VMware FT feature Open vSphere Web Client: Verify vSphere HA is enabled: Verify netowrking for vMotion and FT Logging is in place or create it: Turn On FT for a virtual machine: Verify …
Teach the user how to install and configure the vCenter Orchestrator virtual appliance Open vSphere Web Client: Deploy vCenter Orchestrator virtual appliance OVA file: Verify vCenter Orchestrator virtual appliance boots successfully: Connect to the …
Suggested Courses

770 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question