When a Task client attempts to register, it first requests from the NS for a list of Task Servers using /GetClientTaskServers.aspx. This may return either an FQDN or Netbios name, and sometimes this causes problems during the actual registration of the client.
For instance, if Netbios names don't resolve in an environment, then the registration may fail when attempting to register.
Another example would be for environments that have enabled SSL communications. In this case, the server certificate may have been registered with the FQDN, and thus the Netbios name would fail to receive approval (403 error).
It turns out that some times, the FQDN is returned, and sometimes it is not. The Task Server is designed to give the client not only a preferred task server, but also some fail-over's, such as the NS if the TS can't be reached. Sometimes these don't come back with FQDN, and so the client will try to use NETBIOS instead.
This has been resolved in SMP SP4 HF1.
Applies To NS 7.x
ID: ETK 1926396
Logged in Etrack (Symantec) database
Imported Document Id
This is machine translated content
Login to Subscribe
Please login to set up your
For security reasons, your link to this document has expired. Please click on the attachment link to access this file.
The attachment that you are looking for no longer exists.
There has been an issue retrieving your attachment. Please try again.
Didn't find the article you were looking for? Try these resources.