smtp event log error
in [IIS]
|
Prev: Problems loading an Excel File
Next: iisadmin.mfl
From: Roy on 3 Mar 2005 09:03 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]
From: Sparky Polastri on 3 Mar 2005 09:18 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(a)newsgroup.nospam> wrote in message news:C3371806-8B84-4F43-8321-EAFD4875F417(a)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]
From: Roy on 3 Mar 2005 09:27 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(a)newsgroup.nospam> wrote in message > news:C3371806-8B84-4F43-8321-EAFD4875F417(a)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] > > >
From: Jeff Cochran on 3 Mar 2005 12:14 On Thu, 3 Mar 2005 06:27:04 -0800, Roy <rdeal(a)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(a)newsgroup.nospam> wrote in message >> news:C3371806-8B84-4F43-8321-EAFD4875F417(a)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] >> >> >>
From: Roy on 3 Mar 2005 12:45
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 http://support.microsoft.com/kb/200525 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(a)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(a)newsgroup.nospam> wrote in message > >> news:C3371806-8B84-4F43-8321-EAFD4875F417(a)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] > >> > >> > >> > > |