We have a scenerio of network in which our front-end exch server is connected with our ISA firewall for e-mail forwarding.
but since yesterday we are getting an issue in sending mails to external domains. the problem is that while sending the user gets different undelivery message eg. " There was a SMTP communication problem with the recipient's email server. Please contact your system administrator.
Please provide your kind support on this ASAP.
- If you need clarification, ask it in the comment box above.
- Better answers use proper spelling and grammar.
- Provide details, support with references or personal experience.
Tell us some more! Your answer needs to include more details to help people.You can't post answers that contain an email address.Please enter a valid email address.The email address entered is already associated to an account.Login to postPlease use English characters only.
Tip: The max point reward for answering a question is 15.
I have no idea what firewall you are using. Your posting is lacking crucial detail and that makes this almost impossible to answer you. However, I use a Cisco 5520 in a Data Center and i Host my own Exchange server. This is what you have to do to allow inbound and outbound SMTP traffic in that type of environment.
name (Internal IP here) Exchange description Internal mail server
access-list Inside_access_in remark Allow internal Exchange Server to send SMTP email outbound.
access-list Inside_access_in extended permit tcp host (Internal IP Here) any eq smtp
access-list outside_access_in remark Allow external entities to send SMTP email to Exchange Server
access-list outside_access_in extended permit tcp any host (Public IP Here) eq smtp
This is an excerpt from a MS Technet page for error 53:
Resolutions:1) if it is domain environment, check your WINS; 2) if it is peer-to-peer workgroup, enable NetBIOS over TCP/IP; 3) make sure the machine is running; 4) make sure file and Printer Share enabled on remote computer; 5) make sure client for ms networks is enabled on local computer; 6) make sure you type the correct name. 7) Make sure no firewall running or any security setting.
Pay close attention to #s 4 and 5 - I suspect XP pro might not be open enough.
You might have to create a custom exception rule for Outlook.exe, but this can create compromises to your overall security. Please see article here and here and here and here Also be aware that 3com has a support forum online that may be of some assistance if you can't get it work.
I hope this information allows you to resolve this issue. If you need further assistance, please post back with a comment to this thread. If I've managed to answer your question or solve a problem, please take just a moment to rate this post....thanks!
When a company has a Web monitoring server sites can only be accessed by having the administrator open up access to them. Even using a proxy would not work since traffic first goes through the monitoring server then out to the proxy.
If this is a site you need access to, I'd contact the admin and put in a request for access to the site.
If you're within a network and try connecting to computers on it with the WAN public IP, it simply won't work - you must use the network IP.
On an external Internet connection, it should connect fine to the public IP. If you have access to an external machine (remote desktop), or if you know of an FTP proxy, you can try it that way.
I also believe http://www.webftp.co.uk/ a web based FTP client would act as somewhat of a proxy, you could try that with the public IP and see how you go.