HELP!!!!! Can't connect to any external mail servers!
I'm using exchange 2003, I've been trying to fix my email for the past 2 hours...I can't connect to any other mail servers but my own...web is working. I totally rebuilt all the DNS...I just don't get it. Please help!
what do you mean you can not connect to other mail servers? If you have a specific error please post it.
Check your Access/Authentication settings and restart your Default SMTP Service
just a guess waiting for your details
ASKER
Hey jono!
Thank for responding...listen...I got outbound mail working. but now what I'm having a problem with is that messages just keep building in the "messages pending submission" section of the Queue...any ideas?
Thank for responding...listen...I got outbound mail working. but now what I'm having a problem with is that messages just keep building in the "messages pending submission" section of the Queue...any ideas?
SMTP Properties--> Access--> Relay--> check the box at the botom to allow authenticated realy
Is this the only exchange server you have or do you have a front end back end setup? Do you need to relay to an ISP or are you responsable for your own email? Did you check all services to see if they are running. Does your event log have any errors in it?
ASKER
Hey guys, thanks for trying to help me out...it was actually a combination of problems...GFI, DNS, ISA
I'm going to get my points refunded.
I'm going to get my points refunded.
neomage23 - We are all willing to learn from experience. Would you careto elaborate on your solution?
ASKER
Yes, I'm sorry.
It was a combination of things that led me to this problem. For one, DNS wasn't set up properly. I'm using a schema where I need to maintain two zones...one for my internal active directory and another zone for my external stuff (www, mail, NS) but for some reason I thought I could get away with just having DNS on my ISA server servicing both internal and external requests from internal clients.
Various aspects of that setup began to cause problems with exchange because exchange didn't know where to get DNS information from.
This was further complicated by GFI Mail Security which was configured to reject message for which it could not perform a reverse - lookup on.
Yikes!
So, to fix this, I split the DNS duties the internal server strictly maintains active directory DNS information, and services requests for internal clients, but when it needs to resolve an external name it forwards the request to the ISA computer which is configured to query root servers.
That's it in a nutshell!
It was a combination of things that led me to this problem. For one, DNS wasn't set up properly. I'm using a schema where I need to maintain two zones...one for my internal active directory and another zone for my external stuff (www, mail, NS) but for some reason I thought I could get away with just having DNS on my ISA server servicing both internal and external requests from internal clients.
Various aspects of that setup began to cause problems with exchange because exchange didn't know where to get DNS information from.
This was further complicated by GFI Mail Security which was configured to reject message for which it could not perform a reverse - lookup on.
Yikes!
So, to fix this, I split the DNS duties the internal server strictly maintains active directory DNS information, and services requests for internal clients, but when it needs to resolve an external name it forwards the request to the ISA computer which is configured to query root servers.
That's it in a nutshell!
Trying to maintain your own NS owutside AD can get dicey
Close and refund
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.