PatchQuest

Installation and Start up

1. Successfully installed PatchQuest Server as a Windows service, but service does not start-up (older than build 4201).
2. Successfully installed and started PatchQuest Server as a Windows service, but system addition from the UI fails (older than build 4201).
3. Installed the PatchQuest Server in a Windows machine. Logged in to the web UI and tried to add a Windows system in the domain. Addition of this system failed.
4. Started the PatchQuest Server using the 'Start Server, option from Start Menu --> Programs. It throws an error message : 'Resource check failed for service jboss:service=Naming. Port already in use:2099'

System Discovery

1. Adding a Windows system fails with error message "Unable to establish connection"
2. Adding a Windows system fails with error message "Discovering system [hostname] failed. Remarks : Access is denied."
3. Addition of a Windows systems fails, with error message "Unable to locate SAMBA service". PatchQuest server is installed in a Linux machine.
4. Addition of a Windows systems fails, with error message : "The system language is identified to be ..... Currently only English language is supported... Check Regional & Language options of this system."
5. PatchQuest agent is running on a Windows XP SP2 machine but scan of this machine fails with 'Connection timed out' error. Why ?

Patch Deployment

1. When deploying patches, patch deployment fails with the error : "Failed to execute the patch. The file may either be corrupted or may not be an exe file." or "Failed to push the patch to the remote m/c. Check if the file really exists in the server store."

General

1. Chose the SSH protocol while adding a Linux system. The system did not get added even though SSH is available in the target machine
2. While testing the proxy server configuration, the test is successful even if a wrong user name is given
3. Download of some Debian patches fails

Installation

1. Successfully installed PatchQuest Server as a Windows service, but service does not start-up (older than build 4201)

Reason : Wrong system password given in the "Login Account Information" screen in the wizard, during PatchQuest installation

Solution : Go to the 'LogOn' Properties of the 'PatchQuest' server service, from the Services Applet window and correct the password for 'This account' option. Then, restart the PatchQuest server service.

2. Successfully installed and started PatchQuest Server as a Windows service, but system addition from the UI fails (older than build 4201)

Reason : The "Login Account Information" screen was skipped in the wizard, during PatchQuest installation. Service has started in Local System Account.

Solution : Go to the 'LogOn' Properties of the 'PatchQuest' server service, from the Services Applet window and select 'Log on as: This account'. Enter the system user name (with administrator rights) in the format : <domain name\username> and password. Click 'OK'. Restart the PatchQuest service and retry system addition.

3. Installed the PatchQuest Server in a Windows machine. Logged in to the web UI and tried to add a Windows system in the domain. Addition of this system failed.

Reason : The PatchQuest server machine is not in the domain

Solution : For Windows installation, ensure that the PatchQuest Server is installed in a machine which is in the Windows domain of your enterprise. Addition of Windows systems that are in the domain will not function if PatchQuest is installed in a machine that is not in the domain.

4. Started the PatchQuest Server using the 'Start Server, option from Start Menu --> Programs. It throws an error message : 'Resource check failed for service jboss:service=Naming. Port already in use:2099'

Reason : Another instance of PatchQuest Server is already running (maybe as a service)

Solution : Two instances of the PatchQuest Server cannot be started in the same machine. PatchQuest might be already running as a service. Ensure that the previously running instance is stopped before starting the new one.

System Discovery

1. Adding a Windows system fails with error message "Unable to establish connection"

Reason 1 : The target system is a Windows XP SP2 machine with 'File and Printer Sharing' disabled in the firewall and/or 'simple file sharing' enabled

Solution : 1. Enable or turn-on the "File and Printer Sharing" option in your Windows Firewall (of the target system). This can be done from Control Panel --> Windows Firewall --> Exceptions tab --> Programs and Services --> Check "File and Printer Sharing"

2. Disable simple file sharing (Uncheck the option from Windows Explorer --> Tools --> Folder Options --> View tab --> Use simple file sharing)

Reason 2 : The system is not reachable from the PatchQuest server machine

Solution : Make sure that the system is alive and you are able to access it from the PatchQuest server machine by using : 

(1) PatchQuest Server in Windows - the 'net use' command or UNC location (\\machine-name\ADMIN$). Example : net use \\<machine-name>\ADMIN$ /USER:<administrator username>

If you are unable to reach the system in these ways, contact your system administrator

(2) PatchQuest Server in Linux - <SAMBA_HOME>/bin/net -S <target machine name> [-W <domain>] -U <username>%<password> and see if the command succeeds.

Reason 3 : The 'NetBIOS over TCP/IP' options are not configured in the system you are trying to add.

Solution : To verify and confirm, go to Control Panel --> Network and Dial-up Connections --> Right-click on Local Area Connection --> Select Properties --> Internet Protocol (TCP/IP) --> Properties button --> Advanced button --> WINS tab.

From here, see if the radio-button is selected for the 'Disable NetBIOS over TCP/IP' option. If yes, please deselect this option and select the 'Enable NetBIOS over TCP/IP' option. Once this is done and the configuration is saved, retry the system addition from the 'Add System' screen of PatchQuest's web interface.

2. Adding a Windows system fails with error message "Discovering system [hostname] failed. Remarks : Access is denied."

Reason : The credential provided (username/password) while adding the system, does not have administrator privileges.

Solution : Enter the username with administrator privileges or create a new user account with administrator privileges and use the same.

3. Addition of a Windows systems fails, with error message "Unable to locate SAMBA service". PatchQuest server is installed in a Linux machine.

Reason : Samba package is not installed in the PatchQuest server machine.

Solution : Download Samba package (samba-tng) from http://download.samba-tng.org/tng/ and install it. Point SAMBA_HOME to the Samba installation directory.

4. Addition of a Windows systems fails, with error message : "The system language is identified to be ..... Currently only English language is supported... Check Regional & Language options of this system."

Reason : The system locale of the system you are trying to add, could be set to something other than English (though your OS could be English)

Solution : In Win XP, go to Control Panel --> Regional and Language Options --> Advanced tab. From the 'Language for non-Unicode programs' drop-down menu select English (United States) and click Apply. In the pop-up dialog, click Yes and then restart the computer when prompted. After restart, try to add this system from PatchQuest.

5. PatchQuest agent is running on a Windows XP SP2 machine but scan of this machine fails with 'Connection timed out' error. Why ?

Reason : The Windows firewall is turned on is this machine and it blocks the agent port (default 9001) to be accessed by the server

Solution : Go to Control Panel --> Windows Firewall --> Exceptions tab and add a TCP port exception (Add Port) for the agent's default port 9001. Retry scanning.

Patch Deployment

1. When deploying patches, patch deployment fails with the error : "Failed to execute the patch. The file may either be corrupted or may not be an exe file." or "Failed to push the patch to the remote m/c. Check if the file really exists in the server store."

Reason 1 : You are using a NAT router/firewall and the external IP address of this device is being set as IP address of the PatchQuest Server machine and sent to the target machine. Because of this, the patch is unable to be downloaded into the target system for installation. Ideally, the internal IP address of the server should be received by the target machine.

Solution : Check if you are able to reach the PatchQuest Server machine using the same external IP address from the URL : http://<IP Address:port number>/store/patchname (URL will be present in the error message), from the target machine. If this fails (as the external IP address will not be accessible from the target machine), do appropriate network configurations for the internal IP address (of the server machine) to be returned, and retry the deployment.

Reason 2 : The system on which the PatchQuest Server is installed has more than one NIC (Network Interface Card), each with a different IP Address - one for special use and the other for the local LAN. The PatchQuest Server has picked up the IP address other than the one that is used in the local LAN.

Solution : Ensure that the target system (Agent/Agentless) can connect to the PatchQuest Server using the local LAN IP of Server, after disabling the NIC used for special purpose. Also, check the size of the particular patch file in the <PatchQuest_Install_Dir>/store directory.

General

1. Chose the SSH protocol while adding a Linux system. The system did not get added even though SSH is available in the target machine.

Reason : The Linux system you are trying to add supports only sshv2 protocol

Solution : To manage Linux systems that support sshv2 protocol, carry out the following steps and then add the system from the UI :

• Download sshtools-j2ssh-0.0.4-alpha-bin.tar file from the URL : http://prdownloads.sourceforge.net/sshtools and extract
• Place the jar files present in the 'lib' directory obtained in the extraction, in <PatchQuest_Server_Install_Dir>/AdventNet/SecureCentral/PatchQuest/lib directory
• Restart the PatchQuest server

2. While testing the proxy server configuration, the test is successful even if a wrong user name is given

Reason : Proxy server caching previous successful authentication

Solution : Your proxy server could be caching a previous authentication for a pre-configured period of time. Till such time, tests with new credentials will also pass. Reduce your proxy server authentication cache timing and try again.

3. Download of some Debian patches fails

Reason 1 : Internet access failed

Solution : Make sure that the Proxy Settings are configured and you are able to access the internet from the PatchQuest server machine

Reason 2 : Vulnerability Database in the PatchQuest server is not in sync with the latest patch information

Solution : As a result of the vulnerability database not being in sync, there could be a date mismatch resulting in download failure due to an improper download URL. Update the vulnerability database information and retry the download.