Big news! The community will be moving to a new platform April 21. Read more.
Big news! The community will be moving to a new platform April 21. Read more.
Absent Member.
Absent Member.
2575 views

Novell Client 2 SP3 for Windows IR1

Just installed the latest Windows 7 Client and hoped
it would solve the problem of occasional empty mapped drives.

This has been a real headache as I am constantly getting calls
from users that their files have disappeared. They reboot
and the files are back, but sometimes only temporarily.

Now it is even worse. After rebooting several times now
I cannot see any files on certain drives. They are drives
mapped to NW6 SP8 servers.
Labels (1)
0 Likes
8 Replies
Absent Member.
Absent Member.

On 03/29/2013 05:06 PM, sdoerr wrote:
>
> Just installed the latest Windows 7 Client and hoped
> it would solve the problem of occasional empty mapped drives.
>
> This has been a real headache as I am constantly getting calls
> from users that their files have disappeared. They reboot
> and the files are back, but sometimes only temporarily.
>
> Now it is even worse. After rebooting several times now
> I cannot see any files on certain drives. They are drives
> mapped to NW6 SP8 servers.
>
>



Are this users accessing the server thru citrix session, xenapp maybe?
0 Likes
Absent Member.
Absent Member.

No, just run-of-the-mill workstations and or laptops
running Window 7 64bit.

I friend mentions oplocks and file caching but after checking
the autoexec.ncf I can see both are set to off.
0 Likes
Absent Member.
Absent Member.

> No, just run-of-the-mill workstations and or laptops
> running Window 7 64bit.
>
> I friend mentions oplocks and file caching but after checking
> the autoexec.ncf I can see both are set to off.


Happens here as well but not very often. Usually on 'power user'
workstations that have a lot of Excel/Word files open.
0 Likes
Commodore
Commodore

we have problems with IR1 too - suddenly we could not start consoleone.exe from \\fileserver\sys\public\mgmt\... because the sys-volume seems to be empty !
I checked it and found for the moment, that this problem only exists for access of traditional-filesystem sys (not nss-based sys)
Rolled back to sp3 + post sp3 nss-patch solved the problem with empty sys-volume.

But, generally - where is the good old novell quality ?
- stable and fast winxp-novell-client versus very slow for gis-applications and cache-problematic win7-novell client
- distributed and stopped groupwise 8.0.3, zcm 11.2.3, kernel-error for oes11sp1, ...
0 Likes
Absent Member.
Absent Member.

On 04/05/2013 02:26 PM, goessel wrote:
>
> we have problems with IR1 too - suddenly we could not start
> consoleone.exe from \\fileserver\sys\public\mgmt\... because the
> sys-volume seems to be empty !
> I checked it and found for the moment, that this problem only exists
> for access of traditional-filesystem sys (not nss-based sys)
> Rolled back to sp3 + post sp3 nss-patch solved the problem with empty
> sys-volume.


Novell is aware and working on it

0 Likes
Absent Member.
Absent Member.

After reading your post I went and checked and sure enough the only volumes that
appear to have no files are Traditional. None of the NSS volumes were empty.

Hope they can fix this. These volumes have been in place for a decade.
Unsure if I want to do the conversion at this time.
0 Likes
Absent Member.
Absent Member.

Hi

here, we have the same problem.
No data on traditional volumes.

hope also that Novell will fix this.
Andrej
0 Likes
Absent Member.
Absent Member.

> here, we have the same problem.
> No data on traditional volumes.


NSS here as well.
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.