accessing a share by its dns-alias name

  • Thread starter Thread starter sundar23
  • Start date Start date
S

sundar23

I am having problems accessing a windows share by its dns alias name (
instead of the host name) when I logon to the host.

ie: 1. "box1" is the hostname of the machine
2. "redhot" is its dns alias name.
3. "cold" is a share I defined in

when I access it as \\box1\cold , it works
when I access it as \\redhot\cold, it does not work.

please help

P.S:

Even, \\redhot\cold, did not work to start with. But I made some
modifications as per the Microsoft article,
http://support.microsoft.com/?id=281308 , then It worked.
 
using \\ (aka UNC path) is a NetBIOS feature and is resolving the netBIOS
name of th computer. If you don't have a WINS server, then it is resolved by
broadcast. If you do have a WINS server, you could make a static entry for
the alias.
 
Kurt said:
using \\ (aka UNC path) is a NetBIOS feature and is resolving the netBIOS
name of th computer. If you don't have a WINS server, then it is resolved by
broadcast. If you do have a WINS server, you could make a static entry for
the alias.

since w2k windows tries to resolve the name through dns at first. When
dns resolution fails it uses NetBIOS.
 
I am having problems accessing a windows share by its dns alias name (
instead of the host name) when I logon to the host.

ie: 1. "box1" is the hostname of the machine
2. "redhot" is its dns alias name.
3. "cold" is a share I defined in

when I access it as \\box1\cold , it works
when I access it as \\redhot\cold, it does not work.

The error is caused by the strict name checking. Set the follwing
registry key on the file server:

Key:
HKEY_Local_MachineSystemCurrentControlSetServicesLanmanServerParameters
Name: "DisableStrictNameChecking"
Type: REG_DWORD
Value: 1
 
Hi Frank,

Thanks for the reponse. This registry change was already done as per
the article,

http://support.microsoft.com/?id=281308

Only after this change, accessing the share by its dns-alias name
started working from OTHER machines in the Network.

But, still it is not working from the LOCAL machine. This is my
problem.

Thanks again for the response.

regards
sundar
 
Back
Top