A few weeks back, our ISP decided that they were going to upgrade the mail servers. On the day they were upgraded we could no longer access the mail servers. My wife, who was and still may be extremely pissed, spent two days with the Technicians who could not help. At the end of the second day, my wife mentioned that we had a router and was told that was the problem. That evening I removed the LEAF router and the mail connection was _all well_ as the Windows XP box could connect to the mail server. Thinking that the problem was with my setup of the LEAF box, I am using Dachstein CD V1.0.2, I set up the box to use the default Dach settings. This still did not allow connection to the mail server. At this time I was beginning to believe that DNS could be that problem. About a year and a half ago, the ISP changed the mail server name. Using XP's built in _firewall_ I discovered the IP address for the mail server and using that instead of a the FQN, I was able to get access to the mail server through the LEAF box with the XP Box.
So thinking that since the XP box could connect to the mail server without the LEAF box using the FQN, I changed the LEAF box, at least I think I did, to use my ISP's DNS instead of dnscache in the LEAF box. But alass this _still did not_ work. I added my ISPs servers to DNS0 and DNS1 and set CONFIG_DNS to YES. Soooo, on a hunch I changed my mail Client to access the original mail server name and it works! Original server name = mail.cablespeed.com and the one that was working before the change = mail.bllvwa.cablespeed.com.
The real question becomes, why when using the mail server name when connected direct from XP it works, where as having the LEAF box connected using the mail server name does not work. Is there some difference when using the ISP DNS versus going through the LEAF box with the ISP DNSs identified.
Thanks for any and all help in advance and sorry about the convoluted message.
I don't think you have really told us enough to let us spot the problem.
First thing: does your ISP have a policy against its customers using home routers? Assuming not (if they do, I really would consider changing ISP and telling this one why), the natural thing to do is to ask them how to access their mail server through a router.
Second thing: from out here, both the FQNs you list above resolve to the same IP address:
[EMAIL PROTECTED]:~$ ping mail.cablespeed.com PING mail.cablespeed.com (216.15.205.76): 56 data bytes 64 bytes from 216.15.205.76: icmp_seq=0 ttl=46 time=68.3 ms [...] [EMAIL PROTECTED]:~$ ping mail.bllvwa.cablespeed.com PING mail.bllvwa.cablespeed.com (216.15.205.76): 56 data bytes 64 bytes from 216.15.205.76: icmp_seq=0 ttl=46 time=67.7 ms [...]
This makes me inclined to dismiss any "solution" achieved by changing SMTP server name as a red herring.
Third thing: I would try to sort out the DNS issues directly. Log on to the router and try to ping both FQNs, and see whether they resolve or not. If they don't, stick with the DNS approach to sorting out the problem. IF they don't, then leave it behind and focus on service issues. Or, for that matter, try to ping them from the XP host when it is connected through the Dach router.
Fourth thing: might there be an auth (ident) service issue here? Do you have the Dach box set to ACCEPT traffic to the ident port? For obscure reasons, auth requests respond differently to the connection failure associated with an accessible port that has nothing listening on it than they do to the connection failure associated with a firewall REJECT or DENY.
Last thing: One other way to sort out the DNS component is to tell your XP host to use the ISP's DNS servers, not the forwarder running on Dach. Telling the Dach router to use them, the way you did it (DNS0 and DNS1, I mean), doesn't cause it to use them when resolving connections requested by LAN hosts, just when resolviing connections it needs to make itself.
If none of these thoughts get you anywhere, you might post a followup describing "does not work" in more detail. Do you have a reason, based on the exact failure you see, to blame DNS for this, rather than some problem at the SMTP, or other service, level? (That is, do you get a message like "no such host" when you try to connect, rather then the FQN seeming to resolve but the SMTP connection not completing? I can't be more exact here, since I don't know what e-mail client you use on the XP host ... but here, using Eudora on Win2K, it is easy to distinguish the two types of failure.) For example, if you get your external IP address via DHCP, the hostname of a LAN host might not match the hostname the ISP expects to be associated with that address ... a bit of a long shot, but anti-SPAM measures are getting weirder and weirder.
------------------------------------------------------- SF.Net is sponsored by: Speed Start Your Linux Apps Now. Build and deploy apps & Web services for Linux with a free DVD software kit from IBM. Click Now! http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click ------------------------------------------------------------------------ leaf-user mailing list: [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user SR FAQ: http://leaf-project.org/pub/doc/docmanager/docid_1891.html
