BIND on Windows Vista

[Matt Reeve]

My experience is slightly different - I've found that I can start named 
from my account which has administrator rights, using:

runas /user:named "named -g"

and this starts fine (after I supply named's password at the prompt). I 
can also simply run "named -g" at a run-as-adminstrator command prompt 
and that starts fine too.

I'm using Vista 32-bit.

Matt.

Fabien wrote:
> Hello,
>
> I'm facing the same trouble, I think it's related to the UAC feature on 
> Vista, but not sure.
> I'm running Vista 32 bits.
>
> Actually, I did manage to start BIND only under my personal account
> (I had to add myself in the "log on as a service" privilege and change the 
> service properties).
>
> If you execute "named -g" in a "run as administrator" CLI, it's OK
> If you execute "named -g" under your session, it's OK
> If you execute "named -g" under named account (runas), it first crashes, 
> then output this :
> 15-aout-2007 19:53:32.144 starting BIND 9.4.1-P1 -g
> 15-aout-2007 19:53:32.149 found 2 CPUs, using 2 worker threads
> and generates the c0000005 error, but I don't know what named is violating 
> (memory access ? thread ? registry ?).
>
> Really curious,
> I've tried to tag named.exe to run under administrator rights, no change.
> I've tried to add the named account into Administrators group, no change.
> I've also added full permissions for named account on the BIND folders, I 
> thought named had to write something within, but no change.
>
> any idea why the named account can't manage to start the service ? even with 
> some administrative rights ?
>
> Cheers
> Fabien
>
>   
>> Matt Reeve wrote:
>>     
>>> Hi,
>>>
>>> are there any plans to support ISC BIND on Windows Vista? (or better
>>> still has anybody made it work?)
>>>       
>> It should work.
>>
>>     
>>> I've tried 9.4.1-P1 and it installs OK, but the service fails to start,
>>> the error in the event viewer is:
>>>
>>> Faulting application named.exe, version 0.0.0.0, time stamp 0x4691b2a7,
>>> faulting module unknown, version 0.0.0.0, time stamp 0x00000000,
>>> exception code 0xc0000005, fault offset 0x00000000, process id 0xe14,
>>> application start time 0x01c7dce2a1025bcd
>>>
>>>       
>> Are you running 32-bit Windows or 64-bit Windows?
>>
>> Run named from the DOS prompt. CD to the directory where it's installed
>> and then run it as follows:
>>
>> named -g
>>
>> That should put all output to the DOS Window. See how far it gets and
>> post the output from the DOS Window.
>>
>> Danny
>>
>>
>>
>>     
>
>
>