• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 224
  • Last Modified:

Exchange is able to receive but not send messages.

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
lilceez
Asked:
lilceez
  • 5
  • 5
1 Solution
 
redseatechnologiesCommented:
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
 
lilceezAuthor Commented:
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
 
redseatechnologiesCommented:
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
Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

 
lilceezAuthor Commented:
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
 
redseatechnologiesCommented:
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
 
lilceezAuthor Commented:
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
 
redseatechnologiesCommented:
>>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
 
lilceezAuthor Commented:
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
 
redseatechnologiesCommented:
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
 
lilceezAuthor Commented:
The modem was bad... I appreciate your help though. Thanks!
0

Featured Post

Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

  • 5
  • 5
Tackle projects and never again get stuck behind a technical roadblock.
Join Now