My Server is trying to log into itself

Ok, after looking deeper into the ODBC settings, it looks like its going through the hosting service using its credentials.

I changed the owner of my SQLAgent$SBSMonitoring service to the Administrator account.

Still getting the failure audits.

I PMed you a link on reinstalling the monitoring service....

MLF

I have a few questions.

1.) Is the SBS the only DC on the LAN?

2.) Are you auditing failure events only or sucess and failure events. If you're not auditing sucessful login attempts, turn that on. Then wait a few minutes, then take a look in the event log and see if you are also logging any Event ID 552 events.

If you get the 552 errors, post the PID of the process.

3.) Is it SBS Standard or Premium?

4.) Does the McAfee Product include McAfee ePO, and if so, what version? I had a similar issue running McAfee ePO on a SBS box once.

The only thing that vexes me is that it's saying Logon Type 3, and that's usually what you get from a failed logon using network credentials, i.e. a user logging on from across the network. :confused:

EDIT: Man I'm an idiot...I re-read the thread and see that you already answered Question 3...Duh.

I figured out what was causing my problems, it wasn’t the monitoring service (but I still think there is a problem with it so I am going to reinstall it). It was the Exchange Server, it isn’t fixed yet but the 4 failure audits I am getting are from, m$ Exchange Manager, m$ Exchange MTA Stacks, m$ Exchange Routing Engine, and m$ Exchange System Attendant.

Not sure what I am going to do with that knowledge yet, but that can wait until tomorrow (not utilizing this feature yet).

Quote:

---

Lots of services are dependant on other ones.

MLF

---

Thank you; this is what made me follow the dependencies to find exchange.

As for your questions 576869746568617, yes it’s the only DC, I was logging all events in the log, not just failure, and I don’t see anything about ePO in my McAfee, maybe it’s just because it’s a trial version.

Thanks a bunch for all the help

You know what you can try is to change the password back to what it was.....and see if that clears the errors??...then you know it is password related..remember to restart

Use the exact method you used to change it in the first place...you may be able to reverse the affects

also how did you change it in the first place...there is a wizard you are supposed to use in the server management console...which will change it for all sbs services....you then have to manually reset 3rd party apps that use the admin account

Exchange is a very fussy beast...... ;)

All my support calls to ms have been due to exchange issues...... :(

Any changes to the exchange setup recently..???

Can you manually start the services???

Disable your AV...see if your errors clear up......I have never had success with MacAfee on SBS...and AV needs to be tweaked on a SBS...because of all the apps and services it runs.

Trend has a SBS version....so does symantec

Post your errors...may be able to help.

Also that newsgroup I posted previously is a great help....

Good luck

MLF

Just skimmed all the responces but it looks like the computer account was removed. Every computer that's part of the domain has a computer account. These are in the form COMPUTERNAME$. What you should do on the server that's causing problems.. Remove it from the domain, put it in a workgroup. Reboot. Then add it to the domain again and reboot. That should solve it.

Sorry mr dice...but if you did that with a SBS....I think you would make it unrepairable...

The SBS has many services...and it wouldnt like that very much

there is no way to change a sbs name or domain.....

Do not do this unless you are willing to do a full reinstall


MLF

When ever I work with password related issues I just go into server management and make any changes in the users listing there.

As for the antivirus, the trial version expires tomorrow so I have uninstalled it. I have been looking into the trend antivirus for SBS and it's comforting to hear it being suggested, thank you.

Exchange has been a thorn in my side since we loaded SBS; I have been getting errors from the system attendant, information store, as well as a few others that I can’t recall at the moment. Because of this I haven't actually incorporated it through my company yet, the only people that use it is the other admin and myself so I am curious about your thoughts on just remove and reload it like you were suggesting with the monitoring (if that’s even possible).

I have tried to change the domain shortly after install and it did cause a lot of errors (never did work right again) and I had to resort to a reinstall so I am very hesitant to make any changes of that nature.

And I am willing to do a full reinstall if thats whats needed, but that is more of a last resort in my mind.

Well thats the problem...you broke exchange when you changed the domain name....you cannot rename a DC domain\machine with exchange on it

AFAIK...there is no fixing....


Now if you don not have any data in exchange...I would backup what data you have..and start from scratch.

I would make this site your home page...and read all the technical and setup documentation provided....twice ;)

http://www.microsoft.com/windowsserv...s/default.mspx


my last install of SBS 2003...took me 3 tries to ensure I had no errors or issues on the base install and setup

This from experience as I have been working with SBS since the first version 4.0. (1998)

There is no changing of core settings once installed...sure you can..but you will never recover in my experience...and problems will just compound themselves to the point of instability.

The SBS is a solid machine if correctly setup and maintained...with strong hardware to support it.

My job has been to fix SBS servers that have been installed by people that did not install it right in the first place.

or have fiddled with the install....and initial setup.

Trust me...I know this beast :cool:

Keeps me in fine wine :D

MLF