Support

Search

Close

My Support

Close

  • Guest Welcome
  • Login
  • Register
  • Help
  • 「Arcstar Universal One Virtual」, Are you sure you want to register this support information to My Support?

    • Register
    • Cancel

Frequently Asked Questions

Information for frequently asked questions on Arcstar Universal One Virtual

Return to Previous Page

Registration Date: June 08,2015 / Update Date: June 08,2015

When using vApp to connect to the virtual network, the IP address 169.254.xxx.xxx is assigned, and cannot use the sevice.

When the virtual NIC operating on Windows is not able to get the IP address normally, 169.254.xxx.xxx will be assigned and customers cannot communicate normally.
The possible reasons would be these two below.

{1}Lack of authority of Windows account operating vApp
{2}The conflict with the other application drivers on Window.

Please kindly be requested to confirm the following.
(The following is the explanation for Windows7. The operation can vary partly depending on OS )

(1)Confirm the authority of a user account
1. Open [Control Panel]
2. Open [User Accounts]
3. Open [Manage User Accounts]
4. Select the User who runs vApp in [Users] tab. Then, click [Properties]
5. Please confirm if the [group membership] would be [Standard user] or [Administrator]

(2)Confirm the condition of Windows service
1. Open "Control Panel".
2. Click [Administrative Tools]
3. Press the [Services] button
4. Look for [vnc_service] out of the list, and confirm that "Status" is "Started", "Startup Type" is "Manual", and "Log On As" is "Local System".
(When vApp is not in use or when vApp is not trying to connect to UNO Virtual, it is blank.)
5. Right-click on [vnc_service], then click on [Properties].
6. Please confirm that [Local System account(L)] is selected in [Log On] tab.

If you confirm (1)(2) and find no problem, possible reason {1} has nothing to do with this issue.

In that case, we assume vApp does not work normally due to a conflict with the other applications installed in your device.
Your cooperation would be greatly appreciated to check if there is a common application driver which is installed in the devices having this issue. Please try again after deleting such application driver.

Return to Previous Page


To the top of this page