Anonymous_User Absent Member.
Absent Member.
4028 views

Initial iFolder problems

I have iFolder set-up on my NetWare 6.5 server. The program loads
with
no errors. I followed the directions in the manual and enabled one
user
to use iFolder.

This user is unable to login. I've tried just the user's name, I've tried FQDN but still nothing. Using the FQDN the error is "Invalid
password. Note: passwords are case sensitive."

On the server it says: IS_USER [0]
LOCATE_SERVER jfischer authentication failure

What am I doing wrong?

Thanks.

Jason



Labels (1)
0 Likes
33 Replies
Anonymous_User Absent Member.
Absent Member.

Re: Initial iFolder problems

Check if your ldap is working ok.

Assuming you are using apache for ifolder:
On the apache screen that shows the startup of ifolder, see if you are

getting 'Cannot contact LDAP server (81)'

If so, try PKIDiag.nlm and see what is wrong with your certificates.

Also,
Apache requires a seperate file for the certificate, not in the db, so
you
will need to export the certificate if it is not exported and place it
where
Apache is looking for it.

Phil

"Jason Fischer" <jfischer@kaytee.com> wrote in message
news:rkyTb.5565$Wh.3799@prv-forum2.provo.novell.com...
> I have iFolder set-up on my NetWare 6.5 server. The program loads

with
> no errors. I followed the directions in the manual and enabled one

user
> to use iFolder.
>
> This user is unable to login. I've tried just the user's name, I've


> tried FQDN but still nothing. Using the FQDN the error is "Invalid> password. Note: passwords are case sensitive."
>
> On the server it says: IS_USER [0]
> LOCATE_SERVER jfischer authentication failure
>
> What am I doing wrong?
>
> Thanks.
>
> Jason






0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Initial iFolder problems

Excellent comments, more troubleshooting info:
IFolder simple troubleshooting steps:
1. iFolder 2.x needs eDirectory 8.6.2 or better for LDAP. It will not
work with NW 5.1 DS 8.82 for example.
2. Check that the admin name in the iFolder server config file is
correct
3. Use the clear-text LDAP port for troubleshooting
4. Have iFolder log its screen to a file (below)
5. Turn on LDAP tracing on the LDAP Server/Group Object
6. LOAD DSTRACE. Turn off everything and turn on LDAP, then try to log
in.
7. Does it work if you bypass the proxy in your browser?


Note on 4:
Change startifolder.ncf to read:
LOAD ADDRESS SPACE = IFOLDER APACHE -s -f
SYS:APACHE\IFOLDER\SERVER\HTTPD.CONF
(all on one line)

For some helpful tips:
http://nscsysop.hypermart.net/ifolder.html


0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Initial iFolder problems

I have eDir 8.7.1, the admin name is correct, if I use the clear-text
LDAP port, then I can't even login to the managment page. It doesn't
work if I bypass the proxy.

I had to change my NDS password today, now when I use the new password I
get the 'unprovisioned user" error. Using the old password just tells
me my password is invaild.

Thanks for you help so far!

Jason

AndersG wrote:
> Excellent comments, more troubleshooting info:
> IFolder simple troubleshooting steps:
> 1. iFolder 2.x needs eDirectory 8.6.2 or better for LDAP. It will not
> work with NW 5.1 DS 8.82 for example.
> 2. Check that the admin name in the iFolder server config file is
> correct
> 3. Use the clear-text LDAP port for troubleshooting
> 4. Have iFolder log its screen to a file (below)
> 5. Turn on LDAP tracing on the LDAP Server/Group Object
> 6. LOAD DSTRACE. Turn off everything and turn on LDAP, then try to log
> in.
> 7. Does it work if you bypass the proxy in your browser?
>
>
> Note on 4:
> Change startifolder.ncf to read:
> LOAD ADDRESS SPACE = IFOLDER APACHE -s -f
> SYS:APACHE\IFOLDER\SERVER\HTTPD.CONF
> (all on one line)
>
> For some helpful tips:
> http://nscsysop.hypermart.net/ifolder.html
>
>

0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Initial iFolder problems

Let me ask Novell about this.

- Anders Gustafsson, Engineer, CNE6, ASE
NSC Volunteer Sysop (http://support-forums.novell.com)
Pedago, The Aaland Islands (N60 E20)
Using VA 4.52 build 277 (32-bit) on Windows 2000 build 2195

0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Initial iFolder problems

This is what Novell said:

"Hmm this is strange... It is like we can't contact the server

for grins have him disable and enable the user and see if he can login

if he then can't login have him take an ldap trace (without the debug
option) there has got to be something strange going on

also is he using the webclient or the ifolder client.."

- Anders Gustafsson, Engineer, CNE6, ASE
NSC Volunteer Sysop (http://support-forums.novell.com)
Pedago, The Aaland Islands (N60 E20)
Using VA 4.52 build 277 (32-bit) on Windows 2000 build 2195

0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Initial iFolder problems


Thanks for your help and feedback. I turned on LDAP tracing and here a
couple of the errors that I'm seeing:

13:31:05 AC3D41E0 LDAP: Failed to authenticate local on connection
0x919f3d20, err = failed authentication (-669)
13:33:41 ABEE9120 LDAP: Cannot resolve NDS name 't=KAYTEE' in
ResolveAndAuthNDSName, err = no such entry (-601)

The second one worries me, since that is the name of our eDir. tree.

Jason

AndersG wrote:
> This is what Novell said:
>
> "Hmm this is strange... It is like we can't contact the server
>
> for grins have him disable and enable the user and see if he can login
>
> if he then can't login have him take an ldap trace (without the debug
> option) there has got to be something strange going on
>
> also is he using the webclient or the ifolder client.."
>
> - Anders Gustafsson, Engineer, CNE6, ASE
> NSC Volunteer Sysop (http://support-forums.novell.com)
> Pedago, The Aaland Islands (N60 E20)
> Using VA 4.52 build 277 (32-bit) on Windows 2000 build 2195
>

0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Initial iFolder problems

669 is generally a wrong password. Are you using the webclient or the
ifolder client?

- Anders Gustafsson, Engineer, CNE6, ASE
NSC Volunteer Sysop (http://support-forums.novell.com)
Pedago, The Aaland Islands (N60 E20)
Using VA 4.52 build 277 (32-bit) on Windows 2000 build 2195

0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Initial iFolder problems

The iFolder client. And just to confirm, the iFolder password is the
same as the eDir password, right?

Jason

AndersG wrote:
> 669 is generally a wrong password. Are you using the webclient or the
> ifolder client?
>
> - Anders Gustafsson, Engineer, CNE6, ASE
> NSC Volunteer Sysop (http://support-forums.novell.com)
> Pedago, The Aaland Islands (N60 E20)
> Using VA 4.52 build 277 (32-bit) on Windows 2000 build 2195
>

0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Initial iFolder problems

Jason Fischer,
> And just to confirm, the iFolder password is the
> same as the eDir password, right?
>

Yes.

- Anders Gustafsson, Engineer, CNE6, ASE
NSC Volunteer Sysop (http://support-forums.novell.com)
Pedago, The Aaland Islands (N60 E20)
Using VA 4.52 build 277 (32-bit) on Windows 2000 build 2195

0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Initial iFolder problems

Jason Fischer,
> The iFolder client.
>

CAn you get a packet trace for us. If you do not have a sniffer, then
download and install Ethereal (www.ethereal.com). We need a trace of
comms between client and server. Please include info what the ip
address of client and server is. Mail the trace to d a l t o n AT p e d
a g o DOT f i



- Anders Gustafsson, Engineer, CNE6, ASE
NSC Volunteer Sysop (http://support-forums.novell.com)
Pedago, The Aaland Islands (N60 E20)
Using VA 4.52 build 277 (32-bit) on Windows 2000 build 2195

0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Initial iFolder problems

Traces are complete and on thier way.

Jason

AndersG wrote:
> Jason Fischer,
>
>>The iFolder client.
>>

>
> CAn you get a packet trace for us. If you do not have a sniffer, then
> download and install Ethereal (www.ethereal.com). We need a trace of
> comms between client and server. Please include info what the ip
> address of client and server is. Mail the trace to d a l t o n AT p e d
> a g o DOT f i
>
>
>
> - Anders Gustafsson, Engineer, CNE6, ASE
> NSC Volunteer Sysop (http://support-forums.novell.com)
> Pedago, The Aaland Islands (N60 E20)
> Using VA 4.52 build 277 (32-bit) on Windows 2000 build 2195
>

0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Initial iFolder problems

Just had a quick look and I see traffic to iFolder on both 80 and 8080,
any idea why? Do you have a proxy set?

- Anders Gustafsson, Engineer, CNE6, ASE
NSC Volunteer Sysop (http://support-forums.novell.com)
Pedago, The Aaland Islands (N60 E20)
Using VA 4.52 build 277 (32-bit) on Windows 2000 build 2195

0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Initial iFolder problems

Port 8080 would be the port for our proxy server, however iFolder is not
set-up to use proxy.

Jason

AndersG wrote:
> Just had a quick look and I see traffic to iFolder on both 80 and 8080,
> any idea why? Do you have a proxy set?
>
> - Anders Gustafsson, Engineer, CNE6, ASE
> NSC Volunteer Sysop (http://support-forums.novell.com)
> Pedago, The Aaland Islands (N60 E20)
> Using VA 4.52 build 277 (32-bit) on Windows 2000 build 2195
>

0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Initial iFolder problems

Jason Fischer,
> Port 8080 would be the port for our proxy server, however iFolder is not
> set-up to use proxy.
>

Well, it appears as though it is talking through one...

- Anders Gustafsson, Engineer, CNE6, ASE
NSC Volunteer Sysop (http://support-forums.novell.com)
Pedago, The Aaland Islands (N60 E20)
Using VA 4.52 build 277 (32-bit) on Windows 2000 build 2195

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.