KNOWN ISSUE: Is there any way to generate an FQDN for the UNC path?
|Article:TECH24075|||||Created: 2006-10-25|||||Updated: 2006-10-25|||||Article URL http://www.symantec.com/docs/TECH24075|
|NOTE: If you are experiencing this particular known issue, we recommend that you Subscribe to receive email notification each time this article is updated. Subscribers will be the first to learn about any releases, status changes, workarounds or decisions made.|
Is there any way to generate the FQDN (Fully Qualified Domain Name) for the UNC codebases?
This incident was generated from a client that doesn't have a WINS implementation and the NetBIOS name for the computers does not work. While this is not generally the common practice we have decided that it should be addressed. See the Resolution for the bug tracking number.
The NetBIOS is all that has ever been generated for the UNC codebase.
No resolution at this time as it will require internal code changes to get an FQDN to be generated for UNC codebases. A tracking number has been raised with our Notification Server development team (SydD2 #28314).
The only way to work around this issue is to either implement WINS in the company infrastructure or disable the UNC codebase generation. See KB article #1904 for disabling UNC codebase generation.
|Description||Logged in sydd2 (Altiris - Sydney) database|
Article URL http://www.symantec.com/docs/TECH24075