Teaming and Windows 2003

[Sean Rooney]

Hi I recently upgraded my DL380 G3 to Windows 2003 SP1. As part of the process I installed Support Pack 7.1, not the latest, but consistent across the datacentre.

Have experienced problems in relation to team, such that we upgraded to latest NIC and teaming software in an attempt to solve the problems. To no avail.

NICs are working, but cpqteam utility will not run. If I do Start --> Run --> cpqteam.exe nothing happens. In task manager I can see it running as a process, but it doesn't show on screen to allow me to manipulate teaming.

Anyone got any suggestions?

Thanks, Seán

[Ruslan]

Try reinstall network teaming driver from latest PSP. Start setup.exe - check Network teaming driver only

[Sean Rooney]

Hi, as mentioned in the post I tried updating the NIC and the teaming software to the most up to date versions on the HP site. This didn't help. NICs working fine, but teaming software UI not appearing.

[Michael Maher]

Sean,

I've seen HP teaming acting like this myself but this was after an OS recovery but this info may help you troubleshoot.

The teaming software binds to a location in the registry where the IP address is stored.

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\{E7BADE65-061A-4EF7-A6F3-0C4089354543}

The long string value at the end is a GUID which is generated dynamically by Windows based on the MAC address and the system time.
http://www.webopedia.com/TERM/G/GUID.html

In my experiance, when I rebuilt a server the GUID was regenerated. Then having restored a System State backup on top of it, the original GUID was written back into the registry. The teaming software tries to bind to the old and now invalid GUID and fails.

My fix in this case was to delete the old/invalid GUID from the registry and reinstall the teaming software.

Michael

[Sean Rooney]

Michael, that's great info. Many thanks for the help. I'll try that.

[Connery · Accepted solution]

Sean,
CPQTEAM.EXE is the tray icon, not the configuration GUI, that is why it looks like it does nothing. The only thing that EXE does is put the little icon in the task bar so that you can double click on it to launch the Network Configuration Utility (NCU) GUI.

If you run CPQTEAM.EXE from a command-line, it will likely only add more "Teaming" tray icons but will never launch the Network Configuration Utility.

Three ways to run the Network Configuration Utility (NCU).

(1) Control Panel - HP Network Applet
(2) Double click on HP Teaming Tray icon
(3) Microsoft Network Local Area Connections, Properties of an adapter, under components, Double-click on HP Network Configuration Utility.

Hope this helps,
-sean

[Sean Rooney]

Ahhh, that explained it Seán. The try icon wasn't appearing. I was able to open it from the LAN adapter properties and then click the option to force the icon to open in the system tray. Since I've done this I've been able to team with no problems.

Thanks to everyone for taking the trouble to reply, it is much appreciated.