VM Pro Client Login issue - UC Module, 9.1.1.

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts
  • sconnell72376
    Member
    • Nov 2013
    • 7

    VM Pro Client Login issue - UC Module, 9.1.1.

    I have a customer who is not able to login to their sites, all stand-alone, with the VM Pro client using the creds I provided them from when the systems were prepped and programmed. They get invalid user and password. These systems are running at 9.1.1. with the UC module. I had no problems logging in locally to these, patching into the LAN port, include a final check before I boxed everything up (and yes I did a proper shut down of the UC module). Now installed on site, customer has not been able to log into all 9.1.1. sites remotely from their corporate office via their WAN with connections being of varying degree, and yesterday while patched in to locally on site to the LAN port of one system. As a side note, 9.0 and 8.1 systems -- no problem loggin into VM Pro remotely, so this is clearly exclusive to 9.1 sites.

    I learned my contacts do not have Administrator privelages on their computers, and they need their IT people to install the Admin Lite package and the VM Pro client on their computers. I also found they have the 9.1.0 VM Pro client running, so the 9.1.1 version will be installed by their IT very soon. I told them they need to install and run both as an Administrator, though they had no problems with Manager at all so far, nor using the web manager with same creds i gave them. Beyond these possibilties, anything else that could be causing this issue? I know for a fact no creds on the system were changed, they are as they were when they left my desk.
  • zakabog
    Genius
    • Aug 2014
    • 300

    #2
    If they have version 9.1.0 and they're failing to connect to a 9.1.1 system, the client version would be the first thing I'd fix.

    Comment

    • sconnell72376
      Member
      • Nov 2013
      • 7

      #3
      Waiting on that to get done by their IT group, but wouldn't the error be something different, if it was too early a version? I know it's only one maintenance release back that they are using. I guess we'll see.

      Comment

      Loading