Re: Help with a member server loosing the ability to validate users

The user name and passoword aren't entered in the service logon, which is set to the local system account, but within the application. The error reported in the event log in an 1816 error.

"Jorge Silva" <jorgesilva_pt@xxxxxxxxxxx> wrote in message news:ubirYDgmGHA.5076@xxxxxxxxxxxxxxxxxxxxxxx
What services are failing?

--
I hope that the information above helps you

Good Luck
Jorge Silva
MCSA
Systems Administrator

"Gordon Philip" <nospam@xxxxxxxxxxxxxxxxx> wrote in message news:OO3$1$fmGHA.3600@xxxxxxxxxxxxxxxxxxxxxxx
The users were set up about 12 months ago with no password expiration and the passwords have never changed since they were created, furthermore if the server is rebooted then the they start up and continue to work for a few days with no problems. In fact I only see the error as the database package is closed down each night to allow the backup and then the restart fails.

"Jorge Silva" <jorgesilva_pt@xxxxxxxxxxx> wrote in message news:%23nkwC9fmGHA.2056@xxxxxxxxxxxxxxxxxxxxxxx
Hi

After running for a few days these packages refused to start up using the username credentials that had worked previously.

Did you change the password of these users' accounts? Does the account have password expiration limit?



In an attempt to resolve this I have transferred all 5 FMSO roles to a new server along with the DNS server role. However I am still experiencing the same problem

In all cases rebooting the machine, which is now a member server, resolves the issue



event log errors?


--
I hope that the information above helps you

Good Luck
Jorge Silva
MCSA
Systems Administrator

"Gordon Philip" <nospam@xxxxxxxxxxxxxxxxx> wrote in message news:u69S15fmGHA.4536@xxxxxxxxxxxxxxxxxxxxxxx
I have a machine that used to hold all 5 FMSO roles and was both a DNS server and DHCP server, along with an email package and database package. The latter 2 ran as a service with dedicated username specifically set up to run the service.

After running for a few days these packages refused to start up using the username credentials that had worked previously.

In an attempt to resolve this I have transferred all 5 FMSO roles to a new server along with the DNS server role. However I am still experiencing the same problem

In all cases rebooting the machine, which is now a member server, resolves the issue

Does anyone have any ideas were I should look next?






.

Relevant Pages

  • Re: Protecting database from administrators
    ... If you remove the Builtin\Administrators account all you ... This resolves any of the below issues. ... server resides. ... removing "System Admin" role ...
    (microsoft.public.sqlserver.security)
  • Re: Re-Post - "the trust relationship between this workstation and the
    ... "the trust relationship between this workstation and the primary domain ... only problem is adding a new user account on the station. ... Client computer must use STRICTLY the INTERNAL DNS server which can ... Attr: subschemaSubentry ...
    (microsoft.public.windows.server.active_directory)
  • Re: Same question, still no answer!!!
    ... Sounds then like we are all paying for a feature set only large companies ... The "proxy server" pc is actually an older box stuffed ... Expectation #1) keep the ethernet more or less as is. ... The kids account would be ...
    (microsoft.public.windowsxp.basics)
  • Re: Re-Post - "the trust relationship between this workstation and the
    ... "the trust relationship between this workstation and the primary domain ... only problem is adding a new user account on the station. ... This would be on the DNS server 172.20.100.2 ... Attr: subschemaSubentry ...
    (microsoft.public.windows.server.active_directory)
  • Sending email to mydomain.com
    ... server will appear as undeliverable. ... This happens because you are using the POP3 connector... ... an NDR when an account doesn't exist). ... >different from the user account names for the exchange ...
    (microsoft.public.windows.server.sbs)