If the peer is NBA enabled, obtain the following information to help Customer Support diagnose the problem:
Verify that the peer meets the minimum system requirements.
For more information, see Private Last Mile system requirements.
If you installed the private peer that includes a built-in virtual machine:
Check whether the private peer is installed on a virtual machine.
Check whether there is an existing VMware installation. If there is, remove the VMware and reinstall Private Last Mile. If you cannot remove the VMware, install the No-VM version of the private peer.
Determine whether the peer has a firewall turned on.
Check whether the Windows Task Manager shows that
Provide screen shots that show the running applications and the running processes.
Check the status of the
GomezNBAservices on the service manager.
Verify that the
GomezNBAservice is set to log on as Local System Account.
Review the peer's Preferences dialog box to see whether the option Enable IE Native Browser Agent selected.
Check whether the command
ping gmz-lmreplies with the IP address, and make a note of the reply content.
If the IP address ends in
.1, you may be able to work around the issue by entering the IP address manually, replacing
.128, and setting the IP address to
gmz-lmin the host file. For example, if the IP address is 192.168.172.1:
- Open the file
C:\Windows\system32\drivers\etc\hostsinto a text editor (such as Windows Notepad).
- Add the following line:
- Save and close the file.
- Restart the
- Open the file
vmware*.logfile from the NBA file directory, in addition to the peer's logs.
From a command shell, execute the following:
cd C:\Program Files\VMWare\VMWare Player\
-vnetsniffer VMnet 8
[Ctrl-c]after a few pages of output.
To confirm that one of the listed IP addresses is the right address to use, execute the following in a command shell:
telnet ip_address 7878
*ip_address*is the selected IP address.
Provide a screen shot of the NBA directory if possible.