Symptom:
With Windows 7 or Vista client machines, a client that was checking in fine, suddenly stops checking into a K1000 appliance. The AMP-connection status is 'connected', but the client doesn't update Inventory.
Perform the following tests:
1. Turn on debugging on the client machine
Using notepad, open smmp.conf in the Program Files\KACE\KBOX directory:
add: debug=true
Open a command prompt and try the following commands from the Program Files\KACE\KBOX directory:
2. Try to force a client check-in by running kboxclient.exe from the install directory.
The result is that the client doesn't update its inventory and the KBOXCLIENT process in Task Manager hangs.
3. Try to create a machine.xml file: type KBOXCLIENT.exe -inventory
The folloiwng debug dialog window shows up and inventory.xml doesn't get generated in the Program Files\Kace\kbox directory:
4. The following error message appears in the agent.log file:
[2010-09-13T15:40:33] Network Error: System.Net.WebException: The operation has timed-out.
at System.Net.HttpWebRequest.GetRequestStream()
at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)
at SOAP_KBX_Service.KBX_Service.getClientIdentification(String[] clientIDValues)
at KAgentCommon.KUID.GetServerAssignedId(KBX_Service service)
5. Uninstalling and reinstalling the client results in bootstrap files that don't get downloaded into the kbot_cache sub-directory of Program Files\KACE\KBOX directory.
Solution:
1. Open a command prompt:
Type: ipconfig /all
Do you see any Adapters that are spawning multiple versions of themselves? For example, "Tunnel adapter Local Area Connection #1, #2, #3, etc.."
If you see 4+ generated, then there is a problem where the client is using .NET and .NET is using one of the stale connections.
2. Go to Device Manager: Start -> Control Panel -> Device Manager
After Device Manager is opened, Go to "View" -> "Show Hidden Devices" -> Expand Network Adapters
If you see an Adpater that has mutiple copies of itself, it will need to be uninstalled.
For Example:
Microsoft ISATAP Adapter
Microsoft ISATAP Adapter #2
Microsoft ISATAP Adapter #3
#2 and #3 needs to be uninstalled. Leave 1 instance active.
3. IPv6 needs to be turned off so multiple version of the Adpater will not get spawned after rebooting the client machine.
To turn off IPv6:
Go to the Registry settings referenced in the following Microsoft Knowledge Base-article:
http://support.microsoft.com/kb/929852
From the Knowledge Base:
Click Start, type regedit in the Start Search box, and then click regedit.exe in the Programs list. In the User Account Control dialog box, click Continue. In Registry Editor, locate and then click the following registry subkey:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip6\Parameters\ Double-click DisabledComponents to modify the DisabledComponents entry.
Note: If the DisabledComponents entry is unavailable, you must create it. To do this, follow these steps:
In the Edit menu, point to New, and then click DWORD (32-bit) Value.
Type DisabledComponents, and then press ENTER.
Double-click DisabledComponents.
Type any one of the following values to configure the IPv6 protocol, and then click OK:
This is the setting that is needed:
Type 0xffffffff to disable all IPv6 components, except the IPv6 loopback interface.
The option would look like this from command prompt execution of setting the registry:
reg add hklm\system\currentcontrolset\services\tcpip6\parameters /v DisabledComponents /t REG_DWORD /d 0xFFFFFFFF