Why Experts Exchange?

Experts Exchange always has the answer, or at the least points me in the correct direction! It is like having another employee that is extremely experienced.

Jim Murphy
Programmer at Smart IT Solutions

When asked, what has been your best career decision?

Deciding to stick with EE.

Mohamed Asif
Technical Department Head

Being involved with EE helped me to grow personally and professionally.

Carl Webster
CTP, Sr Infrastructure Consultant
Ask ANY Question

Connect with Certified Experts to gain insight and support on specific technology challenges including:

Professional Opinions
Ask a Question
Did You Know?

We've partnered with two important charities to provide clean water and computer science education to those who need it most. READ MORE

troubleshooting Question

DNS Host A record manually created, UNC Path is read only

Avatar of AMTubular
AMTubularFlag for United States of America asked on
Windows Server 2003Active DirectoryDNS
1 Comment1 Solution586 ViewsLast Modified:
So I work at a large organization and one of our smaller sites just recently moved its file and print server from an aging 2003 physical box to a newer 2008 VM.

The process was tiring due to a ton of legacy applications and very complicated share structures.  In order to make sure if it needs to happen again it moves along more smoothly I created a host record in the DNS to use as a universal pointer for the file and print server on all the client machines.

The server is FILEPRINT-100 and the DNS entry is FILEPRINT.  This way if I ever have to make FILEPRINT-200 I can just change the IP on the pointer as I understand it.

Now the problem.

For certain users of which I can find no link or shared factor, when they UNC path to \\FILEPRINT\DATA\ their files are read only.

When they path to \\FILEPRINT-100\DATA the correct permissions apply.

In both cases actually viewing the permissions reveals them to be the same.  For some unknown and crazy reason some users can't edit files when using the manually entered host record.

Another odd problem is any 2003 server we have in our domain can not resolve \\FILEPRINT\ but can ping it.  They can of course resolve \\FILEPRINT-100\ with no problems.

Anyone know what is tripping me up here?
Avatar of djcanter
djcanterFlag of United States of America imageNetwork Administrator

Our community of experts have been thoroughly vetted for their expertise and industry experience.

This problem has been solved!
Unlock 1 Answer and 1 Comment.
See Answers