Cannot Fix W2K Event Viewer System Log Errors

Rob8UrCakes · Joined: 28 Sep 2007 Posts: 1

For some months I've been unable to fix a bunch of Errors and Warnings
appearing in the recently discovered System Log, and although I've did some
reading on them I'm too stupid to fix them on my own without help, and may
well have inadvertently made matters worse in my futile attempts at a fix.

I use Windows 2000 Professional on an old Compaq Deskpro, Intel Pentium III
with a British Telecom "HomeHub" router.

My main problem is keeping an Internet connection for more than 12 or so
hours.

The most common Event Viewer entries in the System Log are:

2504 & 2505 Server
1003 &1007 Dhcp
20169 RemoteAccess
8033 Browser
11050 dnscache
7024 Service Control Manager
61 WinMgmt
20082 RemoteAccess (7 or 8 times)
20192 RemoteAccess

the last two always appear on bootup, with the others cropping up afterwards.

I'm pretty sure my set-up is somehow screwed but don't know how to fix it
without causing more problems.

If you're able to help, or need answers from me, please Post at your leisure.
Thanks.

Archived from group: microsoft>public>exchange2000>misc

Non delivery errors I have installed a Windows 2000 server with IIS and an SMTP server to relay incoming email to our main email server. Since it's installation I recieve non-delivery messages from the Postmaster indicating a message failed to be delivered. The Sender also

System Attendant service took 10 minutes to start Every time I restart my exchange2000 SP3 server (running over Windows 2000 Server STD SP4), de System attendant services, appears as starting for about 10 minutes, and therefore the Information Store and the MTA also dont start. Is there any obvious reas

9548 messages in event viewer i have read all the posts about adding SELF to the account, etc. My problem is that the account the event log refers to is the SystemMailbox and there is no user disabled or otherwise in the AD. I can plainly see the mailbox in exchange manager but cannot

Event Viewer Messages Completely Absent We had a LAN broadcast storm event the other night which at first gave the impression of being an Active Directory/DNS issue. We literally could not logon to the Exchange server and had to hard reset the device. Once the LAN event was diagnosed and fixed,

System attendant fails to start, 2 errors appear but cant re After trying various trouble shooting on Friday we left the box to rpelicate over the weekend and see if that helped, it hasnt and still MSexchnageSA wont start. We have had to take all exhange boxs at our remote site and our main site on and off the doma