"Aliases" Fail on Some Operations

We have some servers that require DNS CNAMES and a second WINS entry added
manually. For example:
HOST Record - blade1.company.com; CNAME - hrserver.company.com
WINS dynamic entry from server - BLADE1; Static entry on WINS - HRSERVER

We can ping using any of the names and we can connect to SMB shares using
any of the names. If I use nbtstat -a to either NB name, it returns the same
MAC address, but for the static (2nd) entry it shows the name table for the
dynamic entry. For example, "nbtstat -a hrserver" returns the name table for
BLADE1.

The real problem is when admins try and use the name "hrserver" (from the
above example) in an automatically run script (via Scheduled Task or GP
Startup), or for Group Policy Software Installation.

I would have expected these operations to try the DNS name first, which I
don't believe would be a problem. However, they appear to use the NB name
instead and the request fails unless we use the dynamically created (1st)
entry in WINS.

This is my theory at least. I suppose it's possible that the DNS alias is
being tried and that is failing, but that doesn't seem to be the case.

Has anyone else seen this? Creating the static WINS entry seems
straightforward, but perhaps we are not doing it correctly?

Any help would be appreciated.

Hi,

Thank you for posting.

According to your description, I understand that:

DNS Alias request for Alias failed in Logon script, Scheduled Task or Group
Policy Software Installation.

If I have misunderstood the problem, please don't hesitate to let me know.

This issue may be caused by null session access, StrictNameChecking and
other settings. Please try the steps below to change Registry settings.

1. Please try to suggestions to edit Registry in the following article.

How to enable null session shares on a Windows 2000-based computer
http://support.microsoft.com/default...b;EN-US;289655

2. If the issue persists, please create/Edit following registry keys on the
server and then reboot:

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Servic es\LanmanServer\Parameters
Value name: DisableStrictNameChecking
Data type: REG_DWORD
Value: 1

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Contro l\Lsa
Value name: DisableLoopbackCheck
Data type: REG_DWORD
Value: 1

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Contro l\Lsa\MSV1_0
Value name: BackConnectionHostNames
Data type: REG_MULTI_SZ
Value: hrserver

Could we solve the issue? If not, please let us know the detailed error
message of this issue when logon script failed for research.

Sincerely,
Mervyn Zhang
Microsoft Online Community Support

==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.