Router not mailing

Recently I switched from cable to ADSL.

Under "cable", I had a D-Link DI-614+ router connected to the modem, using PPPoE. It's firmware was upgraded to the latest version (2.20).
All PC's and the router used the correct provider's smtp server. All outgoing mail arrived as expected, including the router's logs.

Now the router is connected to my Alcated Speedlink 530 ethernet modem (1 port). I changed SMTP servers and PC's appear to send mail correctly. The router itsef however fails sending mail (haven't got much info other than a message like "Failed sending mail").

What could be wrong?

As far as I know I have no restrictions in SMTP ports (both the modem and the router have a firewall).
The modem has internal IP address and assigns to the router.
The router uses internally and all PC's have adresses in that range (.150 - .250).

The ADSL connection is by KPN (for any dutch readers), and is appearently using PPTP. My knowledge is very limited on that (none!). I have connected the router to the modem using an "ethernet" connection type (not PPPoE, not PPTP). No problems using mail, MSN, browsing, FTP etc. from a PC. Only SMTP from the router.
LVL 13
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Do you know the address of the mail server?  Can you ping that address?  Have you tried to telnet to port 25 on that address?  Does the d-link router have any firewalling features enabled?

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
CRAKAuthor Commented:
The server ( doesn't respond to pinging: it times out. Sending mail from the same PC to that server still works!

Telnet connection (using Hyper terminal in XP) to the server (port 25) responded "220 ESMTP" (postbode is dutch for the guy that delivers mail to your door). Don't know what this means, didn't know what to do with this connection. Disconnected again.

The routers firewall has following enries:
Allow NetBios, Source *,, Dest *,(same range), protocol IP (0), 135-139
Allow Oracle, Source *.(same range), Dest *,(same range), protocol IP (0), 1521
Deny Default, Source *,*, Dest LAN,*, IP (0),*
Allow Default, LAN,*, Dest *,*, IP (0),*
(in that order; the bottom two are the devices defaults and can not be altered, I added the first two, schedule: always and enabled)

Options for Source/Dest are *, WAN or LAN + IP range.
Options for Protocol are TCP, UDP, ICMP or * + port range
Someone else will have a better answer than I.  I don't know d-link router configuration.  My guess is that you need to change something in your router config.
Big Business Goals? Which KPIs Will Help You

The most successful MSPs rely on metrics – known as key performance indicators (KPIs) – for making informed decisions that help their businesses thrive, rather than just survive. This eBook provides an overview of the most important KPIs used by top MSPs.

CRAKAuthor Commented:
So far you're the only one answering. Guess who provived the best options so far?.....

A correction on the router's "WAN" settings:
I'm using "Dynamic IP adres", supplying host name (DI-614+), MAC address, Pri/Sec DNS address ( resp. and "MTU"(?) = 1500.

PPTP would require IP address, subnet mask, server IP, PPTP account, PPTP password + retype, max idle time, "MTU" and auto reconnect (enable/disable).

I'll raise points to attact a wider audience, but please don't let me down!?
Assuming you have WinXP, I also assume you have gone here for the "quick-install" documentation:

When you ping the SMTP server, does the name resolve to an IP address?
Are you stil using the same router (D-Link DI-614+ router) ?

--> PC's appear to send mail correctly.
 ?? Only 'appears'  or have you verified (e.g. create a free mail account somewhere out there, and use it for verification)

--> The router itsef however fails sending mail (haven't got much info other than a message like "Failed sending mail").

did you get that msg from the router ?

have you tried reverting to using only the cable modem + 1 Win XP box and verifying mail transport is ok at that level?

are you able to browse internet problemfree from all boxes inside ?

have you upgrade modem and router firmware to latest versions ?
CRAKAuthor Commented:
The installation manual was included with the device. Didn't go through it again, since everything else worked....
I don't trust this PPTP thing though. I noticed on several ADSL providers forums that a lot of people have trouble installing a router behind the modem. PPTP is often mentioned, hardly ever supported by the router (I needed the firmware upgrade) and most people don't seem to get it to work in any way.

Ping did resolve the IP address.

"Appears"... probably a language problem. Mail was sent and received correctly.

Part of the log:
Nov/03/2003 10:21:49  SMTP: sending mail fail    
Nov/03/2003 09:55:44  DHCP Request success
Nov/03/2003 09:55:44  DHCP Request
Nov/03/2003 09:21:49  SMTP: sending mail fail    
Nov/03/2003 08:55:44  DHCP Request success

Pc connected directly to modem works fine. Either way no problems detected while surfing etc. Im typing this while online through the router's WiFi connection...
PC's are either XP or 98.

I noticed that there is a newer firmware version, but D-link reccommends to upgrade only in case of "connectivity issues". I don't thinks that's the case.
The modem itself logs in on www though: he's got the account + password; not the router.

(Shineon... thanks for staying around!)
Just trying to clarify:

you actually have any problems mailing from the computers in any setup, it's just the router that gives that report ?

what mail are you expecting the router to send ? (firewall/administrative reports ?)

If you are expecting the router to mail you:  have you configured the router with an e-mail address where it should send administrative msg's and the address for an SMTP server ?

Sorry, typo:

> you don't actually have any problems mailing from the computers in any setup, it's just the router that gives that report ?
CRAKAuthor Commented:
That's right: I DON'T have an actual problem, expect when the router itself generates an email.
The mail address remains unchanged. I already used it under the cable account. It's the same account where my EE notifications arrive. It's a free account at the ADSL provider.
I DID change the smtp server from my cable providers one to the ADSL providers one.

The router could periodically send mail (containing the entire log) or do so when attacks occur. E.g. I previously (cable) received some mails that the router received some "ping of death"'s and that those packages were ignored.
ok, - then perhaps the router is not configured to have a hostname and a domain? Some mailservers will reject mail from an unverifiable sender.
CRAKAuthor Commented:
All PC's are internally 192.168.0.x, so is the router.
NAT (router) would translate everything to and pass it on to the modem (
From there (after NAT in the modem) all traffic as seen from the provider is "native" to their systems.
I don't think we have to consider the IP scheme on this problem, I am fairly sure it's a name-related probem of some sorts.

You can try telnetting your router and ping the smtp by name and see if it resolves, - this will verify dns configuration of router.

If the router has some facility for telnet or similar (from within a telnet session to the router), then you can try doing a manual mail delivery´(open a session to your mailserver on port 25/SMTP and write (don't mind the lack of echo):

test test

Replace domain names with valid domain names and pbox at target with valid accounts (from pbox can be anything).

CRAKAuthor Commented:
I don't see how a can feed that to the router, but I tried it on a wireless notebook...
Neat trick! I don't know what happened, but I think I just killed the smtp server. It's now returning a "permanent error" to my mail program (Lotus Notes)....
Don't tell anyone... and don't put the confession online please!?
CRAKAuthor Commented:
At > support > DI 614+ > 2 antenna type you'll find a simulation of the router. Perhaps its any help to discover what it can/can't do....
Don't worry CRAK: an SMTP server should be able to handle it self, even if you mistype a few words. I see no mallicious (is that how it's spelled?) behaviour in sending a mail 'by hand', - after all: that's how it all started, and we still basically run by the same principles no matter how flashy your GUI gets!

Anyhow, - did you try to ping the SMTP while telnet'ed into the router ?
CRAKAuthor Commented:
Hang on....
"...telnet'ed into the router...": I was connecting to Straight through the router + modem. Should I have connected to the router only (as Can you please tell what the "helo" instruction does, so I can determine what to fill out there?

No sorry, I telnet'ed, disconnected after a while an pinged separately. Didn't understand I had to do those simultaneously (we should have a spelling checker at EE, don't you think?). Will try again tonight. I'm at work right now.
don't worry, - old stuff is always messy to fiddle with ;-)

So: yes, - I meant that you should try doing it while telnet'ed to the router, simulating that it is the router mailing.

The 'helo' stuff is not always required, - today various practices apply, but it's civil behaviour to use it.

The text you enter should be (exactly, - notice the '.' on a line by itself):

test test

helo: 'origin' means whatever a dns-lookup for your outside IP would return. You get this info by (from a cmd-box):
> nslookup
> server [public ns]
> set type=PTR
> [public IP]
.. (here comes the reply)
> exit

[public ns] = IP of one of the public nameservers you use (no brackets!)
[public IP] = your public IP (no brackets!)

You will probably get an answer of 5-10 lines. What you are looking for is "name = ". The name can be quite a long string.
Many mail-servers do a ns-lookup to verify the caller.
You can try doing it without the helo, and use '' as [] in the "mail from:" line. It will not always work, as some mail-servers require either the helo or a valid originator-domain (or both).

 . . . . . . anyhow: lot's of instructions from me here, but no help in it ;-) Remember to test the nslookup from the router (i.e. when you are in a telnet session) or get some IP-status in same situation, to make sure it knows a valid name-server.

CRAKAuthor Commented:
Both with and without a telnet session open, pinging returns, but all requests timed out.
Well, - unfortunately that only tells us that the  router has dns setup ok, - the missing reply from the SMTP may be due to a deactivation of IGMP at their end.

Do you get a ping-reply from the SMTP from other places ?
CRAKAuthor Commented:
I'm at work again. Same result on ping here. Can't connect to the server though since I'm not on one of their IP adresses (I guess). At home I tried an 98 PC over WiFi and an XP one wired. Same result.

I'm still wondering... could the (not chosen) tunneling protocol have anything to do with it? What is it anyway?
CRAKAuthor Commented:
D-link advised me to lower MTU (currently 1500) in steps of 100.
Meanwhile I found another two switches to log some more. I now get these failures when the router attempts to generate e-mail itself:
SMTP: unexpected reply: 451 See 

I've sent this info back to D-Link. I suspect the new firmware. Agree?
CRAKAuthor Commented:
I didn't realize thisone was still open....

D-link has released new firmware. I understood that I should download from the UK site, not the US one (I think I did previously). Will try that once I've generated the required energy for it (and some spare time left).

Meanwhile I used a different workaround: my causin has got a mail server of his own. He now accepts mail from my IP address. Clients still connect to The router to my causin's server.

Solved for now (though I'm still not entirely satisfied), but now I need a hand on a different thing.....
What do I do with the 500pt? Not a refund after all the time you've spent....
Are the two of you still around?
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.