Troubleshooting HP Smart Update Manager in
IPv6 Windows Server 2003 environment
To validate that the IPv6 network is configured
correctly for HP Smart Update Manager support, you must verify the
following based on your operating system version.
Validate that the addresses are site-local.
Site-local addresses normally start with "FEC0:". Global and
link-local IPv6 addresses are not supported when the remote target
is Windows Server┬« 2003.
Validate that you can ping the remote target
server. With Windows┬« operating systems, you can still use the ping
command to ping IPv6 addresses: ping <ipv6 address>.
Ensure you can ping the IPv6 loopback
address: ping ::1.
Use the DNS hostname instead of IPv6 address
to ensure the address is correct.
Ensure you have installed the IPv6 protocol.
It is not installed by default in Windows Server┬« 2003. Be sure to
reboot the server after installing the protocol to ensure addresses
are properly obtained.
Verify that you can connect to the admin$
share using the credentials within HP Smart Update Manager by
issuing the following command at a console prompt:
net use *
net use *
You might need to provide the password if
you are using a user name that is not the same as you used to log
in to the local system. All network shares require the use of the
.ipv6-literal.net name string to be properly configured by
Windows┬«. For more information about accessing IPv6, see the
Knowledge Base article.
NOTE: You do
not need to use the .ipv6-literal.net suffix when entering IPv6
address into the HP Smart Update Manager user interface or when
passing IPv6 address using command line parameters to HP Smart
After you validate that you can access the
admin$ share on the remote target server, HP Smart Update Manager
works unless other network or hardware issues exist.