Anonymous_User Absent Member.
Absent Member.
1036 views

Server file sharing protocol being used - how to find?

Hi All,

Just some background before I get into the problem.

I have two virtual servers that on face value look identical, both are SLES 11 SP3 with OES SP2, one is for user home directories, the other team shared directories.

Users on Win 7 workstations with either the older Novell client 2 (SP4-IR2 or SP3-IR10) or the newer OES client 2 Sp4 (IR 4).

Now for the problem.

Users with the OES client will experience problems with some files in their Home directory, but if the same problem files are copied\moved to the Shared server they have no problems at all.

We have also noticed that after a reboot, the problem files (on Home server) will load correctly on the first request, but each attempt thereafter will fail. This failure has not been experienced from the Shared server.

The failure is not isolated to a particular file type, just the server. Also, any other operation on the problem files from the Home server will fail. I thought it could be caused by file locking, but that is not the case as they are able to load the problem files from a computer with the Novell client.

I have un-install the OES client and install the Novell client and had the users again load the problem files from their Home directory, no problems were experienced, even after several load requests.

I originally thought that the problem may be the OES client, but as the problem is only occurring on one server, then there must be some differences between the two servers in the way files are access. I'm suspecting it might have something to do with the file sharing protocol being used, but don't know how to find this information.

Can anyone advise me on how to determine this?

Or am I on the wrong track?

Thanks
Alan
Labels (1)
0 Likes
3 Replies
Knowledge Partner
Knowledge Partner

Re: Server file sharing protocol being used - how to find?

Am 19.01.2017 um 04:10 schrieb Alan Lew:
> Hi All,
> Just some background before I get into the problem.
> I have two virtual servers that on face value look identical, both are SLES 11
> SP3 with OES SP2, one is for user home directories, the other team shared
> directories.
> Users on Win 7 workstations with either the older Novell client 2 (SP4-IR2 or
> SP3-IR10) or the newer OES client 2 Sp4 (IR 4).
> Now for the problem.
> Users with the OES client will experience problems with some files in their Home
> directory, but if the same problem files are copied\moved to the Shared server
> they have no problems at all.
> We have also noticed that after a reboot, the problem files (on Home server)
> will load correctly on the first request, but each attempt thereafter will fail.
> This failure has not been experienced from the Shared server.
> The failure is not isolated to a particular file type, just the server. Also,
> any other operation on the problem files from the Home server will fail. I
> thought it could be caused by file locking, but that is not the case as they are
> able to load the problem files from a computer with the Novell client.
> I have un-install the OES client and install the Novell client and had the users
> again load the problem files from their Home directory, no problems were
> experienced, even after several load requests.
> I originally thought that the problem may be the OES client, but as the problem
> is only occurring on one server, then there must be some differences between the
> two servers in the way files are access. I'm suspecting it might have something
> to do with the file sharing protocol being used, but don't know how to find this
> information.
> Can anyone advise me on how to determine this?
> Or am I on the wrong track?


For starters, the only difference between the "Novell" and the "OES"
client is really the name, and that the OES Client is newer. It has
simply been renamed along the way, but technically it works exactly the
same, especially using the same protocol (NCP).

However, there are of course some difference as time goes by and
features are added, bugs fixed (and new bogs introduced unfortunately).

I can only guess that your problem must be in some recently added
enhancements to NCP that only the newer client understands and uses,
which leads me to believe that possibly you need to patch your servers,
and that the patch status might also be the difference between the two.

CU,
--
Massimo Rosen
Micro Focus Knowledge Partner
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
Anonymous_User Absent Member.
Absent Member.

Re: Server file sharing protocol being used - how to find?

Thanks Massimo,

I suspected that there may have been some patches applied to one server that was not applied to the other.
Will look at doing that soon.

regards
Alan
0 Likes
Knowledge Partner
Knowledge Partner

Re: Server file sharing protocol being used - how to find?

In article <5880C8C3.CD2E.006E.1@law.anu.edu.au>, Alan Lew wrote:
> Can anyone advise me on how to determine this?


After you've checked patch levels and if that doesn't do the trick,
then time to check the basics.

Make sure that neither server is struggling with basics of RAM, CPU, or
space (especially on root). Ganglia can really help on that front,
http://serverIPorName/gweb
'free -m', 'df -h', and 'top' are the command line way to spot check.
For details on those 3 commands:
http://www.konecnyad.ca/andyk/nixadmin.htm

OES11 optimization TID
https://www.novell.com/support/kb/doc.php?id=7003585


Andy of
http://KonecnyConsulting.ca in Toronto
Knowledge Partner
http://forums.novell.com/member.php/75037-konecnya
If you find a post helpful and are logged in the Web interface, please
show your appreciation by clicking on the star below. Thanks!

___
Andy of Konecny Consulting in Toronto
Knowledge Partner Profile
If you find a post helpful, click the Like button below. Thanks!
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.