Guest schulz80134 Posted May 5, 2005 Report Share Posted May 5, 2005 Help!!! I'm in the midst of trying to set up MNF on a Mandriva box and am running into a show-stopper when trying to simply log into the "Mandrake Security" webpage. (i.e. https://192.168.1.1:8443 in my case) I can bring up the https://192.168.1.1:8443 page ok, but when trying to log in as the "admin" user I consistently get a "wrong login/password" response every single time. Here's my current setup: - The machine I'm running MNF on is running Mandriva 2005 LE - The MNF machine has two ethernet cards. One obtains its IP dynamically (that's connected to the net), and the other has an IP manually specified as 192.168.1.1 (that's connected to a hub) - I have a hub between the (manually specified) ethernet card on the MNF box and the client box. - The client machine (that I'm trying to access the configururation page from) is running Windows XP Home. - The client machine has it's IP info manually configured (IP=192.168.1.10, Netmask=255.255.255.0, Gateway=192.168.1.1, (no dns servers specified)) - I've set the times/dates on both the MNF box and the Windows box to be within about 10 seconds of each other. Furthermore, I've insured that both boxes have the time set (and reported) in GMT. (So there definitely shouldn't be any issues with time discrepancies, even any due to timezones or daylight savings.) - I'm using Mozilla Firefox to access http://192.168.1.1:8443/index.php Here's a quick list of some of the things that I've tried: - I've tried accessing the http://192.168.1.1:8443 page both as http://192.168.1.1:8443, http://192.168.1.1:8443/index.php - I've tried accessing http://192.168.1.1:8443 using IE6 - I've tried changing the admin password via the 'passwd' command as root. (i.e. 'passwd admin') - I've verified that I'm using the correct admin password as I can log into the console as admin (and that correctly launches the 'Network Appliance Administration Tool Control Console' (i.e. /usr/bin/naat-console)) - I've restarted httpd2-naat (via "/etc/init.d/httpd2-naat restart"). - I've stopped shorewall (via "shorewall clear") - I've aligned the date/times on the two machines (as mentioned above) to be within ~10 seconds of each other, and have forced both machines to use strict GMT in order to be sure that I'm avoiding any timezone or daylight savings issues between the two boxes. After hours and hours of trying everything I can think of, I'm really at a loss here. Help!!!!!!!! Any help would really be appreciated!!!! Thanks in advance! Quote Link to comment Share on other sites More sharing options...
aioshin Posted May 5, 2005 Report Share Posted May 5, 2005 (edited) maybe you should try to change the admin passwd at console #passwd admin if you have'nt done that yet Edited May 5, 2005 by aioshin Quote Link to comment Share on other sites More sharing options...
Guest farmer_jim Posted May 9, 2005 Report Share Posted May 9, 2005 (edited) I'm having the exact same problem and have been searching for an anser for days now. I've found several similar issues none with a resolution. Did you ever get this working? Edited May 9, 2005 by farmer_jim Quote Link to comment Share on other sites More sharing options...
Guest schulz80134 Posted June 2, 2005 Report Share Posted June 2, 2005 I'm having the exact same problem and have been searching for an anser for days now. I've found several similar issues none with a resolution. Did you ever get this working? <{POST_SNAPBACK}> After a lot of digging, I found the problem... The pwauth program is used by the mnf software to do the login authentication. When pwauth is compiled, one of the elements which is specified is a designation of which users are authorized to use the program. For mandrake, this appears to be apache and root. In the case of mnf, it is the httpd2-naat user which is using pwauth, and so it fails. (The program has suid permissions, but for some reason it is still detecting the actual user (httpd2-naat) when running.) But, we're in luck. Apparently they goofed up when compiling the pwauth program and assumed that the apache user was a particular UID. As such, they have issued an updated verison of the pwauth rpm. This updated version removes the dependency on the user and allows the httpd2-naat user to access it successfully. Download the updated version (pwauth-2.2.8.1.1.102mdk.i586.rpm) and run 'rpm --freshen <rpmfile>' on it. Then, when installed, the pwauth program is located under /usr/sbin/pwauth. MNF is looking for it under /usr/lib/apache/pwauth. This can be solved by a link: mkdir /usr/lib/apache ln -s /usr/bin/pwauth /usr/lib/apache/pwauth Quote Link to comment Share on other sites More sharing options...
Guest amdfrkslpknt Posted June 30, 2005 Report Share Posted June 30, 2005 Download the updated version (pwauth-2.2.8.1.1.102mdk.i586.rpm) and run 'rpm --freshen <rpmfile>' on it. Then, when installed, the pwauth program is located under /usr/sbin/pwauth. MNF is looking for it under /usr/lib/apache/pwauth. This can be solved by a link: mkdir /usr/lib/apache ln -s /usr/bin/pwauth /usr/lib/apache/pwauth <{POST_SNAPBACK}> Did this and still no luck, I found in another forum that you had the change the ownership of pwauth to the group admin to get this to work. Did that too and still cannot get in. I'm on an install of Mandriva 10.2 with httpd2-naat and the latest updates any ideas? Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.