Highlighted
Absent Member.
Absent Member.
5553 views

OES2 sp1 LOCAL_CODE_PAGE

I`m testing OES2 sp1. in windows environment all test are successful. In linux environment with protocol NCP and mount options codepage=cp866,iocharset=utf8 (for support local language) in new version of OES now shown all files(folders are visible). Parameter LOCAL_CODE_PAGE is CP866 on server. Server is OES2 sp1 and client is OES2 sp1. On previous version OES2 is work correctly.
Labels (2)
0 Likes
24 Replies
Highlighted
Acclaimed Contributor.
Acclaimed Contributor.

Re: OES2 sp1 LOCAL_CODE_PAGE

solomin,

hwo do you make that linux ncp connections ?

Novell Client for Linux or ncpmount ?

Can you provide us the output ot the command "locale" ?

Rainer
0 Likes
Highlighted
Absent Member.
Absent Member.

Re: OES2 sp1 LOCAL_CODE_PAGE

Yes, i mount via NCP.

I use ncpmount(e.g. record in /etc/fstab like "username mount_point ncpfs mount_options...")

locale:
LANG=en_US.UTF-8
LC_CTYPE="en_US.UTF-8"
LC_NUMERIC="en_US.UTF-8"
LC_TIME="en_US.UTF-8"
LC_COLLATE="en_US.UTF-8"
LC_MONETARY="en_US.UTF-8"
LC_MESSAGES="en_US.UTF-8"
LC_PAPER="en_US.UTF-8"
LC_NAME="en_US.UTF-8"
LC_ADDRESS="en_US.UTF-8"
LC_TELEPHONE="en_US.UTF-8"
LC_MEASUREMENT="en_US.UTF-8"
LC_IDENTIFICATION="en_US.UTF-8"
LC_ALL=

Only in UTF-8 locale russian file names and folder names display correctly(on ncp shares with OES2 without sp1 as server or locally on both version OES2).
0 Likes
Highlighted
Absent Member.
Absent Member.

Re: OES2 sp1 LOCAL_CODE_PAGE

with mount options "nolong" (and also codepage=cp866,iocharset=utf8) all filenames displays correctly but with short(cutted) filenames.
0 Likes
Highlighted
Knowledge Partner
Knowledge Partner

Re: OES2 sp1 LOCAL_CODE_PAGE

Hi,

solomin wrote:
>
> Yes, i mount via NCP.
>
> I use ncpmount


Ncpmount doesn't support UTF8, and your symptoms clearly show that there
are filenames stored on the server that cannot be translated to your
chosen codepage (that's when they stop to show in clients).

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

Re: OES2 sp1 LOCAL_CODE_PAGE

mrosen;1718875 wrote:
Hi,

solomin wrote:
>
> Yes, i mount via NCP.
>
> I use ncpmount


Ncpmount doesn't support UTF8, and your symptoms clearly show that there
are filenames stored on the server that cannot be translated to your
chosen codepage (that's when they stop to show in clients).

CU,
--
Massimo Rosen
Novell Product Support Forum Sysop
No emails please!
Untitled Document


I use parameter LOCAL_CODE_PAGE for older client and set it to my codepage(cp866).
UTF-8 - is the codepage what display file names to my screen (parameter iocharset=utf8 in fstab), from server i tailk in cp866 codepage (parameter codepage=cp866 in fstab).

Why it perfectly works on OES2 without sp1?

May be i dont understand, ncpmount <=> using ncpfs in fstab?

Furthermore, if i set parameter codepage to utf8 in fstab on client machine and LOCAL_CODE_PAGE to UTF-8 on server side, all russian characters (both files and folders shown perfectly), but with these case all other old client (Win95, Win98...) not work with server.
0 Likes
Highlighted
Absent Member.
Absent Member.

Re: OES2 sp1 LOCAL_CODE_PAGE

When using cp866 as LOCAL_CODE_PAGE and in fstab, what exactly is wrong with your files? Which if the following 3 is the coase:

1) You don't see any files at all

2) Some files are missing and those that show are correct

3) Files are showing but have incorrect names

Also, have you veified that Windows 95/98 clients can really connect fine with cp866 and that no files are missing or are shown incorrectly?

Finally, have you tested whether it is the NCP server or ncpfs that is the problem? E.g. did you try connecting from an OES2 (without SP1) to an OES2SP1 server, and did you try connecting from an OES2SP1 server to an OES2 (no SP1) server?
0 Likes
Highlighted
Absent Member.
Absent Member.

Re: OES2 sp1 LOCAL_CODE_PAGE

My case is 1(I don't see any files at all), but i see all folders(including folders with cyrillic symbols).
Windows 95/98 clients work fine with that configuration(no files are missing or are shown incorrectly).
My means, these is problem of NCP server of OES2 sp1. I try different configuration:
1. OES2sp1(client)-OES2sp1(server)
2. CentOS(client)-OES2sp1(server)
3. Fedora(client)-OES2sp1(server)
4. Win95/98/2000/XP/Vista/2003(client)-OES2sp1(server)
5. OES2nosp1(client)-OES2nosp1(server)
6. CentOS(client)-OES2nosp1(server)
7. Fedora(client)-OES2nosp1(server)
8. Win95/98/2000/XP/Vista/2003(client)-OES2nosp1(server)
9. And also all

These problem exist only with Linux ncpfs and server's version OES2 sp1.
And also all these clients with NW6.0 as server.
0 Likes
Highlighted
Absent Member.
Absent Member.

Re: OES2 sp1 LOCAL_CODE_PAGE

solomin wrote:

>These problem exist only with Linux ncpfs and server's version OES2
>sp1.
>And also all these clients with NW6.0 as server.


You mean the problem also exists when you access a NetWare 6.0 server?

Anyway, here is some background information on clients and character
handling:

Up to NetWare 6.0, the NCP protocol did not have support for unicode.
Instead, file names were always represented in the code page of the
server, and therefore the NCP client and the server had to be configured
to use the same code page in order to have the same understanding of
special characters in file names.
It's only starting with NetWare 6.5, that Novell introduced new verbs in
the NCP protcol to natively handle UTF8 and thus allow a correct
understaning of characters in file names indpendently of the code page
used on the server and client side. However only clients written to
support these new NCP verbs can take advantage of native UTF8 support in
the NCP protocol. This is the case fot he following clients:

Novell client 4.91 (or later) for Windows 2000/XP
Novell Client for Vista
Novell Client for Linux (not to be confused with ncpfs)

The following clients do not have native UTF8 support and only work (more
or less well) if client and server agree on using the same code page:
Novell Client for NT/2000/XP version 4.90 or older
Novell Client for Windows 95/98
Any Novell Client for DOS
ncpfs for Linux

While none of these clients are officially supported as clients for OES2,
Novell has nevertheless included the downward compatibility option of the
"LOCAL_CODE_PAGE" setting which gives a kind of a best effort attempt to
support obsolete clients.

It is a bit suprising that in your case, the client for Windows 95/98
works, but ncpfs does not. However I guess this means that ncpfs is using
even more obsolete NCP options than the Windows 95/98 client and that
these protocol options are no longer properly supported in OES2SP1. Note
that ncpfs is not written by Novell but by other people and is based on
reverse engineering of the NCP protocol on old NetWare versions.
The best solutionm would of course be if Novell would officially support
running the Novell client for Linux on OES2 servers. In that case, you
would have a supported and fully utf8 aware client without any limitations
or quirks on file names.

In any case, I can try if I can get Novell interrested in looking into
your problem. For that however I need packet traces. Best would be to have
4 packet traces for the 4 following scenarios (in each case using cp866)

- a Windows 95/98 client making a directory listing of an OES2 server
- an ncpfs making a directory listing of an OES2 server
- a Windows 95/98 client making a directory listing of an OES2SP1 server
- an ncpfs client making a directory listing of an OES2SP1 server

Short of finding a solution for ncpfs, the onl workaround I can see is use
another protocol to make server to server connections, like nfs or
cifs/samba.

--
Marcel Cox
http://support.novell.com/forums
------------------------------------------------------------------------
Marcel Cox's Profile: http://forums.novell.com/member.php?userid=8
0 Likes
Highlighted
Absent Member.
Absent Member.

Re: OES2 sp1 LOCAL_CODE_PAGE

Where can i placen trace files?
0 Likes
Highlighted
Absent Member.
Absent Member.

Re: OES2 sp1 LOCAL_CODE_PAGE

solomin wrote:

>Where can i placen trace files?


You can zip them into a single zip file and post it here as an attachment,
or laternately, you can also email them to me at marcel . cox at gmail . com

--
Marcel Cox
http://support.novell.com/forums
------------------------------------------------------------------------
Marcel Cox's Profile: http://forums.novell.com/member.php?userid=8
0 Likes
Highlighted
Absent Member.
Absent Member.

Re: OES2 sp1 LOCAL_CODE_PAGE

I sent zip archive via email with short comment.

P.S. With LOCAL_CODE_PAGE parameter is set to CP437, these problem with ncpfs exist too.
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.