Problem with CNAME in DNS and browsing fileshare
Hello,
I have following issue. I have a fileshare on a server called server1 and created a cname for server1 in DNS called fileserver. When I try to ping both names I get responses on both names, so DNS resolution works fine. But when I try to browse to the fileshare it only works with
\\server1
When I try to browse to \\fileserver I get a response that the computer cannot connect.
It has been working before but suddenly stopped working although the CNAME is still existing in DNS.
Thank you for your help.
Regards,
LikeWindows
I have following issue. I have a fileshare on a server called server1 and created a cname for server1 in DNS called fileserver. When I try to ping both names I get responses on both names, so DNS resolution works fine. But when I try to browse to the fileshare it only works with
\\server1
When I try to browse to \\fileserver I get a response that the computer cannot connect.
It has been working before but suddenly stopped working although the CNAME is still existing in DNS.
Thank you for your help.
Regards,
LikeWindows
I have to use the FQDN as in point #2 if the server is on another AD domain.
I should also add - nor can I access "\\other-server.my-ad.loca
You can get around this by having users on both domains with the same username and password. then they will automatically be able to connect to servers on either domain without being prompted. You have to synchronise the credentials through a VBScript or manually though unless you setup domain trusts.
You can get around this by having users on both domains with the same username and password. then they will automatically be able to connect to servers on either domain without being prompted. You have to synchronise the credentials through a VBScript or manually though unless you setup domain trusts.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
We have only one domain here and it is a Windows Server 2008 Domain.
oBdA, how do I disable the behaviour that a Windows Server only reacts to connections made to its original name or IP address ?
oBdA, how do I disable the behaviour that a Windows Server only reacts to connections made to its original name or IP address ?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
By setting the "DisableStrictNameChecking
ASKER
The article is for Windows 2000 or 2003 domains. Here we have a Windows 2008 Domain.
W2k8 has the exact same behavior and uses the exact same registry value.
On my LAN we use "my-ad.local", we have another domain "other-ad.local". Each domain has fileservers called "my-server.my-ad.local" and "other-server.other-ad.loca
1. I can access any share on "my-ad.local" using "\\my-server\someshare" or "\\my-server.my-ad.local\so
2. I can access any share on "other-ad.local" using the FQDN "\\other-server.other-ad.lo
3. In "my-ad.local" DNS, I *cannot* create a CNAME or A for "other-server" pointing to its IP, and access it by "\\other-server\someshare", otherwise I get the same "Cannot find server" error.