2010-06-25 03:03 PM
Running into an interesting problem.
I have two FAS 980s, one running 7.0.5, and another running 7.3.2, they have been running without a hitch for sometime now, fully accessible on UNIX and Windows XP.
I'm in the process of upgrading our systems from XP to VISTA Enterprise and ran across an odd issue, all the CIFS shares have a preceding "1".
so on and so forth.
Funny thing is, when I browse to the share on Vista, the shares looks like this
When I try to connect to the share, I get the following error message:
\\FILER\home1 is not accessible. You might not have the permission to use this network resource. Contact the administrator of this server to find out if you have access permissions. Network Timeout or HCLNFSD/PCNFSD not running on host.
When I try to connect directly to the share, \\FILER\home, I get the following error:
Windows cannot access \\FILER\home
Check the spelling of the name. Otherwise, there might be a problem with your network. To try to identify and resolve problems, click Diagnose. <-- Which, BTW, was pointless
I've check the filer configuration, domain controller, network settings on the PCs, and nothing seems to stand out as a possible culprit.
I believe it might be a Vista setting.
Any help on this matter would be greatly appreciated.
2010-06-27 02:01 PM
Leo, I found a very strange (and really old) article that describe in some way your problem. It's probably not your problem, put maybe you can give it a look:
2010-06-27 03:17 PM
|Windows XP shows filer shares with extra '1' on them|
View Environment section
|When client browses the shares on the filer they see them but there is an extra '1' added to the names. For example if a sharename were 'home' it would show up as 'home1'|
|Keywords : shares have extra characters,hummingbird,sharename wrong|
Be aware that the client application Hummingbird Exceed comes with a NFS client of its own and that it is enabled by default. In essence the client XP machine will have 2 'homes'; "home" and "home1". The client will need to disable the NFS client on Hummingbird to make the extra character go away.
2010-07-19 05:52 AM
Turns out to have a GPO setting on the local workstation
Local Security Policy > Local Policies > Security Options > Microsoft network client: Digitally sign communications (always)
Microsoft network client: Digitally sign communications (always) was set to ENABLED
Changed the setting to DISABLED, rebooted, and I was able to connect the cifs shares.
Thank you everyone for your assistance.