Hi Wasim,
Further to Mark's comments, here are a couple of troubleshooting steps you can try:
Step 1: can you ping the IP on the Stingray VA?
Access the console for the virtual appliance using whatever VMware tool you are using. Once the appliance has booted for the first time, you should see a 'Welcome' message that provides the URL (https://192.168.1.151:9090) for the admin server. Note: the IP address is obtained via DHCP. If the appliance could not get an IP, it will select 192.168.1.101.
Ensure that you can ping the IP from your client machine. If you cannot ping it, then there's a routing problem, or Stingray has raised the incorrect IP. Using the console:
- Alt+F2 to switch to tty2
- Log in as admin/admin
- Run z-set-initial-address to set the IP to something appropriate
- Logout and Alt+F1 to switch back to tty1
- Check the admin URL and verify that you can ping it
Keep working with the networking until you have raised an IP on Stingray that you can ping
Step 2: can you access the admin server?
Point a web browser at http://IP:9090. All being well, the webbrowser should be redirected to https://IP:9090 (note the switch from http to https) and then you will probably get an 'untrusted SSL certificate warning' that you should permit, then you will get the initial config wizard.
Use the developer tools or an http client (e.g curl -i) to verify that you are getting the redirect from http to https:
ogarrett-mbpro:~ ogarrett$ curl -i http://192.168.35.10:9090
HTTP/1.1 302 Moved Temporarily
Date: Thu, 07 Feb 2013 17:33:18 GMT
Content-Type: text/html
Connection: close
Location: https://192.168.35.10:9090/
<html><body>This service is encrypted</body></html>
Then try the https URL. It's normal to get a certificate error (as Stingray's admin interface uses a self-signed, automatically-generated certificate that is not trusted by default).
If you still have problems, raise a query with our support team.
Hope that this helps
Owen
