I'll give you the whole story of what happened.
A couple of days ago I suddenly realised that the sambar server wasn't sending and
mail. I looked at the logs and found out that I was getting these errors:
ERROR: cm_dns_gethostaddr() failed for 'yahoo.com'
ERROR: ROUTER: Connect to remote SMTP Server 'yahoo.com' failed.
I discovered that the MTA tests weren't working either. The server had been working
perfectly before and suddenly was giving problems.
I checked all the DNS settings and they were all set correctly according to the
documentation i.e. the DNS addresses were set in the config.ini file and they were the
same as the NT box was configured to.
I then checked to see if the DNS servers were down but they seemed to be fine. I did
nslookup checks from the NT box on whcih the sambar server is installed.
I decided to reboot the machine. My machine did not restart as the drive crashed. I
got a new drive reinstalled NT server and Sambar server. I reconfigured Sambar server
using the same settings as before. Everything started woking fine so I thought it
might have been the drive causing some sort of problem. The sambar server ran for
about a day and a half and then it gave the same problems again. It couldn't access
any DNS records and all mail sent through the SMTP server was failing. Nothing had
changed on the server. I can still use nslookup from the Sambar machine to get DNS
records. But Sambar won't work. I've tried rebooting the computer and restarting the
server. I've reinstalled the NT TCP/IP services... I can only think of one thing that
might have cause some sort of problem and that is Norton Antivirus which is the only
other thing that runs on the machine.
At the moment I have had to configure the Sambar server to send mail using my ISP SMTP
server. Has any one got any ideas about this problem?
On 19/Sep/2002 22:31:09, James Wright wrote:
> It seems to work largely in 'cooperation' with Windows; so
> usually if NT is off it will affect Sambars performance. I've
> had what you're seeing happen a couple times; once it was just a
> silly mistake and the other was what I thought was an
> insignificant OS setting - so that took forever to find :-) A
> common thing is any changes to TCP/IP filtering... I've seen
> that one mess things up more than once.
>
> I'm sure you've already thought of this, but go over any changes
> to Sambar or the OS in the past few days and also do a full
> reboot of everything (modem, routers, etc.). Ya never know;
> could just be a network glitch.
>
>
>
> ----- Original Message -----
> From: "Ross Rozendaal" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Thursday, 19 September, 2002 07:03
> Subject: [sambar] DNS MX records problems {05}
>
>
> > No ports have been blocked. Could it be an NT problem? Does
> the Sambar server have its own DNS lookup engine or does it use
> something on the NT machine?
> >
> -------------------------------------------------------
> To unsubscribe please go to <A TARGET="_blank"
>HREF="http://www.sambar.ch/list/";>http://www.sambar.ch/list/</A>
>
>
>
-------------------------------------------------------
To unsubscribe please go to http://www.sambar.ch/list/
