I tested in the early hours today and this is what happend. I cut our isp connection and I was able to send an email internally for the early 1-2 minutes or so after the internet was shut off, then it got flakey.
I couldnt even telnet to it. Remember also that all clients are dhcp clients and they get our internal dns server for Pri and Sec. Im not sure what the deal is. I tried this with recursion on and off on the dns forwarders tab. Still the same either way. Here is how internally its setup and working C:\>nslookup Default Server: waco-dc1.waco-domain.com Address: 192.168.1.13 > set type=mx > waco-eng.com Server: waco-dc1.waco-domain.com Address: 192.168.1.13 waco-eng.com MX preference = 10, mail exchanger = 192.168.1.13 > quit Server: waco-dc1.waco-domain.com Address: 192.168.1.13 > C:\>ping mail.waco-eng.com Pinging mail.waco-eng.com [192.168.1.13] with 32 bytes of data: Reply from 192.168.1.13: bytes=32 time<10ms TTL=128 Reply from 192.168.1.13: bytes=32 time<10ms TTL=128 This is how its working from the clients internally. On the outside trying this you get the correct WAN ip. I dont understand why this will not work if our ISP fails. It must have something to do with our DNS here but what? -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of webmaster Sent: Monday, October 20, 2003 2:46 PM To: [EMAIL PROTECTED] Subject: [xmail] Re: local sending problem "If it doesn't work at all, try pushing *only* your internal DNS servers to the client, and let your DNS servers handle lookups that aren't in it's cache. See if that helps." This is currently how it works here. The dhcp server gives out the dns of the two local internal servers. I have forwarding setup in both DNS servers. And to answer your first question.. I kinda think its internmittant but it may be as soon as the inet goes down. I need to unplug and test to really see, maybe after hours. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Tracy Sent: Monday, October 20, 2003 2:24 PM To: [EMAIL PROTECTED] Subject: [xmail] Re: local sending problem Does it not work at all when the net conneciton is down, or does it not work intermittantly when the net connection is down? The thing about Windows and DNS client setup is that Windows will randomly choose which DNS server to make a lookup against (although, I have to say that the "random" choice that Windows makes always seems to be to the one that's not working when I need to do something...:) If it doesn't work at all, try pushing *only* your internal DNS servers to the client, and let your DNS servers handle lookups that aren't in it's cache. See if that helps. You can also try manually sending a test message from one of the failing clients using telnet... telnet mail.whatever.com 25 HELO Testing.mail MAIL FROM: <[EMAIL PROTECTED]> RCPT TO: <[EMAIL PROTECTED]> DATA Subject: This is a test message Date: 20 Oct 2003 15:30:00 From: Testing Mail Connectivity To: Testing Mail Connectivity This is a test to see if mail can be sent manually. .... QUIT If that succeeds, then it's Outlook. If that fails (especially if telnet fails to connect), it's probably DNS related. Tracy At 15:14 10/20/2003, webmaster wrote: >Tracy thanks for the speedy response but I do have it setup that way. > >I have my internal dhcp server scope options set to give all clients my two >internal dns servers. > >On my dns server I have an mx record for internal use as well as >"mail.whatever.com" >All clients can ping the mail.whatever.com and get the correct lan Ip of >the mail server but if the internet goes down we have trouble. > >I have my dns server setup with my isp servers for forwarding and for some >reason if there is no inet connection it just still will not work right even >though everything is set to use the local stuff. > > >-----Original Message----- >From: [EMAIL PROTECTED] >[mailto:[EMAIL PROTECTED] Behalf Of Tracy >Sent: Monday, October 20, 2003 12:08 PM >To: [EMAIL PROTECTED] >Subject: [xmail] Re: local sending problem > > >At 13:02 10/20/2003, webmaster wrote: > >It appears that if my forwarders are not correct or my isp goes down. I > >cannot send mail internally. > > > >Task 'email - Sending' reported error (0x8004210B) : 'The operation > >timed out waiting for a response from the sending (SMTP) server. If you > >continue to receive this message, contact your server administrator or > >Internet service provider (ISP).' > > > >I get the above message generated by outlook xp or the following error > >message generated by outlook 2k and outlook 97 > > > >Your message did not reach some or all of the intended recipients. > > > > Subject: RE: Please reply > > Sent: 10/20/2003 11:43 AM > > > >The following recipient(s) could not be reached: > > > > '[EMAIL PROTECTED]' on 10/20/2003 11:44 AM > > No transport provider was available for delivery to this > >recipient. > > > > > > > >Whats the Deal with this? > > >Some choices: > >1) Configure an internal DNS server that resolves IPs for your domain - so >that clients can resolve the IP of the mail server even if your ISP is >down. Don't forget to change the client configuration to point to those DNS >servers. > >2) Add an entry to the HOSTS file (C:\WINNT\System32\Drivers\Etc) for your >mail server, so the address will always be resolved locally (again, must be >done on each machine). > >3) Configure Outlook to point to the IP address of the server rather than >the DNS name (strongly not recommended). > > >- >To unsubscribe from this list: send the line "unsubscribe xmail" in >the body of a message to [EMAIL PROTECTED] >For general help: send the line "help" in the body of a message to >[EMAIL PROTECTED] > > >- - To unsubscribe from this list: send the line "unsubscribe xmail" in the body of a message to [EMAIL PROTECTED] For general help: send the line "help" in the body of a message to [EMAIL PROTECTED]
