lem9

Absent Member.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
2014-08-28
16:46
1119 views
One server in the tree asks for credentials
Hi,
On Windows 7 with Novell client 2 SP3 (IR3), I am able to type \\SERVERA in the file explorer and I am connected to this server. However, typing \\SERVERB (which is in the same tree) asks for my credentials. This happens not only on my workstation.
If I reboot SERVERB, all is fine for some days, but the problem comes back. I suspect that one of the novell processes is dying but I cannot see which one.
thanks,
Marc Delisle
On Windows 7 with Novell client 2 SP3 (IR3), I am able to type \\SERVERA in the file explorer and I am connected to this server. However, typing \\SERVERB (which is in the same tree) asks for my credentials. This happens not only on my workstation.
If I reboot SERVERB, all is fine for some days, but the problem comes back. I suspect that one of the novell processes is dying but I cannot see which one.
thanks,
Marc Delisle
5 Replies


Knowledge Partner
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
2014-08-28
17:04
lem9;2331188 wrote:
Hi,
On Windows 7 with Novell client 2 SP3 (IR3), I am able to type \\SERVERA in the file explorer and I am connected to this server. However, typing \\SERVERB (which is in the same tree) asks for my credentials. This happens not only on my workstation.
If I reboot SERVERB, all is fine for some days, but the problem comes back. I suspect that one of the novell processes is dying but I cannot see which one.
thanks,
Marc Delisle
If I had to guess I'd say ndsd is not running.
Next time it happens again do:
rcndsd status
does it show "dead"?
lem9

Absent Member.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
2014-08-28
18:05
No, the output is normal, showing it running with the correct tree name.


Knowledge Partner
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
2014-08-29
20:31
lem9;2331225 wrote:
No, the output is normal, showing it running with the correct tree name.
You may need to enable ncp debug logging then and see what the logs show
I think there's 3 logs (if you count the nss2ncp or whatever). I believe it's in the docs on how to set the log level to debug (ncpcon command I think).
It's been a while.
When the problem happens, can you login to NRM as "root"?
If so, then that at least rules out networking issues, and more likely ncp/ndsd issues (can't use CIFS to troubleshoot because CIFS relies upon ncpengine)
lem9

Absent Member.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
2014-09-04
15:54
After enabling ncp debug logging and watching the two logs, I see nothing happenning when I try to connect on my workstation with \\SERVERB. Connecting to NRM as "root" on this server works fine.


Knowledge Partner
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
2014-09-04
17:13
lem9;2332049 wrote:
After enabling ncp debug logging and watching the two logs, I see nothing happenning when I try to connect on my workstation with \\SERVERB. Connecting to NRM as "root" on this server works fine.
If the logs show nothing at all, then I'd say the culprit is ncp or ncpengine died or is having issues.
Normally it would log things and you'll see the userid and attempts to access files, etc. showing up.
You may need to open an SR to figure out why ncp is dying.
I'm not sure if you can restart the ncp processes, to be honest, and maybe that would show something.
NRM doesn't use ncp for authentication, that I'm aware of. If you use a non-root user I believe it uses LUM at that point.