Subject | Re: [firebird-support] Re: Windows security problems. |
---|---|
Author | Helen Borrie |
Post date | 2004-10-29T02:43:20Z |
At 12:38 AM 29/10/2004 +0000, you wrote:
privileges to the IPServer ("Windows local connect"). Since you've been
uniinstalling and reinstalling pieces, also don't overlook the possibiity
that you are now (or might have before) have installed the Classic
server. You can't use the IPServer connection protocol with Classic, period.
your installation. That way, when you raise further support questions, you
reduce the amount of E.S.P. required of people to answer your questions.
This is not directed as a personal flame at you and please don't take it as
such. However, when people set off to do unconventional things with their
installations (much to be encouraged, within the boundaries of common
sense) they change the parameters. The better the information you give us,
the better the solutions we can give you.
tutorial from the FAQ page. http://firebird.sourceforge.net?op=faq
./heLen
>On a lark I tried to connect to the databases on my computer withAt a guess, I'd say that the firebird user you created doesn't have
>flamerobin and the darn thing worked! I looked at some items in the NT
>event logs and chased down a few web sites and just as a guess I tried:
>
>"C:\Program Files\Firebird\Firebird_1_5\bin\isql.exe" -m
>"localhost:c:\dbs\asv.fdb" -u "sysdba" -pas "masterkey"
>
>So adding the reference to local host worked.
>
>I immediately went to that big black and yellow book on FB (Helen, you
>should e proud) and looked up the syntax for gsec and added the
>references to the local host and the path to the security db:
>
>
>C:\Documents and Settings\David>"C:\Program
>Files\Firebird\Firebird_1_5\bin\gsec
>.exe" -database "localhost:C:\Program
>Files\Firebird\Firebird_1_5\security.fdb"
>-user sysdba -password masterkey
>
>That worked great!
>
>So my question is why did the need to add the reference to localhost
>suddenly appear after changing the account that the services run under?
privileges to the IPServer ("Windows local connect"). Since you've been
uniinstalling and reinstalling pieces, also don't overlook the possibiity
that you are now (or might have before) have installed the Classic
server. You can't use the IPServer connection protocol with Classic, period.
>What can I do get around this?As a first step, write down, learn and inwardly digest all the variables of
your installation. That way, when you raise further support questions, you
reduce the amount of E.S.P. required of people to answer your questions.
This is not directed as a personal flame at you and please don't take it as
such. However, when people set off to do unconventional things with their
installations (much to be encouraged, within the boundaries of common
sense) they change the parameters. The better the information you give us,
the better the solutions we can give you.
>Thanks for the link to the tutorial, Simon! That worked exactly theAnd I'm pleased to say that Simon agreed to let us link through to the
>same under XP Pro as it dies under 2003, and it was exactly what I
>needed.
tutorial from the FAQ page. http://firebird.sourceforge.net?op=faq
./heLen