Both are in wins.

However the one that fails is dynamic and the one that works is a static.

Both are in dns.

It doesn't seem to help.

Cheers

Matt

-----Original Message----- From: Willeke, Jochen Jochen.Willeke@wincor-nixdorf.com To: Davies,Matt; Brent Ellis interi@bu.edu; Callaway, Michael Mcallaway@ntta.org CC: toasters@mathworks.com toasters@mathworks.com Sent: Thu Jan 11 18:18:21 2007 Subject: RE: Vista and Netapp??

Hi,

is it possible that the name which does not work is equal to the wins-name, and the second name is not registered with wins?

Regards

Jochen

________________________________

From: owner-toasters@mathworks.com [mailto:owner-toasters@mathworks.com] On Behalf Of Davies,Matt Sent: Thursday, January 11, 2007 6:04 PM To: Brent Ellis; Callaway, Michael Cc: toasters@mathworks.com Subject: RE: Vista and Netapp??

I found a way round this problem, or at least it seems to work for me.

From a vista machine I am unable to connect to the shares using the filer host name, but we have our filers advertise an additional netbios name (for DR reasons), and for some reason I can connect to the shares by using the additional netbios name.

Hope this helps

Matt

__________________________________________________ Matt Davies

General Atlantic 83 Pall Mall London SW1Y 5ES UK Tel: +44 (0) 20 7484 3203 Fax: +44 (0) 20 7484 2803 Mobile: +44 (0) 77 7559 4265 http://www.generalatlantic.com/ Email: mdavies@generalatlantic.com mailto:mdavies@generalatlantic.com __________________________________________________

________________________________

From: owner-toasters@mathworks.com [mailto:owner-toasters@mathworks.com] On Behalf Of Brent Ellis Sent: 11 January 2007 16:21 To: Callaway, Michael Cc: toasters@mathworks.com Subject: Re: Vista and Netapp??

We currently use this filer in production with windows 2000 and windows xp clients. I have had no user permission problems up until this point. The filer allowed us to join it to our domain and we can access the filer from windows clients and set AD permissions on folders in the file share using windows xp or 2000.

I am guessing this is Microsofts way of making windows more secure or maybe a small protocol difference with CIFS in Vista that the filer is not able to deal with.

BTW as I said I can connect to the filer with CIFS using accounts I explicitly setup in the filer, just not active directory accounts.

Brent Ellis Computing Services Group Boston University 617-358-2486 interi@bu.edu cashelp@bu.edu

On Jan 11, 2007, at 11:14 AM, Callaway, Michael wrote:

Can other non-visa clients access this CIFS share in the way you want your vista box to access it? Just because your user is in AD, doesn't give it permissions on the share. You need to make sure that user has access on the filer through group and user permissions as well as the shares have to be given to that user or a group that user is in. I would first make the exact same setup on an XP or 2000 box (whichever you have) and determine if it's a user setup problem or something that can be directly attributed to Vista.

-- *--------------------------------------- Michael Callaway (Server Administrator) North Texas Tollway Authority http://www.ntta.org http://www.ntta.org/ 214-461-2033 o 214-325-5523 m 972-930-2633 f ----------------------------------------

________________________________

From: owner-toasters@mathworks.com [mailto:owner-toasters@mathworks.com] On Behalf Of Brent Ellis Sent: Thursday, January 11, 2007 9:09 AM To: toasters@mathworks.com Subject: Vista and Netapp?? I am just starting to test Vista against our netapp FAS 3020c filers. We use these machines with the CIFS license for basic file sharing. The shares have Active Directory permissions applied to them and the servers have been added to AD. In Vista, I cannot connect to the servers using an AD account. Only the accounts created on the filer itself will allow me to connect from Vista.

Has anyone run into this? Any solutions? Brent Ellis Computing Services Group Boston University 617-358-2486 interi@bu.edu cashelp@bu.edu

____________________________________________________________

This e-mail (including all attachments) is confidential and may be privileged. It is for the exclusive use of the addressee only. If you are not the addressee, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, please erase all copies of the message and its attachments and notify us immediately at help@generalatlantic.com. Thank You.