Could this be maybe from MailEnable?
Or something to do with the monitoring?

Event Type: Error
Event Source: pNSClient.exe
Event Category: None
Event ID: 0
Date: 10/21/2003
Time: 11:09:29 PM
User: N/A
Computer: MYSERVER01
Description:
The description for Event ID ( 0 ) in Source ( pNSClient.exe ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: Asynchronous socket error 10053.

pNSClient.exe does not seems to be related to MailEnable but rather NetSaint remote monitoring client.

pNSClient.exe is installed by Server Matrix. It's a monitoring tool. Maybe they can fill you in.

I signed up for the silver monitoring plan and filled
out the form in the orbit servermatrix backoffice
administration, and quite frankly, I'll embarrass
myself by stating that I don't have a clue how this
monitoring system works.
I signed up for some services, dns, http,
stuff I thought I should know if there's a problem
about, but, how am I notified? email?
per day? per week? only on a trouble?

I'm a newbie.

Don't feel bad I looked at the monitoring page and left. I posted some questions back in September but never got a reply. I guess I should fill out a ticket asking the protocol/requirements for the silver plan.
http://forums.servermatrix.com/viewtopic.h...tml?p=2634#2634

From my experience, they only informed you if your services are down. If you laid down some escalation procedures then they would comply to that and proceed using the steps you lay out. If you ask them to contact you when the services are down, they probably would do so. You can define how you want to be contacted.

For me, I told them to fix whatever problems which comes their way and if it is unfixable or take too long to do so, to contact me and let me decide at that point. If a quick reboot would solve it then I can be left in the dark.

They will only contact you when there is a problem and not when there isn't. This will reduce their load in sending out unimportant emails and concentrate on the work at hand.

I see. Well then, I guess there's something wrong with this
monitoring software they installed on my server. Is that NetSaint?
I posted a ticket and I'm waiting for technical service to come back
to me..

Nagios used to be called NetSaint. Posting a ticket is the right way to go.

This is the reply I got for my ticket:

------------------------------------------
(kirvin-10/23/03-11:29):
This is the Agent service we install for monitoring. This error probably indicates that the agent could not connecto to the service being monitored.
--------------------------------------

Honestly, I cannot understand how it can be..

wtf? I would think if a monitoring service was added it would be tested and configured to work. If it's not working I would think someone would offer to look at it. If they just do a "template" install and it attempts to monitor services that are not even installed then that's whacked.
I'm used to colocating my own servers so I wouldn't want anyone installing or configuring anything on my servers that I'm not familiar with anyway.
Wondering why the ticket doesn't say anything like, "this is bad we will look into it" or " that is normal don't worry" ?

I'm sure it's a configuration thing. Reply back on that ticket and ask them why its not working. Right now I couldn't speculate (I'm not too familiar with the monitoring daemon... yet ).

------------------------------------------
(kirvin-10/28/03-12:28):
This error generally occurs because our monitoring service needs the ability to bind to port 1248 to listen. It appears that another service may be occupying this port causing the failure. If there are any third-party applications running on this port, they will need to be moved to allow the monitoring service to function.

--------------------------------------------------
The only thing I've installed on my server is MailEnable
for the time being. I had some problems with it, but
it was common for every other user of win2003 on the
ME forums and was fixed by a fix ME provided.
What could possibly be on port 1248?

They claim some application installed on my computer is occupying
port 1248, but in fact, I've installed only MailEnable.
I've installed Active Ports today to validate this claim, and realized
that there's no application on port 1248!!!

Here's a proof:


I'm clueless.