Re: [Ani-users] ANI boot floppy fails to connect to share, then kernel panics on Dell OptiPlex GX150

[Hagen M. <h.m...@su...>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
 

Doherty, Chris - Elmira, ON wrote:

| I am using ANI 1.1.1 with the boot floppy, since I am waiting on
| approval to make the necessary changes to the DHCP server.  The
| server is a Windows Server 2003 SP1 HP box. I have performed all
| the configuration steps listed on
| http://ani.sourceforge.net/installation.php?lang=en witrh the
| exception of the extra DHCP options, but those have been added
| manually to the floppy image using ANIDisk.
|
| The client is a Dell OptiPlex GX150 SFF with an integrated 3Com
| 3C905C NIC ("Tornado").  The NIC driver appears to load
| successfully, but then I get the following boot messages:
|
| Connection to '\\cael-dp01\AI386' failed!                    failed
|  Kernel panic: Attempted to kill init!
|

| From the init.rc, it looks like smbmount is failing, but I have no
| idea why.
|
| One possible answer is this whole encrypted password nonsense.
| While I realize the rationale behind encrypting the password, if
| that's going to be a built-in part of the system, the documentation
|  needs to clearly and explicitly state exactly where the encrypted
| password is entered and where the plaintext password is to be
| entered.  For instance, when I am creating the ANI access user on
| the server, do I use the encrypted password or the plaintext
| password?  When I set the custom options on the DHCP server, do I
| use the plaintext password or the encrypted password?  When I
| create the boot floppy using ANIDisk, do I specify the plaintext
| password or the encrypted password?  For that matter, do I need to
| specify the username as just 'aniuser' or do I need to use the
| fully-qualified 'cael-dp01\aniuser' syntax in ANIDisk?

Did you consider that the password must be provided as plain text, if
you add the options manually to the ANI disk?
To debug it, you can remove the comment for the 'openshell' parameter
in ani.cf0 on the floppy disk (OPENSHELL=y) and try to connect manually:

smbmount //cael-dp01/ai386 /tmp -ousername=aniuser/cael-dp01%<plain
text passwd>

The account will be composed of the option  'ORGUNIT' and 'INSTACC'.
But you can assign the composed account name on the floppy disk as
mentioned:
- ---snip---
INSTACC='cael-dp01\aniuser'
- ---snip---

The composed account name must then be enclosed by single quotas.

If the password is provided by the floppy disk, the call of smbmount
is as shown above and the DHCP option won't be further evaluated
(init.rc).
Then no decryption will be done by smbmount.
If the password is provided by the DHCP server (<=> there's no pasword
provided by the floppy disk), the code assumes that the password is
encrypted. In this case the call of smbmount will be

smbmount //cael-dp01/ai386 /tmp -ousername=aniuser/cael-dp

smbmount then will read the encrypted password and from /etc/instpwd
and decrypt it by itself (see adaptions in smbmount.c; search for 'ANI').
_
Hagen
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (MingW32)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
 
iD8DBQFDKSBtJ31vBDLS4wQRAo7YAJ9lbgURcySvLq7jMUhKI/nHzX39/gCg+l2A
NO7r5N5qDfWnU0L7dBP8gF4=
=Xu0Q
-----END PGP SIGNATURE-----