?
Solved

XP following CNAME to file server

Posted on 2011-10-30
14
Medium Priority
?
1,514 Views
Last Modified: 2012-05-12
I am running a Windows Server 2003 R2 file server with multiple shares, let's call it OldFileServer. I have migrated all of my data over to a new file server called NewFileServer. NewFileServer is a Nasuni storage appliance but still presents CIFS shares.

I have changed all login scripts and home drives to point to NewFileServer. Everything works fine with that. Problem is shortcuts or links that are still looking for \\OldFileServer\<share>\etc...

I deleted the A record on my DNS server and created a  CNAME alias directing queries for OldFileServer to NewFileServer.

I test by logging into a Windows 7 machine and try to access \\NewFileServer\ShareA. It works. I then try to access the same place but using the old server name \\OldFileServer\ShareA. It works. I verified I am actually accessing NewFileServer by creating a new file.

When I do the same on a Windows XP machine and try to access \\OldFileServer\ShareA I get a prompt for credentials. Doesn't matter what I enter it won't let me in. I am fine browsing to \\NewFileServer\ShareA. What is different in the way XP handles a CNAME?
0
Comment
Question by:L_Parker
  • 6
  • 5
  • 2
  • +1
14 Comments
 
LVL 21

Expert Comment

by:Alan
ID: 37054933
Hi,

What is the XP machine resolving OldFileServer to?

Try this from an command prompt on the XP machine:

ping -a OldFileServer

then

ping -a NewFileServer

Are they giving the same IP address?

If not, check for where the XP machine is getting is DNS resolution from, including any entries in the HOSTS file on that machine.

Alan.
0
 
LVL 17

Expert Comment

by:sweetfa2
ID: 37054945
The difference will be in the way that XP handles authentication.   I am guessing that the DNS will be resolving the CNAME correctly.

Possibly you will find that the XP is not encrypting passwords in a manner that the CIFS server accepts whereas Windows 7 is (of course it may be reversed).  Been a while since I have played around with this stuff.
0
 

Author Comment

by:L_Parker
ID: 37054976
Found this:
Connecting to SMB share on a Windows 2000-based computer or a Windows Server 2003-based computer may not work with an alias name

It sounds like the Nasuni file server uses CIFS v1. Since it runs some proprietary OS I can't apply the hotfix.  Unless I can figure out a way to get the XP clients to play nice with CNAME's I will have to contact Nasuni to come up with a fix.
0
Get your Disaster Recovery as a Service basics

Disaster Recovery as a Service is one go-to solution that revolutionizes DR planning. Implementing DRaaS could be an efficient process, easily accessible to non-DR experts. Learn about monitoring, testing, executing failovers and failbacks to ensure a "healthy" DR environment.

 
LVL 17

Expert Comment

by:sweetfa2
ID: 37054986
So when you attempt to connect from your XP machine do you get that error:

net view \\NewFileServer

Open in new window


System error 52 has occurred.
A duplicate name exists on the network.
0
 
LVL 21

Expert Comment

by:Alan
ID: 37054999

Have you positively confirmed that the XP machine is resolving the name correctly?

If not, then everything else is moot.

Always best to troubleshoot from the beginning :-)

Alan.
0
 

Author Comment

by:L_Parker
ID: 37055002
Yes, when I ping Old I get the IP for New.

I would actually have to net view \\OldFileServer to test. When I do I get System error 5 has occurred. Access is denied.

I may have jumped to the conclusion about CNAME not working on CIFS 1. Then again I have no problems accessing \\OldFileServer on my Win 7 machines so it has to be a CIFS 1 issue.
0
 
LVL 21

Expert Comment

by:Alan
ID: 37055012
This may be a silly question, but where are all these links?

If they are on an intranet for example, perhaps you could just re-write them all to NewFileServer as it would probably be pretty easy to do.

Alan.
0
 

Author Comment

by:L_Parker
ID: 37055031
Great question. I weighed the headache of trying to find an answer vs impact to users. The links are everywhere. The migrated shares were shared and home drives. I have confirmed links within Outlook emails, Word, and Excel may say P:\example.txt but actually point to \\OldFilerServer\Public\example.txt so those fail.

Office is just the beginning. Hard to say what else will have problems.
0
 
LVL 21

Expert Comment

by:Alan
ID: 37055072
Okay, another question:  How many XP machines do you have, versus Win7 machines?

If a small enough number of XPs could you accept it, and solve problems for those users while you replace those machines?

Alan.
0
 

Author Comment

by:L_Parker
ID: 37055093
It's about 60 on Win7 and 60 XP. Come January 2012, 40 of the XP's are getting replaced with Win7. With 2 ppl taking the calls I think we could get overrun.

I know the root of the problem is something to do with XP using SMB 1.0 vs Win7 using 2.1. I've reached out to Nasuni to check their implementation of CIFS.
0
 
LVL 21

Expert Comment

by:Alan
ID: 37055851
Okay - Good luck, but I wouldn't be getting your hopes up too much on a device like that.

Definitely worth a try though.

Another possibility:  Could you take an old machine (doesn't have to be a server), and set it up to 'mirror' the Nasuni drive?  You could then point the client machines at that to access the files.

You don't mention how much 'stuff' is on there, but a 1TB drive is less than $100 now, so if you re-purpose an old machine with, say, Ubuntu or similar on it, the cost would be just the drive (if you don't have one lying around already).  You wouldn't need to back it up, since it is only a mirror of the source drive anyway.

Alan.

0
 

Expert Comment

by:CL-IS
ID: 37091844
I'm looking to do something similar at the moment, and have read that In sme cases a registry setting to disable strict name checking is required. It may be something similar causing your issue?  http://www.geekshangout.com/node/14
0
 

Accepted Solution

by:
L_Parker earned 0 total points
ID: 37172560
After speaking with Nasuni Support I have found it is a problem in their implementation of SAMBA. They are working on a fix. Thanks for your help.
0
 

Author Closing Comment

by:L_Parker
ID: 37194316
Solved own issue
0

Featured Post

Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

When you start your Windows 10 PC and got an "Operating system not found" error or just saw  "Auto repair for startup" or a blinking cursor with black screen. A loop for Auto repair will start but fix nothing.  You will be panic as there are no back…
This article will help to fix the below errors for MS Exchange Server 2016 I. Certificate error "name on the security certificate is invalid or does not match the name of the site" II. Out of Office not working III. Make Internal URLs and Externa…
In this Micro Tutorial viewers will learn how to use Boot Corrector from Paragon Rescue Kit Free to identify and fix the boot problems of Windows 7/8/2012R2 etc. As an example is used Windows 2012R2 which lost its active partition flag (often happen…
This Micro Tutorial will give you a basic overview of Windows Live Photo Gallery and show you various editing filters and touches to photos you can apply. This will be demonstrated using Windows Live Photo Gallery on Windows 7 operating system.
Suggested Courses

839 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question