4 replies
by grbeckmeyer
My first thought is that you should check the server while the problem is happening. From the server, load ping and try pinging some public IP's by both number and name. For example, try to ping 192.233.80.9 (Novell) If that works, stop that ping and try pinging "novell.com". If you can ping the number but not the name, that definitely falls in with this info I found on Novell's knowledgebase...
The gateway had been functioning correctly for some time - 3 days ago, the errors started occurring. Through some troubleshooting we found that the daemon was sending out the messages but they were being sent back straight away with the response errors.
As it seemed that the error was not being caused by the gateway, the customer contact their ISP and then discovered that the ISP had changed the name and location of the specified DNS host for this customer. We edited the Resolv.Cfg file to reflect the changes to the DNS & restarted the gateway and daemon. The customer could now send internet mail without error.
This discussion is closed to new replies.
Trending Networks posts
Sort by Trending