|
Related Topics:
| Event ID 4006 / 4007 - The SMTP verb which caused the erro.. - Hi, I'm problems with my w2k3 standard etd. IIS has been installed and several websites are running. There has been a virtual smtp server installed with relay access granted to a few ip adresses AND the Access has been given to..
SMTP Event 4000 - I have an SMTP virtual server installed on Windows 2000/IIS 5 server (patched except for updates). As of a few days ago, it sent mail to all A few days ago, it stopped sending mail to one call it..
SMTP Event sink - Hi I have win2k srv sp4 with iis & smtp services I have developed an c# com class using to intercept some e-mail messages. I have the com class using but when I try to send a new mail message using the..
Removing SMTP events from the event log? - Hi there.. Currently the system log is swamped in events about the SMTPSVC not being able to deliver a message to some domain that does not exists. It's not a system problem or like, so I would like to be able to exclude these events from..
How to disable event logging by SMTP service? - Hi: is there a way to disable the logging of event 4001 by SMTPSVC - delivery to the remote domain failed for the following reason: The was dropped by the remote Event log is clogged with those
|
|
|
Next: IIS: IIS 5.0 Inetinfo.exe 100% CPU Utilization Issue
|
| Author |
Message |
External
Since: Mar 03, 2005
Posts: 7
|
(Msg. 1) Posted: Thu Mar 03, 2005 6:03 am
Post subject: smtp event log error
Archived from groups: microsoft>public>inetserver>iis (more info?)
|
|
|
I have a program that I wrote which sends text messages to my cell phone.
The program uses IMessage from cdosys. It has been working fine for about a
year, but about a week ago, errors like the following started showing up in
the nt event log:
source: smtpsvc
event id: 4000
description: Message delivery to the remote domain 'vtext.com' failed for
the following reason: An internal DNS error caused a failure to find the
remote server.
The only thing I can think of that I did around that time was put my Windows
2000 box into a new workgroup while trying to set up peer-to-peer networking
between 2 machines at my house. I haven't changed any settings on my router.
I tried putting the computer back in the WORKGROUP workgroup, but that
didn't fix the problem.
I did run the smtpdiag utility, but I'm unsure of how to interpret the
output. The output is included below. Any ideas what might be going on?
Thanks,
Roy
Searching for Exchange external DNS settings.
Computer name is THEBOX.
Failed to connect to the domain controller. Error:
8007054b
Checking SOA for vtext.com.
Checking external DNS servers.
Checking internal DNS servers.
Checking TCP/UDP SOA serial number using DNS server
[192.168.2.1].
Failed: DNS server [192.168.2.1] may be down.
DNS server [192.168.2.1] did not return a valid SOA
record.
SOA serial number match: Failed with one or more
failures.
Checking local domain records.
Starting TCP and UDP DNS queries for the local domain.
This test will try to
validate that DNS is set up correctly for inbound
mail. This test can fail for
3 reasons.
1) Local domain is not set up in DNS. Inbound mail
cannot be routed to
local mailboxes.
2) Firewall blocks TCP/UDP DNS queries. This will
not affect inbound mail,
but will affect outbound mail.
3) Internal DNS is unaware of external DNS
settings. This is a valid
configuration for certain topologies.
Checking MX records using TCP: comcast.net.
Warning: The TCP DNS query returned no results.
Checking MX records using UDP: comcast.net.
MX: gateway-s.comcast.net (5)
MX: gateway-r.comcast.net (5)
A: gateway-s.comcast.net [IP address - looks valid]
A: gateway-s.comcast.net [IP address - looks valid]
A: gateway-r.comcast.net [IP address - looks valid]
A: gateway-r.comcast.net [IP address - looks valid]
A: dns01.jdc01.pa.comcast.net [IP address - looks valid]
A: dns02.jdc01.pa.comcast.net [IP address - looks valid]
Checking remote domain records.
Starting TCP and UDP DNS queries for the remote
domain. This test will try to
validate that DNS is set up correctly for outbound
mail. This test can fail for
3 reasons.
1) Firewall blocks TCP/UDP queries which will
block outbound mail. Windows
2000/NT Server requires TCP DNS queries. Windows
Server 2003 will use UDP
queries first, then fall back to TCP queries.
2) Internal DNS does not know how to query
external domains. You must
either use an external DNS server or configure DNS
server to query external
domains.
3) Remote domain does not exist. Failure is
expected.
Checking MX records using TCP: vtext.com.
Warning: The TCP DNS query returned no results.
Checking MX records using UDP: vtext.com.
MX: smtpsp.vtext.com (50)
MX: smtpsp1.vtext.com (50)
A: smtpsp.vtext.com [IP address - looks valid]
A: smtpsp1.vtext.com [IP address - looks valid] |
|
| Back to top |
|
 | |
External
Since: Feb 04, 2005
Posts: 59
|
(Msg. 2) Posted: Thu Mar 03, 2005 8:18 am
Post subject: Re: smtp event log error [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)
|
|
|
Log onto the box and do some DNS queries to make sure the box is getting
proper DNS.
Changing network stuff around could very well cause ripple-effect type
errors in DNS.
"Roy" <rdeal.RemoveThis@newsgroup.nospam> wrote in message
news:C3371806-8B84-4F43-8321-EAFD4875F417@microsoft.com...
>I have a program that I wrote which sends text messages to my cell phone.
> The program uses IMessage from cdosys. It has been working fine for about
> a
> year, but about a week ago, errors like the following started showing up
> in
> the nt event log:
>
> source: smtpsvc
> event id: 4000
> description: Message delivery to the remote domain 'vtext.com' failed for
> the following reason: An internal DNS error caused a failure to find the
> remote server.
>
> The only thing I can think of that I did around that time was put my
> Windows
> 2000 box into a new workgroup while trying to set up peer-to-peer
> networking
> between 2 machines at my house. I haven't changed any settings on my
> router.
> I tried putting the computer back in the WORKGROUP workgroup, but that
> didn't fix the problem.
>
> I did run the smtpdiag utility, but I'm unsure of how to interpret the
> output. The output is included below. Any ideas what might be going on?
>
> Thanks,
> Roy
>
> Searching for Exchange external DNS settings.
> Computer name is THEBOX.
> Failed to connect to the domain controller. Error:
> 8007054b
>
> Checking SOA for vtext.com.
> Checking external DNS servers.
> Checking internal DNS servers.
>
> Checking TCP/UDP SOA serial number using DNS server
> [192.168.2.1].
> Failed: DNS server [192.168.2.1] may be down.
> DNS server [192.168.2.1] did not return a valid SOA
> record.
> SOA serial number match: Failed with one or more
> failures.
>
> Checking local domain records.
> Starting TCP and UDP DNS queries for the local domain.
> This test will try to
> validate that DNS is set up correctly for inbound
> mail. This test can fail for
> 3 reasons.
> 1) Local domain is not set up in DNS. Inbound mail
> cannot be routed to
> local mailboxes.
> 2) Firewall blocks TCP/UDP DNS queries. This will
> not affect inbound mail,
> but will affect outbound mail.
> 3) Internal DNS is unaware of external DNS
> settings. This is a valid
> configuration for certain topologies.
> Checking MX records using TCP: comcast.net.
> Warning: The TCP DNS query returned no results.
> Checking MX records using UDP: comcast.net.
> MX: gateway-s.comcast.net (5)
> MX: gateway-r.comcast.net (5)
> A: gateway-s.comcast.net [IP address - looks valid]
> A: gateway-s.comcast.net [IP address - looks valid]
> A: gateway-r.comcast.net [IP address - looks valid]
> A: gateway-r.comcast.net [IP address - looks valid]
> A: dns01.jdc01.pa.comcast.net [IP address - looks valid]
> A: dns02.jdc01.pa.comcast.net [IP address - looks valid]
>
> Checking remote domain records.
> Starting TCP and UDP DNS queries for the remote
> domain. This test will try to
> validate that DNS is set up correctly for outbound
> mail. This test can fail for
> 3 reasons.
> 1) Firewall blocks TCP/UDP queries which will
> block outbound mail. Windows
> 2000/NT Server requires TCP DNS queries. Windows
> Server 2003 will use UDP
> queries first, then fall back to TCP queries.
> 2) Internal DNS does not know how to query
> external domains. You must
> either use an external DNS server or configure DNS
> server to query external
> domains.
> 3) Remote domain does not exist. Failure is
> expected.
> Checking MX records using TCP: vtext.com.
> Warning: The TCP DNS query returned no results.
> Checking MX records using UDP: vtext.com.
> MX: smtpsp.vtext.com (50)
> MX: smtpsp1.vtext.com (50)
> A: smtpsp.vtext.com [IP address - looks valid]
> A: smtpsp1.vtext.com [IP address - looks valid]<!-- ~MESSAGE_AFTER~ --> |
|
| Back to top |
|
| |
External
Since: Mar 03, 2005
Posts: 7
|
(Msg. 3) Posted: Thu Mar 03, 2005 8:18 am
Post subject: Re: smtp event log error [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)
|
|
|
I am not very networking savvy, so what you mean by do some DNS queries? I
did do a few things with nslookup - I that's along the lines of what you
recommended - that I read in a kbase article or two, but interpreting the
output is not my strong suit.
Thanks for the advice.
"Sparky Polastri" wrote:
> Log onto the box and do some DNS queries to make sure the box is getting
> proper DNS.
>
> Changing network stuff around could very well cause ripple-effect type
> errors in DNS.
>
> "Roy" <rdeal.TakeThisOut@newsgroup.nospam> wrote in message
> news:C3371806-8B84-4F43-8321-EAFD4875F417@microsoft.com...
> >I have a program that I wrote which sends text messages to my cell phone.
> > The program uses IMessage from cdosys. It has been working fine for about
> > a
> > year, but about a week ago, errors like the following started showing up
> > in
> > the nt event log:
> >
> > source: smtpsvc
> > event id: 4000
> > description: Message delivery to the remote domain 'vtext.com' failed for
> > the following reason: An internal DNS error caused a failure to find the
> > remote server.
> >
> > The only thing I can think of that I did around that time was put my
> > Windows
> > 2000 box into a new workgroup while trying to set up peer-to-peer
> > networking
> > between 2 machines at my house. I haven't changed any settings on my
> > router.
> > I tried putting the computer back in the WORKGROUP workgroup, but that
> > didn't fix the problem.
> >
> > I did run the smtpdiag utility, but I'm unsure of how to interpret the
> > output. The output is included below. Any ideas what might be going on?
> >
> > Thanks,
> > Roy
> >
> > Searching for Exchange external DNS settings.
> > Computer name is THEBOX.
> > Failed to connect to the domain controller. Error:
> > 8007054b
> >
> > Checking SOA for vtext.com.
> > Checking external DNS servers.
> > Checking internal DNS servers.
> >
> > Checking TCP/UDP SOA serial number using DNS server
> > [192.168.2.1].
> > Failed: DNS server [192.168.2.1] may be down.
> > DNS server [192.168.2.1] did not return a valid SOA
> > record.
> > SOA serial number match: Failed with one or more
> > failures.
> >
> > Checking local domain records.
> > Starting TCP and UDP DNS queries for the local domain.
> > This test will try to
> > validate that DNS is set up correctly for inbound
> > mail. This test can fail for
> > 3 reasons.
> > 1) Local domain is not set up in DNS. Inbound mail
> > cannot be routed to
> > local mailboxes.
> > 2) Firewall blocks TCP/UDP DNS queries. This will
> > not affect inbound mail,
> > but will affect outbound mail.
> > 3) Internal DNS is unaware of external DNS
> > settings. This is a valid
> > configuration for certain topologies.
> > Checking MX records using TCP: comcast.net.
> > Warning: The TCP DNS query returned no results.
> > Checking MX records using UDP: comcast.net.
> > MX: gateway-s.comcast.net (5)
> > MX: gateway-r.comcast.net (5)
> > A: gateway-s.comcast.net [IP address - looks valid]
> > A: gateway-s.comcast.net [IP address - looks valid]
> > A: gateway-r.comcast.net [IP address - looks valid]
> > A: gateway-r.comcast.net [IP address - looks valid]
> > A: dns01.jdc01.pa.comcast.net [IP address - looks valid]
> > A: dns02.jdc01.pa.comcast.net [IP address - looks valid]
> >
> > Checking remote domain records.
> > Starting TCP and UDP DNS queries for the remote
> > domain. This test will try to
> > validate that DNS is set up correctly for outbound
> > mail. This test can fail for
> > 3 reasons.
> > 1) Firewall blocks TCP/UDP queries which will
> > block outbound mail. Windows
> > 2000/NT Server requires TCP DNS queries. Windows
> > Server 2003 will use UDP
> > queries first, then fall back to TCP queries.
> > 2) Internal DNS does not know how to query
> > external domains. You must
> > either use an external DNS server or configure DNS
> > server to query external
> > domains.
> > 3) Remote domain does not exist. Failure is
> > expected.
> > Checking MX records using TCP: vtext.com.
> > Warning: The TCP DNS query returned no results.
> > Checking MX records using UDP: vtext.com.
> > MX: smtpsp.vtext.com (50)
> > MX: smtpsp1.vtext.com (50)
> > A: smtpsp.vtext.com [IP address - looks valid]
> > A: smtpsp1.vtext.com [IP address - looks valid]
>
>
><!-- ~MESSAGE_AFTER~ --> >> Stay informed about: smtp event log error |
|
| Back to top |
|
| |
External
Since: Jun 10, 2004
Posts: 1807
|
(Msg. 4) Posted: Thu Mar 03, 2005 1:35 pm
Post subject: Re: smtp event log error [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)
|
|
|
On Thu, 3 Mar 2005 06:27:04 -0800, Roy <rdeal.TakeThisOut@newsgroup.nospam> wrote:
>I am not very networking savvy, so what you mean by do some DNS queries? I
>did do a few things with nslookup - I that's along the lines of what you
>recommended - that I read in a kbase article or two, but interpreting the
>output is not my strong suit.
Post the output in the DNS groups and you'll get a decent tutorial in
how to read them.
Jeff
>Thanks for the advice.
>
>"Sparky Polastri" wrote:
>
>> Log onto the box and do some DNS queries to make sure the box is getting
>> proper DNS.
>>
>> Changing network stuff around could very well cause ripple-effect type
>> errors in DNS.
>>
>> "Roy" <rdeal.TakeThisOut@newsgroup.nospam> wrote in message
>> news:C3371806-8B84-4F43-8321-EAFD4875F417@microsoft.com...
>> >I have a program that I wrote which sends text messages to my cell phone.
>> > The program uses IMessage from cdosys. It has been working fine for about
>> > a
>> > year, but about a week ago, errors like the following started showing up
>> > in
>> > the nt event log:
>> >
>> > source: smtpsvc
>> > event id: 4000
>> > description: Message delivery to the remote domain 'vtext.com' failed for
>> > the following reason: An internal DNS error caused a failure to find the
>> > remote server.
>> >
>> > The only thing I can think of that I did around that time was put my
>> > Windows
>> > 2000 box into a new workgroup while trying to set up peer-to-peer
>> > networking
>> > between 2 machines at my house. I haven't changed any settings on my
>> > router.
>> > I tried putting the computer back in the WORKGROUP workgroup, but that
>> > didn't fix the problem.
>> >
>> > I did run the smtpdiag utility, but I'm unsure of how to interpret the
>> > output. The output is included below. Any ideas what might be going on?
>> >
>> > Thanks,
>> > Roy
>> >
>> > Searching for Exchange external DNS settings.
>> > Computer name is THEBOX.
>> > Failed to connect to the domain controller. Error:
>> > 8007054b
>> >
>> > Checking SOA for vtext.com.
>> > Checking external DNS servers.
>> > Checking internal DNS servers.
>> >
>> > Checking TCP/UDP SOA serial number using DNS server
>> > [192.168.2.1].
>> > Failed: DNS server [192.168.2.1] may be down.
>> > DNS server [192.168.2.1] did not return a valid SOA
>> > record.
>> > SOA serial number match: Failed with one or more
>> > failures.
>> >
>> > Checking local domain records.
>> > Starting TCP and UDP DNS queries for the local domain.
>> > This test will try to
>> > validate that DNS is set up correctly for inbound
>> > mail. This test can fail for
>> > 3 reasons.
>> > 1) Local domain is not set up in DNS. Inbound mail
>> > cannot be routed to
>> > local mailboxes.
>> > 2) Firewall blocks TCP/UDP DNS queries. This will
>> > not affect inbound mail,
>> > but will affect outbound mail.
>> > 3) Internal DNS is unaware of external DNS
>> > settings. This is a valid
>> > configuration for certain topologies.
>> > Checking MX records using TCP: comcast.net.
>> > Warning: The TCP DNS query returned no results.
>> > Checking MX records using UDP: comcast.net.
>> > MX: gateway-s.comcast.net (5)
>> > MX: gateway-r.comcast.net (5)
>> > A: gateway-s.comcast.net [IP address - looks valid]
>> > A: gateway-s.comcast.net [IP address - looks valid]
>> > A: gateway-r.comcast.net [IP address - looks valid]
>> > A: gateway-r.comcast.net [IP address - looks valid]
>> > A: dns01.jdc01.pa.comcast.net [IP address - looks valid]
>> > A: dns02.jdc01.pa.comcast.net [IP address - looks valid]
>> >
>> > Checking remote domain records.
>> > Starting TCP and UDP DNS queries for the remote
>> > domain. This test will try to
>> > validate that DNS is set up correctly for outbound
>> > mail. This test can fail for
>> > 3 reasons.
>> > 1) Firewall blocks TCP/UDP queries which will
>> > block outbound mail. Windows
>> > 2000/NT Server requires TCP DNS queries. Windows
>> > Server 2003 will use UDP
>> > queries first, then fall back to TCP queries.
>> > 2) Internal DNS does not know how to query
>> > external domains. You must
>> > either use an external DNS server or configure DNS
>> > server to query external
>> > domains.
>> > 3) Remote domain does not exist. Failure is
>> > expected.
>> > Checking MX records using TCP: vtext.com.
>> > Warning: The TCP DNS query returned no results.
>> > Checking MX records using UDP: vtext.com.
>> > MX: smtpsp.vtext.com (50)
>> > MX: smtpsp1.vtext.com (50)
>> > A: smtpsp.vtext.com [IP address - looks valid]
>> > A: smtpsp1.vtext.com [IP address - looks valid]
>>
>>
>><!-- ~MESSAGE_AFTER~ --> >> Stay informed about: smtp event log error |
|
| Back to top |
|
| |
External
Since: Mar 03, 2005
Posts: 7
|
(Msg. 5) Posted: Thu Mar 03, 2005 1:35 pm
Post subject: Re: smtp event log error [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)
|
|
|
Thanks for the pointers, Jeff and Sparky. Since the event log error mentions
an internal DNS error, it seems like I should use nslookup to troubleshoot my
router's DNS server. Is that correct? If so, then what queries do I issue?
I see from <a style='text-decoration: underline;' href="http://support.microsoft.com/kb/200525" target="_blank">http://support.microsoft.com/kb/200525</a> examples for querying my
ISP's incoming/outgoing email hosts (mail.comcast.net/smtp.comcast.net), but
how do I query MY machine to make sure it's getting proper DNS?
"Jeff Cochran" wrote:
> On Thu, 3 Mar 2005 06:27:04 -0800, Roy <rdeal.RemoveThis@newsgroup.nospam> wrote:
>
> >I am not very networking savvy, so what you mean by do some DNS queries? I
> >did do a few things with nslookup - I that's along the lines of what you
> >recommended - that I read in a kbase article or two, but interpreting the
> >output is not my strong suit.
>
> Post the output in the DNS groups and you'll get a decent tutorial in
> how to read them.
>
> Jeff
>
> >Thanks for the advice.
> >
> >"Sparky Polastri" wrote:
> >
> >> Log onto the box and do some DNS queries to make sure the box is getting
> >> proper DNS.
> >>
> >> Changing network stuff around could very well cause ripple-effect type
> >> errors in DNS.
> >>
> >> "Roy" <rdeal.RemoveThis@newsgroup.nospam> wrote in message
> >> news:C3371806-8B84-4F43-8321-EAFD4875F417@microsoft.com...
> >> >I have a program that I wrote which sends text messages to my cell phone.
> >> > The program uses IMessage from cdosys. It has been working fine for about
> >> > a
> >> > year, but about a week ago, errors like the following started showing up
> >> > in
> >> > the nt event log:
> >> >
> >> > source: smtpsvc
> >> > event id: 4000
> >> > description: Message delivery to the remote domain 'vtext.com' failed for
> >> > the following reason: An internal DNS error caused a failure to find the
> >> > remote server.
> >> >
> >> > The only thing I can think of that I did around that time was put my
> >> > Windows
> >> > 2000 box into a new workgroup while trying to set up peer-to-peer
> >> > networking
> >> > between 2 machines at my house. I haven't changed any settings on my
> >> > router.
> >> > I tried putting the computer back in the WORKGROUP workgroup, but that
> >> > didn't fix the problem.
> >> >
> >> > I did run the smtpdiag utility, but I'm unsure of how to interpret the
> >> > output. The output is included below. Any ideas what might be going on?
> >> >
> >> > Thanks,
> >> > Roy
> >> >
> >> > Searching for Exchange external DNS settings.
> >> > Computer name is THEBOX.
> >> > Failed to connect to the domain controller. Error:
> >> > 8007054b
> >> >
> >> > Checking SOA for vtext.com.
> >> > Checking external DNS servers.
> >> > Checking internal DNS servers.
> >> >
> >> > Checking TCP/UDP SOA serial number using DNS server
> >> > [192.168.2.1].
> >> > Failed: DNS server [192.168.2.1] may be down.
> >> > DNS server [192.168.2.1] did not return a valid SOA
> >> > record.
> >> > SOA serial number match: Failed with one or more
> >> > failures.
> >> >
> >> > Checking local domain records.
> >> > Starting TCP and UDP DNS queries for the local domain.
> >> > This test will try to
> >> > validate that DNS is set up correctly for inbound
> >> > mail. This test can fail for
> >> > 3 reasons.
> >> > 1) Local domain is not set up in DNS. Inbound mail
> >> > cannot be routed to
> >> > local mailboxes.
> >> > 2) Firewall blocks TCP/UDP DNS queries. This will
> >> > not affect inbound mail,
> >> > but will affect outbound mail.
> >> > 3) Internal DNS is unaware of external DNS
> >> > settings. This is a valid
> >> > configuration for certain topologies.
> >> > Checking MX records using TCP: comcast.net.
> >> > Warning: The TCP DNS query returned no results.
> >> > Checking MX records using UDP: comcast.net.
> >> > MX: gateway-s.comcast.net (5)
> >> > MX: gateway-r.comcast.net (5)
> >> > A: gateway-s.comcast.net [IP address - looks valid]
> >> > A: gateway-s.comcast.net [IP address - looks valid]
> >> > A: gateway-r.comcast.net [IP address - looks valid]
> >> > A: gateway-r.comcast.net [IP address - looks valid]
> >> > A: dns01.jdc01.pa.comcast.net [IP address - looks valid]
> >> > A: dns02.jdc01.pa.comcast.net [IP address - looks valid]
> >> >
> >> > Checking remote domain records.
> >> > Starting TCP and UDP DNS queries for the remote
> >> > domain. This test will try to
> >> > validate that DNS is set up correctly for outbound
> >> > mail. This test can fail for
> >> > 3 reasons.
> >> > 1) Firewall blocks TCP/UDP queries which will
> >> > block outbound mail. Windows
> >> > 2000/NT Server requires TCP DNS queries. Windows
> >> > Server 2003 will use UDP
> >> > queries first, then fall back to TCP queries.
> >> > 2) Internal DNS does not know how to query
> >> > external domains. You must
> >> > either use an external DNS server or configure DNS
> >> > server to query external
> >> > domains.
> >> > 3) Remote domain does not exist. Failure is
> >> > expected.
> >> > Checking MX records using TCP: vtext.com.
> >> > Warning: The TCP DNS query returned no results.
> >> > Checking MX records using UDP: vtext.com.
> >> > MX: smtpsp.vtext.com (50)
> >> > MX: smtpsp1.vtext.com (50)
> >> > A: smtpsp.vtext.com [IP address - looks valid]
> >> > A: smtpsp1.vtext.com [IP address - looks valid]
> >>
> >>
> >>
>
><!-- ~MESSAGE_AFTER~ --> >> Stay informed about: smtp event log error |
|
| Back to top |
|
| |
External
Since: Feb 04, 2005
Posts: 59
|
(Msg. 6) Posted: Thu Mar 03, 2005 1:35 pm
Post subject: Re: smtp event log error [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)
|
|
|
Well the first step is to know what DNS should be for that domain. i.e. www
goes to what IP, MX goes to what hostname and then to what IP.
Then use ping to find out what the DNS resolution on that box is (by logging
onto it, using ping with the hostname) and compare that with what your
network actually is.
Chances are a) your DNS resolution system is not working (thus "Internal DNS
error") or b) DNS is cached locally and reporting the wrong IP for that mail
server or c) dns for that domain actually is messed up.
Logging onto the box can get you a) and b). c) can be done using any number
of tools on the web.
Also in general, DNS is forced to refresh if you reboot devices (including
the router). Whether or not you should do that depends on your use of the
machines. If you can't reboot, stop and restart the DNS client service on
the computer to make sure it is not "remembering" the wrong IP addresses.
"Roy" <rdeal.TakeThisOut@newsgroup.nospam> wrote in message
news:8509B4B4-0630-4164-98D3-1BD9692E30E5@microsoft.com...
> Thanks for the pointers, Jeff and Sparky. Since the event log error
> mentions
> an internal DNS error, it seems like I should use nslookup to troubleshoot
> my
> router's DNS server. Is that correct? If so, then what queries do I
> issue?
>
> I see from <a style='text-decoration: underline;' href="http://support.microsoft.com/kb/200525" target="_blank">http://support.microsoft.com/kb/200525</a> examples for querying my
> ISP's incoming/outgoing email hosts (mail.comcast.net/smtp.comcast.net),
> but
> how do I query MY machine to make sure it's getting proper DNS?
>
> "Jeff Cochran" wrote:
>
>> On Thu, 3 Mar 2005 06:27:04 -0800, Roy <rdeal.TakeThisOut@newsgroup.nospam> wrote:
>>
>> >I am not very networking savvy, so what you mean by do some DNS queries?
>> >I
>> >did do a few things with nslookup - I that's along the lines of what you
>> >recommended - that I read in a kbase article or two, but interpreting
>> >the
>> >output is not my strong suit.
>>
>> Post the output in the DNS groups and you'll get a decent tutorial in
>> how to read them.
>>
>> Jeff
>>
>> >Thanks for the advice.
>> >
>> >"Sparky Polastri" wrote:
>> >
>> >> Log onto the box and do some DNS queries to make sure the box is
>> >> getting
>> >> proper DNS.
>> >>
>> >> Changing network stuff around could very well cause ripple-effect type
>> >> errors in DNS.
>> >>
>> >> "Roy" <rdeal.TakeThisOut@newsgroup.nospam> wrote in message
>> >> news:C3371806-8B84-4F43-8321-EAFD4875F417@microsoft.com...
>> >> >I have a program that I wrote which sends text messages to my cell
>> >> >phone.
>> >> > The program uses IMessage from cdosys. It has been working fine for
>> >> > about
>> >> > a
>> >> > year, but about a week ago, errors like the following started
>> >> > showing up
>> >> > in
>> >> > the nt event log:
>> >> >
>> >> > source: smtpsvc
>> >> > event id: 4000
>> >> > description: Message delivery to the remote domain 'vtext.com'
>> >> > failed for
>> >> > the following reason: An internal DNS error caused a failure to find
>> >> > the
>> >> > remote server.
>> >> >
>> >> > The only thing I can think of that I did around that time was put my
>> >> > Windows
>> >> > 2000 box into a new workgroup while trying to set up peer-to-peer
>> >> > networking
>> >> > between 2 machines at my house. I haven't changed any settings on
>> >> > my
>> >> > router.
>> >> > I tried putting the computer back in the WORKGROUP workgroup, but
>> >> > that
>> >> > didn't fix the problem.
>> >> >
>> >> > I did run the smtpdiag utility, but I'm unsure of how to interpret
>> >> > the
>> >> > output. The output is included below. Any ideas what might be
>> >> > going on?
>> >> >
>> >> > Thanks,
>> >> > Roy
>> >> >
>> >> > Searching for Exchange external DNS settings.
>> >> > Computer name is THEBOX.
>> >> > Failed to connect to the domain controller. Error:
>> >> > 8007054b
>> >> >
>> >> > Checking SOA for vtext.com.
>> >> > Checking external DNS servers.
>> >> > Checking internal DNS servers.
>> >> >
>> >> > Checking TCP/UDP SOA serial number using DNS server
>> >> > [192.168.2.1].
>> >> > Failed: DNS server [192.168.2.1] may be down.
>> >> > DNS server [192.168.2.1] did not return a valid SOA
>> >> > record.
>> >> > SOA serial number match: Failed with one or more
>> >> > failures.
>> >> >
>> >> > Checking local domain records.
>> >> > Starting TCP and UDP DNS queries for the local domain.
>> >> > This test will try to
>> >> > validate that DNS is set up correctly for inbound
>> >> > mail. This test can fail for
>> >> > 3 reasons.
>> >> > 1) Local domain is not set up in DNS. Inbound mail
>> >> > cannot be routed to
>> >> > local mailboxes.
>> >> > 2) Firewall blocks TCP/UDP DNS queries. This will
>> >> > not affect inbound mail,
>> >> > but will affect outbound mail.
>> >> > 3) Internal DNS is unaware of external DNS
>> >> > settings. This is a valid
>> >> > configuration for certain topologies.
>> >> > Checking MX records using TCP: comcast.net.
>> >> > Warning: The TCP DNS query returned no results.
>> >> > Checking MX records using UDP: comcast.net.
>> >> > MX: gateway-s.comcast.net (5)
>> >> > MX: gateway-r.comcast.net (5)
>> >> > A: gateway-s.comcast.net [IP address - looks valid]
>> >> > A: gateway-s.comcast.net [IP address - looks valid]
>> >> > A: gateway-r.comcast.net [IP address - looks valid]
>> >> > A: gateway-r.comcast.net [IP address - looks valid]
>> >> > A: dns01.jdc01.pa.comcast.net [IP address - looks valid]
>> >> > A: dns02.jdc01.pa.comcast.net [IP address - looks valid]
>> >> >
>> >> > Checking remote domain records.
>> >> > Starting TCP and UDP DNS queries for the remote
>> >> > domain. This test will try to
>> >> > validate that DNS is set up correctly for outbound
>> >> > mail. This test can fail for
>> >> > 3 reasons.
>> >> > 1) Firewall blocks TCP/UDP queries which will
>> >> > block outbound mail. Windows
>> >> > 2000/NT Server requires TCP DNS queries. Windows
>> >> > Server 2003 will use UDP
>> >> > queries first, then fall back to TCP queries.
>> >> > 2) Internal DNS does not know how to query
>> >> > external domains. You must
>> >> > either use an external DNS server or configure DNS
>> >> > server to query external
>> >> > domains.
>> >> > 3) Remote domain does not exist. Failure is
>> >> > expected.
>> >> > Checking MX records using TCP: vtext.com.
>> >> > Warning: The TCP DNS query returned no results.
>> >> > Checking MX records using UDP: vtext.com.
>> >> > MX: smtpsp.vtext.com (50)
>> >> > MX: smtpsp1.vtext.com (50)
>> >> > A: smtpsp.vtext.com [IP address - looks valid]
>> >> > A: smtpsp1.vtext.com [IP address - looks valid]
>> >>
>> >>
>> >>
>>
>><!-- ~MESSAGE_AFTER~ --> >> Stay informed about: smtp event log error |
|
| Back to top |
|
| |
External
Since: Mar 03, 2005
Posts: 7
|
(Msg. 7) Posted: Thu Mar 03, 2005 1:35 pm
Post subject: Re: smtp event log error [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)
|
|
|
I'll have to confirm this, but I believe I can logon to the machine with the
event log errors and ping it by name, and the IP address returned by ping is
the same as it has always been 192.168.2.3. That is within the range that
has been set up in my router.
If I do an ipconfig /all, then the DNS IP is 192.168.2.1, which is correct.
I'll try your suggestions tonight.
You know, I remember one other thing I did to the network settings on the
2nd machine in my home network. I disabled the Computer Browser service on
it so it would not be the master browser. Could that have anything to do
with this?
"Sparky Polastri" wrote:
> Well the first step is to know what DNS should be for that domain. i.e. www
> goes to what IP, MX goes to what hostname and then to what IP.
>
> Then use ping to find out what the DNS resolution on that box is (by logging
> onto it, using ping with the hostname) and compare that with what your
> network actually is.
>
> Chances are a) your DNS resolution system is not working (thus "Internal DNS
> error") or b) DNS is cached locally and reporting the wrong IP for that mail
> server or c) dns for that domain actually is messed up.
>
> Logging onto the box can get you a) and b). c) can be done using any number
> of tools on the web.
>
> Also in general, DNS is forced to refresh if you reboot devices (including
> the router). Whether or not you should do that depends on your use of the
> machines. If you can't reboot, stop and restart the DNS client service on
> the computer to make sure it is not "remembering" the wrong IP addresses.
>
> "Roy" <rdeal RemoveThis @newsgroup.nospam> wrote in message
> news:8509B4B4-0630-4164-98D3-1BD9692E30E5@microsoft.com...
> > Thanks for the pointers, Jeff and Sparky. Since the event log error
> > mentions
> > an internal DNS error, it seems like I should use nslookup to troubleshoot
> > my
> > router's DNS server. Is that correct? If so, then what queries do I
> > issue?
> >
> > I see from <a style='text-decoration: underline;' href="http://support.microsoft.com/kb/200525" target="_blank">http://support.microsoft.com/kb/200525</a> examples for querying my
> > ISP's incoming/outgoing email hosts (mail.comcast.net/smtp.comcast.net),
> > but
> > how do I query MY machine to make sure it's getting proper DNS?
> >
> > "Jeff Cochran" wrote:
> >
> >> On Thu, 3 Mar 2005 06:27:04 -0800, Roy <rdeal RemoveThis @newsgroup.nospam> wrote:
> >>
> >> >I am not very networking savvy, so what you mean by do some DNS queries?
> >> >I
> >> >did do a few things with nslookup - I that's along the lines of what you
> >> >recommended - that I read in a kbase article or two, but interpreting
> >> >the
> >> >output is not my strong suit.
> >>
> >> Post the output in the DNS groups and you'll get a decent tutorial in
> >> how to read them.
> >>
> >> Jeff
> >>
> >> >Thanks for the advice.
> >> >
> >> >"Sparky Polastri" wrote:
> >> >
> >> >> Log onto the box and do some DNS queries to make sure the box is
> >> >> getting
> >> >> proper DNS.
> >> >>
> >> >> Changing network stuff around could very well cause ripple-effect type
> >> >> errors in DNS.
> >> >>
> >> >> "Roy" <rdeal RemoveThis @newsgroup.nospam> wrote in message
> >> >> news:C3371806-8B84-4F43-8321-EAFD4875F417@microsoft.com...
> >> >> >I have a program that I wrote which sends text messages to my cell
> >> >> >phone.
> >> >> > The program uses IMessage from cdosys. It has been working fine for
> >> >> > about
> >> >> > a
> >> >> > year, but about a week ago, errors like the following started
> >> >> > showing up
> >> >> > in
> >> >> > the nt event log:
> >> >> >
> >> >> > source: smtpsvc
> >> >> > event id: 4000
> >> >> > description: Message delivery to the remote domain 'vtext.com'
> >> >> > failed for
> >> >> > the following reason: An internal DNS error caused a failure to find
> >> >> > the
> >> >> > remote server.
> >> >> >
> >> >> > The only thing I can think of that I did around that time was put my
> >> >> > Windows
> >> >> > 2000 box into a new workgroup while trying to set up peer-to-peer
> >> >> > networking
> >> >> > between 2 machines at my house. I haven't changed any settings on
> >> >> > my
> >> >> > router.
> >> >> > I tried putting the computer back in the WORKGROUP workgroup, but
> >> >> > that
> >> >> > didn't fix the problem.
> >> >> >
> >> >> > I did run the smtpdiag utility, but I'm unsure of how to interpret
> >> >> > the
> >> >> > output. The output is included below. Any ideas what might be
> >> >> > going on?
> >> >> >
> >> >> > Thanks,
> >> >> > Roy
> >> >> >
> >> >> > Searching for Exchange external DNS settings.
> >> >> > Computer name is THEBOX.
> >> >> > Failed to connect to the domain controller. Error:
> >> >> > 8007054b
> >> >> >
> >> >> > Checking SOA for vtext.com.
> >> >> > Checking external DNS servers.
> >> >> > Checking internal DNS servers.
> >> >> >
> >> >> > Checking TCP/UDP SOA serial number using DNS server
> >> >> > [192.168.2.1].
> >> >> > Failed: DNS server [192.168.2.1] may be down.
> >> >> > DNS server [192.168.2.1] did not return a valid SOA
> >> >> > record.
> >> >> > SOA serial number match: Failed with one or more
> >> >> > failures.
> >> >> >
> >> >> > Checking local domain records.
> >> >> > Starting TCP and UDP DNS queries for the local domain.
> >> >> > This test will try to
> >> >> > validate that DNS is set up correctly for inbound
> >> >> > mail. This test can fail for
> >> >> > 3 reasons.
> >> >> > 1) Local domain is not set up in DNS. Inbound mail
> >> >> > cannot be routed to
> >> >> > local mailboxes.
> >> >> > 2) Firewall blocks TCP/UDP DNS queries. This will
> >> >> > not affect inbound mail,
> >> >> > but will affect outbound mail.
> >> >> > 3) Internal DNS is unaware of external DNS
> >> >> > settings. This is a valid
> >> >> > configuration for certain topologies.
> >> >> > Checking MX records using TCP: comcast.net.
> >> >> > Warning: The TCP DNS query returned no results.
> >> >> > Checking MX records using UDP: comcast.net.
> >> >> > MX: gateway-s.comcast.net (5)
> >> >> > MX: gateway-r.comcast.net (5)
> >> >> > A: gateway-s.comcast.net [IP address - looks valid]
> >> >> > A: gateway-s.comcast.net [IP address - looks valid]
> >> >> > A: gateway-r.comcast.net [IP address - looks valid]
> >> >> > A: gateway-r.comcast.net [IP address - looks valid]
> >> >> > A: dns01.jdc01.pa.comcast.net [IP address - looks valid]
> >> >> > A: dns02.jdc01.pa.comcast.net [IP address - looks valid]
> >> >> >
> >> >> > Checking remote domain records.
> >> >> > Starting TCP and UDP DNS queries for the remote
> >> >> > domain. This test will try to
> >> >> > validate that DNS is set up correctly for outbound
> >> >> > mail. This test can fail for
> >> >> > 3 reasons.
> >> >> > 1) Firewall blocks TCP/UDP queries which will
> >> >> > block outbound mail. Windows
> >> >> > 2000/NT Server requires TCP DNS queries. Windows
> >> >> > Server 2003 will use UDP
> >> >> > queries first, then fall back to TCP queries.
> >> >> > 2) Internal DNS does not know how to query
> >> >> > external domains. You must
> >> >> > either use an external DNS server or configure DNS
> >> >> > server to query external
> >> >> > domains.
> >> >> > 3) Remote domain does not exist. Failure is
> >> >> > expected.
> >> >> > Checking MX records using TCP: vtext.com.
> >> >> > Warning: The TCP DNS query returned no results.
> >> >> > Checking MX records using UDP: vtext.com.
> >> >> > MX: smtpsp.vtext.com (50)
> >> >> > MX: smtpsp1.vtext.com (50)
> >> >> > A: smtpsp.vtext.com [IP address - looks valid]
> >> >> > A: smtpsp1.vtext.com [IP address - looks valid]
> >> >>
> >> >>
> >> >>
> >>
> >>
>
>
><!-- ~MESSAGE_AFTER~ --> >> Stay informed about: smtp event log error |
|
| Back to top |
|
| |
External
Since: Jun 10, 2004
Posts: 1807
|
(Msg. 8) Posted: Thu Mar 03, 2005 4:35 pm
Post subject: Re: smtp event log error [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)
|
|
|
On Thu, 3 Mar 2005 12:15:11 -0800, Roy <rdeal RemoveThis @newsgroup.nospam> wrote:
>I'll have to confirm this, but I believe I can logon to the machine with the
>event log errors and ping it by name, and the IP address returned by ping is
>the same as it has always been 192.168.2.3. That is within the range that
>has been set up in my router.
>
>If I do an ipconfig /all, then the DNS IP is 192.168.2.1, which is correct.
>
>I'll try your suggestions tonight.
>
>You know, I remember one other thing I did to the network settings on the
>2nd machine in my home network. I disabled the Computer Browser service on
>it so it would not be the master browser. Could that have anything to do
>with this?
Not likely. That might affect NetBIOS name issues, but not DNS. Have
you simply retried the message? Some of these errors can be from
temporary network glitches too.
Jeff
>"Sparky Polastri" wrote:
>
>> Well the first step is to know what DNS should be for that domain. i.e. www
>> goes to what IP, MX goes to what hostname and then to what IP.
>>
>> Then use ping to find out what the DNS resolution on that box is (by logging
>> onto it, using ping with the hostname) and compare that with what your
>> network actually is.
>>
>> Chances are a) your DNS resolution system is not working (thus "Internal DNS
>> error") or b) DNS is cached locally and reporting the wrong IP for that mail
>> server or c) dns for that domain actually is messed up.
>>
>> Logging onto the box can get you a) and b). c) can be done using any number
>> of tools on the web.
>>
>> Also in general, DNS is forced to refresh if you reboot devices (including
>> the router). Whether or not you should do that depends on your use of the
>> machines. If you can't reboot, stop and restart the DNS client service on
>> the computer to make sure it is not "remembering" the wrong IP addresses.
>>
>> "Roy" <rdeal RemoveThis @newsgroup.nospam> wrote in message
>> news:8509B4B4-0630-4164-98D3-1BD9692E30E5@microsoft.com...
>> > Thanks for the pointers, Jeff and Sparky. Since the event log error
>> > mentions
>> > an internal DNS error, it seems like I should use nslookup to troubleshoot
>> > my
>> > router's DNS server. Is that correct? If so, then what queries do I
>> > issue?
>> >
>> > I see from <a style='text-decoration: underline;' href="http://support.microsoft.com/kb/200525" target="_blank">http://support.microsoft.com/kb/200525</a> examples for querying my
>> > ISP's incoming/outgoing email hosts (mail.comcast.net/smtp.comcast.net),
>> > but
>> > how do I query MY machine to make sure it's getting proper DNS?
>> >
>> > "Jeff Cochran" wrote:
>> >
>> >> On Thu, 3 Mar 2005 06:27:04 -0800, Roy <rdeal RemoveThis @newsgroup.nospam> wrote:
>> >>
>> >> >I am not very networking savvy, so what you mean by do some DNS queries?
>> >> >I
>> >> >did do a few things with nslookup - I that's along the lines of what you
>> >> >recommended - that I read in a kbase article or two, but interpreting
>> >> >the
>> >> >output is not my strong suit.
>> >>
>> >> Post the output in the DNS groups and you'll get a decent tutorial in
>> >> how to read them.
>> >>
>> >> Jeff
>> >>
>> >> >Thanks for the advice.
>> >> >
>> >> >"Sparky Polastri" wrote:
>> >> >
>> >> >> Log onto the box and do some DNS queries to make sure the box is
>> >> >> getting
>> >> >> proper DNS.
>> >> >>
>> >> >> Changing network stuff around could very well cause ripple-effect type
>> >> >> errors in DNS.
>> >> >>
>> >> >> "Roy" <rdeal RemoveThis @newsgroup.nospam> wrote in message
>> >> >> news:C3371806-8B84-4F43-8321-EAFD4875F417@microsoft.com...
>> >> >> >I have a program that I wrote which sends text messages to my cell
>> >> >> >phone.
>> >> >> > The program uses IMessage from cdosys. It has been working fine for
>> >> >> > about
>> >> >> > a
>> >> >> > year, but about a week ago, errors like the following started
>> >> >> > showing up
>> >> >> > in
>> >> >> > the nt event log:
>> >> >> >
>> >> >> > source: smtpsvc
>> >> >> > event id: 4000
>> >> >> > description: Message delivery to the remote domain 'vtext.com'
>> >> >> > failed for
>> >> >> > the following reason: An internal DNS error caused a failure to find
>> >> >> > the
>> >> >> > remote server.
>> >> >> >
>> >> >> > The only thing I can think of that I did around that time was put my
>> >> >> > Windows
>> >> >> > 2000 box into a new workgroup while trying to set up peer-to-peer
>> >> >> > networking
>> >> >> > between 2 machines at my house. I haven't changed any settings on
>> >> >> > my
>> >> >> > router.
>> >> >> > I tried putting the computer back in the WORKGROUP workgroup, but
>> >> >> > that
>> >> >> > didn't fix the problem.
>> >> >> >
>> >> >> > I did run the smtpdiag utility, but I'm unsure of how to interpret
>> >> >> > the
>> >> >> > output. The output is included below. Any ideas what might be
>> >> >> > going on?
>> >> >> >
>> >> >> > Thanks,
>> >> >> > Roy
>> >> >> >
>> >> >> > Searching for Exchange external DNS settings.
>> >> >> > Computer name is THEBOX.
>> >> >> > Failed to connect to the domain controller. Error:
>> >> >> > 8007054b
>> >> >> >
>> >> >> > Checking SOA for vtext.com.
>> >> >> > Checking external DNS servers.
>> >> >> > Checking internal DNS servers.
>> >> >> >
>> >> >> > Checking TCP/UDP SOA serial number using DNS server
>> >> >> > [192.168.2.1].
>> >> >> > Failed: DNS server [192.168.2.1] may be down.
>> >> >> > DNS server [192.168.2.1] did not return a valid SOA
>> >> >> > record.
>> >> >> > SOA serial number match: Failed with one or more
>> >> >> > failures.
>> >> >> >
>> >> >> > Checking local domain records.
>> >> >> > Starting TCP and UDP DNS queries for the local domain.
>> >> >> > This test will try to
>> >> >> > validate that DNS is set up correctly for inbound
>> >> >> > mail. This test can fail for
>> >> >> > 3 reasons.
>> >> >> > 1) Local domain is not set up in DNS. Inbound mail
>> >> >> > cannot be routed to
>> >> >> > local mailboxes.
>> >> >> > 2) Firewall blocks TCP/UDP DNS queries. This will
>> >> >> > not affect inbound mail,
>> >> >> > but will affect outbound mail.
>> >> >> > 3) Internal DNS is unaware of external DNS
>> >> >> > settings. This is a valid
>> >> >> > configuration for certain topologies.
>> >> >> > Checking MX records using TCP: comcast.net.
>> >> >> > Warning: The TCP DNS query returned no results.
>> & | | |
FAQ
Search
Profile
Private Messages
Log in/Register/Password
