Solved

Exchange is able to receive but not send messages.

Posted on 2007-04-04
10
216 Views
Last Modified: 2010-03-06
Exchange server is receiving but not sending messages. All messages sent are staying in queue. I would think it is a DNS issue but I have tried changing forwarders and it still doesn't work. Please help!
0
Comment
Question by:lilceez
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 5
  • 5
10 Comments
 
LVL 39

Expert Comment

by:redseatechnologies
ID: 18854529
On the queues, what does it say (down the bottom, there should be a reason as to why they are not going).

Generally, this will be because you are forwarding to a dead smarthost, or have dodgy DNS entries on the exchange server (in exchange, you can also set dns servers, which is not desirable)
0
 

Author Comment

by:lilceez
ID: 18854735
It says "no additional information is available" on the the emails I tried to send. On some of the other random emails it says "remote server cannot be found"
0
 
LVL 39

Expert Comment

by:redseatechnologies
ID: 18854788
Sounds like it could be DNS then.

Exchange can have DNS entries here - remove them totally;

ESM > Your Server > protocols > SMTP > (right click) default SMTP server > properties > Delivery > advanced > configure

Also, on the advanced tab, ensure that there is no smarthost entry listed.

-red
0
Office 365 Training for Admins - 7 Day Trial

Learn how to provision tenants, synchronize on-premise Active Directory, implement Single Sign-On, customize Office deployment, and protect your organization with eDiscovery and DLP policies.  Only from Platform Scholar.

 

Author Comment

by:lilceez
ID: 18855272
I actually tried that earlier. Right now there is nothing in there  and it still doesn't work. Thanks again for your help, I really appreciate it. Do you have any other suggestions?
0
 
LVL 39

Expert Comment

by:redseatechnologies
ID: 18855301
Do you have any anti-virus on the server by chance?

Another thing I would do is look at routing all mail via a smart host; this will get mail going until you fix it properly

http://www.amset.info/exchange/smtp-connector.asp

-red
0
 

Author Comment

by:lilceez
ID: 18855484
That's what I did. This server is located at my boss' house. He has his own domain, exchange server, the works. He has a VPN to the office and have I have trust between his domain and work's. What I did was add his server as computer able to relay on work's exchange and made his connector forward all email to work's exchange server instead of using DNS. I still need to figure out why its not working using DNS. I have a theory but I can't test it out this moment though, let me know if you think it makes sense. On his firewall we have 2 seperate lines of service, cable and DSL. The cable is a dynamic ip and used as the primary gateway just because its about 10Mb/ download speed compared to DSL's 3Mb. The DSL however has 5 static IP's which we use to NAT to certain things behind the firewall. I just noticed that the server, even though is assigned a static and that is what we have in registered in DNS, it is actually for some reason going out using the dynamic address. Now when you do a reverse DNS it will look like it's coming from a different server, would this actually prevent emails from going out or just label them as spam on the recipient's inbox?
0
 
LVL 39

Accepted Solution

by:
redseatechnologies earned 500 total points
ID: 18855619
>>would this actually prevent emails from going out or just label them as spam on the recipient's inbox?

Very possibly, but it is more likely that it would bounce than just timeout

It is also possible that the ISP is blocking traffic to port 25.

Try telnetting to a server from your server on port 25 and see what it does;

telnet mail.bigpond.com 25
ehlo yourdomain.com
mail from:whoever@yourdomain.com
rcpt to:postmaster@bigpond.com
data
subject:this is a test
this is a test email
.

i expect it will either not work at the start, or die when you try to "ehlo"

-red

0
 

Author Comment

by:lilceez
ID: 18855629
But we can receive email over port 25. This is also a business account through AT&T, there are no ports blocked as far as I know, I'll give it a shot though.
0
 
LVL 39

Expert Comment

by:redseatechnologies
ID: 18855641
receiving on 25 is not really a security risk - but if it is a business account it is unlikely.

try the test anyway and tell me where it fails

-red
0
 

Author Comment

by:lilceez
ID: 18887636
The modem was bad... I appreciate your help though. Thanks!
0

Featured Post

Free Tool: IP Lookup

Get more info about an IP address or domain name, such as organization, abuse contacts and geolocation.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Read this checklist to learn more about the 15 things you should never include in an email signature.
This article will help to fix the below errors for MS Exchange Server 2013 I. Certificate error "name on the security certificate is invalid or does not match the name of the site" II. Out of Office not working III. Make Internal URLs and Externa…
In this video we show how to create a Contact in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center. Navigate to the Recipients >> Contact ta…
In this video we show how to create a mailbox database in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center. Navigate to the Servers >> Data…

728 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question