I can't say that I have ever tried setting the root and admin passwords
to be the same. Mine are different. However, I would have expected that
the two would be completely separate, and that it would not matter if
they were the same.

Ben.

On Tue, 2005-03-29 at 07:43, Edwin Humphries wrote:
> Ben,
> 
> My apologies: I did see the front page, and the auth window came up when I 
> tried to do something.
> 
> I have just (again) reset the password through the setup utility, this time I 
> set it to something that wasn't also the root password. It works. Maybe 
> that's 
> a "feature" if IPCOP.
> 
> On 28 Mar 2005 at 22:01, Ben Stanley wrote:
> 
> > Hi,
> > 
> > I have been using IPCop for years. I must admit I've never had the
> > problem that you describe, but I'll try to help you work through it.
> > 
> > I just checked my /etc/passwd and /etc/shadow files, and root is the
> > only account with a username. However, I also have an admin account and
> > password. This is administered through the setup program, and the
> > details are stored in /var/ipcop/auth/users . These users are apache
> > users rather than unix users.
> > 
> > When you connect to ipcop, using http://ipcop:81/ , it should just show
> > you the front page. There should be no need to authenticate, unless you
> > try to 'connect' or use some other function through the menus. In that
> > case, you should login with the username 'admin' or 'dial', with the
> > appropriate password. I don't believe the root password will help you
> > here.
> > 
> > Try again and please tell us exactly when it asks for authentication.
> > Your message seems to indicate 'immediately, without showing the home
> > page'.
> > 
> > What version of IPCop did you install?
> > 
> > You might also consider bugging the IPCop mailing lists...
> > 
> > Ben.
> > 
> > 
> > On Mon, 2005-03-28 at 09:03, Edwin Humphries wrote:
> > > G'day all,
> > > 
> > > We're just setting up an IPCOP box to handle all our firewalling and
> > > routing, but I have a problem. I've RTFM'd and no help there.
> > > 
> > > After installation, I checked out the web interface with no problems. 
> > > Then interruptions for over a week before I came back to it; now I 
> > > can't access it. Pulled up the interface on a browser (Firefox) and 
> > > when I try to do anything up comes a auth window, asking for the name and 
> > > password for "Restricted". Entering "root" and the root password doesn't 
> > > work, 
> > > although the shadow password file shows root is the only user. I tried 
> > > creating 
> > > user "admin" and set it's password - still no good. Tried setting the 
> > > "admin" 
> > > password using the setup utility - no good. Tred entering "Restricted" as 
> > > the 
> > > username - no good.
> > > 
> > > Can anyone help?
> > > 
> > > Regards,
> > > Edwin Humphries
> > > Mobile: 0419 233 051
> > > Ironstone Technology Pty Ltd
> > > P. O. Box 423, Kiama, NSW, 2533
> > > Phone: +61 (0)2 4233 2285
> > > Facsimile: +61 (0)2 4233 2299
> > > Web: http//www.ironstone.com.au
> > > 
> > > ***********************************************************
> > > This email is intended for the named addressee/s only and 
> > > may contain confidential or privileged information. If you 
> > > are not a named addressee please delete the message and 
> > > notify the sender.
> > > ***********************************************************
> 
> Regards,
> Edwin Humphries
> Mobile: 0419 233 051
> Ironstone Technology Pty Ltd
> P. O. Box 423, Kiama, NSW, 2533
> Phone: +61 (0)2 4233 2285
> Facsimile: +61 (0)2 4233 2299
> Web: http//www.ironstone.com.au
> 
> ***********************************************************
> This email is intended for the named addressee/s only and 
> may contain confidential or privileged information. If you 
> are not a named addressee please delete the message and 
> notify the sender.
> ***********************************************************
> 
> 

-- 
SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/
Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html

Reply via email to