[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[cobalt-users] front page problem with RaQ2
- Subject: [cobalt-users] front page problem with RaQ2
- From: "Tom Kolbe" <kolbe@xxxxxxxxxxx>
- Date: Mon Feb 21 09:42:40 2000
Gentlemen,
I've been reading this message board for over a month now and have found it
quite informative. I'm very glad this list is available. Unfortunately I
have a problem that I am hoping someone can help me with. Recently I had a
customer call to say that the frontpage 98 extensions on his dedicated RaQ2
were not authenticating him and that he could not connect to publish his
site on any of his virtual domains or the main site. He stated to me that he
had not changed any passwords and that he uses the same passwd for all
virutal domain accts, admin acct, and FP accts. I proceeded to uncheck all
list options for front page extensions (both in the user account area and
all domains). After doing this, I re-added them to see if it would fix the
problem (he had first stated that they weren't working until further
analysis). After this failed to fix the problem, I proceeded to telnet into
the system to see what was going on. I found nothing out of the ordinary
(out of the ordinary for a cobalt that is). So, I tried creating a new acct
on the main site, gave it site admin privs and front page extensions. The
password would not authenticate either when I tried connecting to the site
(either <root> or ~user) from InterDev. I then telnetted in again to try
some playing around. As root, I compared the encrypted service.pwd password
file for admin in /home/sites/home/web/users/admin/_vti_pvt to the shadow
password file admin account and found them to look totally different even
though the fp accts pwd should be the same as the shadow pwd. After backing
up the file I proceeded to do a copy/paste from the shadow passwd file for
the admin acct to the service.pwd file and try connecting again. Didn't
work, so I reverted to the old file. What's going on here? Will reinstalling
the FP extensions fix this? rtr.com says to fully reinstall the extensions,
but I feel this is not going to fix the problem.
Thank you for your help,
Tom Kolbe (kolbe@xxxxxxxxxxx)