In 5.3 support for Unicode was added. CIFS can only access directories that have been converted to the new Unicode format. Directories that are not in Unicode format are converted automatically to Unicode format when first accessed by CIFS.

But since snapshots are read only, directories in snapshots cannot be converted and are not accessible from CIFS.

Before 5.3, there were two directory formats: those accessed by CIFS (cifs format) and those never accessed by CIFS(non-cifs format). The first time CIFS accessed a directory it would be converted to CIFS format. Non-cifs format directories in snapshots were not accessible from CIFS.

In 5.3, both cifs-format and non-cifs format directories are converted to unicode format when accessed by CIFS. Directories created by CIFS are created in unicode format.

There is an option wafl.create_ucode that can be used to create unicode directories by default from NFS.

Refer to the System Administration Guide for more information.

Joan Pearson

At 11:08 AM 5/3/99 , you wrote:

I upgraded to 5.3.1 this morning. After the upgrade I noticed I was unable to access any snapshots via CIFS. The snapshots would show up in Explorer but when I tried to access the snapshots, even logged in as root, I received a error message "Access is Denied".

I tried several ideas to resolve the issue without any luck. I then ran "cifs testdc" and received the following message:

---

Using Established configuration Current Mode of NBT is H Mode

Netbios scope "" Registered names... NEWTOASTER < 0> WINS Broadcast NEWTOASTER < 3> WINS Broadcast NEWTOASTER <20> WINS Broadcast OSSRTPPROD < 0> WINS Broadcast OSSRTPPROD < 3> WINS Broadcast OSSRTPPROD <20> WINS Broadcast

Testing Primary Domain Controller found 1 addresses

Testing all Domain Controllers found 3 addresses trying 192.168.255.4...192.168.255.4 is alive trying 192.168.255.4...192.168.255.4 is alive trying 192.168.255.14...192.168.255.14 is alive found DC OSSRTPNT40 at 192.168.255.4 Not able to communicate with DC 192.168.255.4 found DC OSSRTPBDC at 192.168.255.14 ______________________________________________________

Thinking the problem was on my end, I terminated CIFS, deleted the filer on my PDC and readded the filer. I rebooted the filer and reran "cifs setup" and kept receiving a error message stating "PDC is not active" and cifs setup would terminate.

I finally dropped back to 5.21.

I reran "cifs testdc" and received the following: ____________________________________________________________________________ ____ testfiler> cifs testdc Using Established configuration Current Mode of NBT is H Mode

Netbios scope "" Registered names... TESTINGFILER < 0> WINS TESTINGFILER < 3> WINS TESTINGFILER <20> WINS OSSRTPPROD < 0> WINS OSSRTPPROD < 3> WINS OSSRTPPROD <20> WINS

Testing Primary Domain Controller found 1 addresses trying 192.168.255.4...192.168.255.4 is alive found PDC OSSRTPNT40

Testing all Domain Controllers found 3 addresses trying 192.168.255.4...192.168.255.4 is alive trying 192.168.255.4...192.168.255.4 is alive trying 192.168.255.14...192.168.255.14 is alive found DC OSSRTPBDC found DC OSSRTPNT40 found DC OSSRTPBDC ____________________________________________________________________________ ____________

Finally, I reran cifs setup without a problem. I was able to get back into the snapshots. Has anyone else came across a similar issue with 5.3.1 and if so how did you resolve?