From: | "Thomas H(dot)" <me(at)alternize(dot)com> |
---|---|
To: | "George Weaver" <gweaver(at)shaw(dot)ca> |
Cc: | "pgsql-general" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: PostgreSQL doesn't accept connections when Windows |
Date: | 2006-12-01 15:10:39 |
Message-ID: | 099c01c7155a$dcfda9c0$0201a8c0@iwing |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
> If I understand what you're suggesting, perhaps upon reboot PostgreSQL is
> starting before another app that listens on the same port, which could
> cause the problem, but if I then restart the PostgreSQL service this
> solves the problem?
if you can start it manually, then its probably not a problem with another
tool using the same port.
a) do you have a software firewall installed on that machine that might be
interfering here?
b) is your windows in a domain?
if so, make sure you manually set "log on as a service" priviledges on the
domain controller for the local postgres user. the installed only sets local
priviledges that are overwritten upon reboot.
you find the setting here: start -> run -> mmc -> file -> add snapin ->
add -> group policy editor -> browse -> default domain policy
then browse for computer configuration -> windows settings -> security
settings -> local policies -> user rights -> log on as a service. add the
user there.
regards,
- thomas
From | Date | Subject | |
---|---|---|---|
Next Message | Richard Huxton | 2006-12-01 15:24:26 | Re: Problem with function parameters |
Previous Message | Richard Huxton | 2006-12-01 15:02:54 | Re: initdb problem on Windows XP Home |