drominore Absent Member.
Absent Member.
1490 views

File/Directory visibility issues

Sirs:
We are experiencing something I have never seen before! Although its not a true hang or abend, the situation is troublesome enough to qualify as a problem so forgive the post location if it is wrong.
We have a user who is on a WinXP-SP2 system. She saves data to an NW65SP7 personal drive mapped to J:. Although she says she did not do anything strange, she *did* say she was playing around a bit. Now, from her station logged in as her she cannot see ANY folders and some files are also missing. When I review her home directory from MY PC I see the same situation: some files are there but all directories are gone.
Now here comes the real odd part. I have researched things like hidden directories, etc. I ran an ADS streams checker without anything becoming visible or flagged. I next went to the server console and ran Monitor. Yes, they are there and visible under File/Lock activity. Now, lets experiment. I create a new directory, call it 123. I see the directory. Exit the location then come back. The directory is NOT visible. Go to crteate a NEW directory withthe name 123 and I am told there is one already with that name. Turn on all file view options in explorer (hidden, system, etc). Still nothing. OK, fire up the trusty DOS prompt. Go to the home directory. DIR shows nothing just like explorer did. Do a "cd 123" and the prompt now shows "j:\123->". The directories and files are all there but for some reason something she did has caused any folder or I think anything updated to become invisible, not hidden. I have checked all the simple things. I have run dir /ah, /as all without success. This is an NSS volume and is the ONLY user with a problem here.
Can ANYONE give me a path to follow on this issue? I have searched high and low, google and NKB without anything that makes any sense or applies. As I said, the closest was the ADS streams but no file seems to show any of the naming structure that specifies.

MJK
Labels (2)
0 Likes
10 Replies
mathew35 Absent Member.
Absent Member.

Re: File/Directory visibility issues

I've had a similar problem in the past - I ran a dsrepair and I cleaned it right up.
Hope this helps.
0 Likes
drominore Absent Member.
Absent Member.

Re: File/Directory visibility issues

mathew35;1466860 wrote:
I've had a similar problem in the past - I ran a dsrepair and I cleaned it right up.
Hope this helps.


Just finished DSREAPIR --> Unattended full repair.

Nothing changed, and the master is on the server with the directory issue. 14 errors found but mostly timestamp issues.

The elusive reason must still be out there!

MJK
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: File/Directory visibility issues

First, don't trust the client. Windows will go to great lengths to hide
things it thinks you shouldn't get to. AV software can do the same.

Go to the server, LOAD EDIT, press INS and use it to drill down through
the directory structure to an invisible folder / file. If you CAN see
them from EDIT, bit NOT from the client, then its a rights issue or an
instance of the user using IRFs to block their own access or something
stoopid.

I say NOT to use NCO on the server because it uses Java and that can
result in the client libraries being used - so its the same as using a
NCP client. Using EDIT used the C libraries to access the file
systems, and so generally side steps rights issues.

If you cannot see the files from EDIT, then its corruption on the volume
and then you need to take the next steps to diagnose this as such.

-- Bob

- - - - - - - - - - - - - - - - -
Robert Charles Mahar
Traffic Shaping Engine for NetWare
http://www.TrafficShaper.com
- - - - - - - - - - - - - - - - -


drominore wrote:
> Sirs:
> We are experiencing something I have never seen before! Although
> its not a true hang or abend, the situation is troublesome enough to
> qualify as a problem so forgive the post location if it is wrong.
> We have a user who is on a WinXP-SP2 system. She saves data to an
> NW65SP7 personal drive mapped to J:. Although she says she did not do
> anything strange, she *did* say she was playing around a bit. Now, from
> her station logged in as her she cannot see ANY folders and some files
> are also missing. When I review her home directory from MY PC I see the
> same situation: some files are there but all directories are gone.
> Now here comes the real odd part. I have researched things like
> hidden directories, etc. I ran an ADS streams checker without anything
> becoming visible or flagged. I next went to the server console and ran
> Monitor. Yes, they are there and visible under File/Lock activity. Now,
> lets experiment. I create a new directory, call it 123. I see the
> directory. Exit the location then come back. The directory is NOT
> visible. Go to crteate a NEW directory withthe name 123 and I am told
> there is one already with that name. Turn on all file view options in
> explorer (hidden, system, etc). Still nothing. OK, fire up the trusty
> DOS prompt. Go to the home directory. DIR shows nothing just like
> explorer did. Do a "cd 123" and the prompt now shows "j:\123->". The
> directories and files are all there but for some reason something she
> did has caused any folder or I think anything updated to become
> invisible, not hidden. I have checked all the simple things. I have run
> dir /ah, /as all without success. This is an NSS volume and is the ONLY
> user with a problem here.
> Can ANYONE give me a path to follow on this issue? I have searched
> high and low, google and NKB without anything that makes any sense or
> applies. As I said, the closest was the ADS streams but no file seems
> to show any of the naming structure that specifies.
>
> MJK
>
>

0 Likes
drominore Absent Member.
Absent Member.

Re: File/Directory visibility issues

Thanks Robert but I can definately see the directories in Monitor-File Locks & in Edit. I've checked rights and IRF's even to the point of comparing them to another account side by side.... This really has me befuddled. I can feel it has to be something NDS related but its elisive as I have full access and still see the same as the user does. Think I'll let it run DSREPAIR again and see what happens..
MJK




If you cannot see the files from EDIT, then its corruption on the volume
and then you need to take the next steps to diagnose this as such.

-- Bob

- - - - - - - - - - - - - - - - -
Robert Charles Mahar
Traffic Shaping Engine for NetWare
Traffic Shaper and Bandwidth Manager for NetWare
- - - - - - - - - - - - - - - - -
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: File/Directory visibility issues

Why would it be NDS related? NDS has nothing to do with your file system
rights, unless you grant file system rights by granting S NDS rights to
the server object. Don't keep running DSrepairs, if one doesn't fix it
then more will not help.

It sounds more like a licensing or UTF-8 issue to me. Do VERSION on the
server console and report the results please; is this happening on more
than one server?

What client32 version?
--
Andrew C Taubman
Novell Support Forums Volunteer SysOp
http://forums.novell.com/
(Sorry, support is not provided via e-mail)

Opinions expressed above are not
necessarily those of Novell Inc.
0 Likes
drominore Absent Member.
Absent Member.

Re: File/Directory visibility issues

OK sorry the long delay; even us technology people get a vacation once and a while.. I checked the UTF-8 settings a while back when I came across the issue. The settings were as recommended by the Novell tech entry I saw; I did not need to chenge anything....

I thought it was an NDS issue as NDS controls access to the visibility of the file system. No errors beyond a few time stamps.... OK, on the server in question, the version command shows:

Novell Open Enterprise Server, Netware 6.5
Support Pack Revision 06
Server Version 5.70.06 October 26, 2006
Novell eDirectory Version 8.7.3.9 SMP
NDS Version 10553.73 October 9, 2006
Server License: Novell Netware 6 Server 650 SN:xxxxxxxxxxx
User Licenses: Audited


On the workstation, the client version is 4.91.1.20050819

The setting for UTF-8 is Advanced Settings -- Use UTF8 encoding and NCPs is turned on.

She says she did something then she didn't see directories and newly created files. I can see them in Console Monitor but NOT from my machine in the same home directory. I have even run nss /VisibilityRebuild=<VOLUMENAME> on the volume without any errors or issues. This is only one user affected but it is a serious hinderance to this instructor. At this point I'd love to try whatever I can but the truth is I've exhausted everything I could think of....

MJK



Andrew C Taubman;1468051 wrote:
Why would it be NDS related? NDS has nothing to do with your file system
rights, unless you grant file system rights by granting S NDS rights to
the server object. Don't keep running DSrepairs, if one doesn't fix it
then more will not help.

It sounds more like a licensing or UTF-8 issue to me. Do VERSION on the
server console and report the results please; is this happening on more
than one server?

What client32 version?
--
Andrew C Taubman
Novell Support Forums Volunteer SysOp
http://forums.novell.com/
(Sorry, support is not provided via e-mail)

Opinions expressed above are not
necessarily those of Novell Inc.
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: File/Directory visibility issues

drominore wrote:

> She says she did something then she didn't see directories and newly
> created files. I can see them in Console Monitor but NOT from my
> machine in the same home directory. I have even run nss
> /VisibilityRebuild=<VOLUMENAME> on the volume without any errors or
> issues. This is only one user affected but it is a serious hinderance
> to this instructor. At this point I'd love to try whatever I can but
> the truth is I've exhausted everything I could think of....

I had a similar problem. We found out that one filename was some kind of
corrupted. If windows explorer or dos dir came to that file it stopped
showing anything beyond. We tried to do dir commands with different sort
options and suddenly found some more files. We even were able to change to
directories which weren't seen. Finally we found the problematic file and
deleted it (i think with nrm) and than all was ok.
--
Netprofi
Germany
MCNE, CLP
0 Likes
Knowledge Partner
Knowledge Partner

Re: File/Directory visibility issues

Hi,

drominore wrote:
>
> On the workstation, the client version is 4.91.1.20050819


I'd start by updating that, it's oooollllldddd....

CU,
--
Massimo Rosen
Novell Product Support Forum Sysop
No emails please!
http://www.cfc-it.de
0 Likes
drominore Absent Member.
Absent Member.

Re: File/Directory visibility issues

OK, resolved but it looks like the culprit was an odd character as a directory name. The teacher *remembered* that she had copied a student issue to her network drive for safekeeping and deleted it this morning. Thanks for all the help everyone!
MJK


mrosen;1470755 wrote:
Hi,

drominore wrote:
>
> On the workstation, the client version is 4.91.1.20050819


I'd start by updating that, it's oooollllldddd....

CU,
--
Massimo Rosen
Novell Product Support Forum Sysop
No emails please!
Untitled Document
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: File/Directory visibility issues

drominore wrote:

>
> OK, resolved but it looks like the culprit was an odd character as a
> directory name. The teacher *remembered* that she had copied a student
> issue to her network drive for safekeeping and deleted it this morning.
> Thanks for all the help everyone!
> MJK
>

Good to here but on the other hand at least strange to see.
--
Netprofi
Germany
MCNE, CLP
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.