Exchange Server Forums
Forums |
Register |
Login |
My Profile |
Inbox |
RSS
|
My Subscription |
My Forums |
Address Book |
Member List |
Search |
FAQ |
Ticket List |
Log Out
RE: MX Records
|
Users viewing this topic:
none
|
Logged in as: Guest
|
Login | |
|
Limited time MSExchange.org offer! -- 1.Sep.2008 1:00:00 PM
|
|
TechGenix and SolarWinds have partnered to provide free copies of SolarWinds Exchange Monitor to all visitors who join the MSExchange.org Forums. SolarWinds Exchange Monitor is a handy desktop dashboard that continuously monitors Microsoft Exchange to deliver real-time insight into Exchange services, mail queue sizes, and host server health. Learn more about Exchange Monitor and the free offer!
|
RE: MX Records - 22.Mar.2006 7:37:39 PM
|
|
|
lhenriquez
Posts: 15
Joined: 14.Mar.2006
Status: offline
|
quote:
ORIGINAL: Xguru Issue is with the firewall or anything sitting before Exchange.... As blackman suggested you may want to recreate the NAT external ip >> internal IP forward to Exchange IP. Port NAT any to any XGURU Well, the problem definitively does not reside in the firewall, that's for sure. Let me give u this information about our internet's configuration: ADSL Modem [Alcatel Speedtouch 510 (Working in Bridge mode, or DHCP Spoofing?) ]==> Router/Firewall NEtgear FVS318 (this is who actually has my external IP, hence does the NAT work) ==> LAN Again, i already recreated the NAT rule, I even removed the Firewall from my configuration (and assigned my external IP to my exchange server), but it did not work Either! So, should I open (forward?) port 25 in my ADSL Modem?...considering it is working in a Bridge Mode, i thought this would not be necessary. How about my ISP? (still not gettin' answer from them), maybe they're blocking incoming SMTP traffic, don't u guys think?
|
|
|
|
RE: MX Records - 22.Mar.2006 8:24:20 PM
|
|
|
Xguru
Posts: 287
Joined: 14.Feb.2006
Status: offline
|
Your questions at this point is right..... You have to forward port also on the modem... You suspecting the ISP blocking port 25 traffic may be true... Are we able to telnet localhost 25 yeald banner when executed on the exchange server? XGURU
|
|
|
|
RE: MX Records - 22.Mar.2006 8:48:07 PM
|
|
|
Xguru
Posts: 287
Joined: 14.Feb.2006
Status: offline
|
Good enuf.... Telnet localhost 25 would mean sitting on the exhcange box and trying a telnet. Are you able to drop and email to yourself by telnetting to exchange from a client box? test following to check the same; telnet IPofexchange 25 ehlo mail from: admin@msexchange.org rcpt to: yourname@yourdomain.com data test message . (add this period to end telnet conversation) check your inbox and if you have received the email then do not look further and troubleshoot your modem or firewall if any. XGURU
|
|
|
|
RE: MX Records - 22.Mar.2006 9:01:04 PM
|
|
|
Xguru
Posts: 287
Joined: 14.Feb.2006
Status: offline
|
Perfect brother.... I am sure you will nail the issue down.. keep looking and you will find the problem... its is somewhere on the modem, switch, router or firewall before firewall preventing port 25 traffic. XGURU
|
|
|
|
RE: MX Records - 22.Mar.2006 10:06:17 PM
|
|
|
de.blackman
Posts: 1436
Joined: 4.Apr.2005
From: Toronto, Canada
Status: offline
|
You mentioned you are able to successfully telnet locally on the server and in ur network but when i tried on port 25, connection cannot be made. Port 80 telnets fine though, so that definitely tells me something is blocking port 25 access to your server.
_____________________________
De BlackMan List Moderator "Did you backup your Information Store Today?!"
|
|
|
|
RE: MX Records - 23.Mar.2006 2:25:55 PM
|
|
|
lhenriquez
Posts: 15
Joined: 14.Mar.2006
Status: offline
|
quote:
ORIGINAL: de.blackman You mentioned you are able to successfully telnet locally on the server and in ur network but when i tried on port 25, connection cannot be made. Port 80 telnets fine though, so that definitely tells me something is blocking port 25 access to your server. My mistake: It seems to me that my ISP is allowing incoming SMTP traffic ONLY for some IP's. My IP is in the range 200.42.x.x. I could access my server whenever i tried to connect from a similar IP, otherwise it was not possible. Thanks guys, I think it's clear now that there's an ISP's problem which I need to deal with.
|
|
|
|
New Messages |
No New Messages |
Hot Topic w/ New Messages |
Hot Topic w/o New Messages |
Locked w/ New Messages |
Locked w/o New Messages |
|
Post New Thread
Reply to Message
Post New Poll
Submit Vote
Delete My Own Post
Delete My Own Thread
Rate Posts |
|