Bug 20885
Summary: | ncpfs and netware 5.1 servers... | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Need Real Name <robertcn> |
Component: | ncpfs | Assignee: | Phil Knirsch <pknirsch> |
Status: | CLOSED NOTABUG | QA Contact: | David Lawrence <dkl> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 7.0 | CC: | bjh21, rvokal |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2002-01-17 11:08:25 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Need Real Name
2000-11-14 22:53:25 UTC
Ooops. The version of Redhat that the ncpfs wasn't broken on was a 6.0 box. I've just run into this exact error, and worked-around the problem. On our network 7.1 users could not connect to some of the Netware shares/servers. 6.1 users could connect to all. The problem exists in 7.1, but not in 6.1. I'm not sure about 6.2 or 7.0. So a work-around is to revert to the version of ncpfs that was in RedHat 6.1: 1. Download ncpfs-2.2.0.16.a-1.src.rpm from ftp://ftp.redhat.com/pub/redhat/linux/6.1/en/os/i386/SRPMS/ 2. As superuser: rpm -e ncpfs-2.2.0.18-3 rpm --rebuild ncpfs-2.2.0.16.a-1.src.rpm cd /usr/src/redhat/RPMS/i386 rpm -ivh ncpfs-2.2.0.16.a-1.i386.rpm Redhat: It would be great to have this fixed in a future release. And perhaps an update for 7.2 if it's not fixed in that. I don't have a copy as it has not been released yet. Best wishes, Alastair. A note as I have been remiss in keeping track of this bug. If you need to log into an nds server with ncpfs and the server is IP only, use the -A flag and give it the FQDN of the server (or just the server name if you have resolv.conf looking up the right address) and it'll work as well. As this seems to be more of a configuration issue and the comments already provide a workaround resp. a correct configuration for the problem i'm closing the bug as NOTABUG. Read ya, Phil |