Link to home
Start Free TrialLog in
Avatar of jasonmichel
jasonmichel

asked on

Exchange 2010 451 4.4.0 Primary Target IP address responded 421 4.2.1 unable to connect.

have a new exchange 2010 installed into a forest with a 2007 server already running, the two exchange servers serve different domains,  on the 2010 server all out going messages sit in queue with the error 451 4.4.0 Primary Target IP address responded 421 4.2.1 unable to connect., i have my send connector set to send to internet.  I can ping mail.domain.com for a domain in queue and it replies, i can nslookup and it resolves fine, but i cannot telnet into it at all..any ideas?
ASKER CERTIFIED SOLUTION
Avatar of zulumike
zulumike
Flag of Norway image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Has this only just happened recently? Have you tried the message flow troubleshooting assistant in the Toolbox?Does the Exchange 2010 server have it's own Send Connector? Are any Send Connectors set to deliver to a Smart Host or do they send direct to the Internet via DNS?
Avatar of jasonmichel
jasonmichel

ASKER

Firewall is fine.. running server2008 yes own send connector sending to internet..this is fresh install
Firewall is fine.. running server2008 yes own send connector sending to internet..this is fresh install
Uninstall AV / EPO / firewall off the Exchange 2010 server and then see if messages start flowing or not.

Does your server have more than 1 NIC installed?
firewall is off, and there is no AV installed yet.  Yes server only has 1 nic
heres something odd, i can't telnet to any outside mailserver from inside the network on 25, i wonder if a firewall gpo could be the problem?
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
You can find MX records for other domains with Www.mxtoolbox.com and then try telnet on port 25 from your network to that server (MX record)
it was an acl on the router, thanks for the help tho
Thanks for the points and final solution