Ray/Charles,
I was afraid you'd both still point to the TCP/IP settings of the Exchange
box as the cause for the failure. I had thought that scanning a range of
ports was to check if it was open. But it looks like my assumption was
wrong. It checks for responses and obviously the scanner isn't getting a
proper response from port 25. What layer does the scanning work on? Layer 3
or higher (especially the application layer?) of the OSDI model?
Since this Exchange box is active, I cannot change the IP settings until
after hours. I also would need to change the MX record settings on our
external DNS server. I wonder if there's a neat trick one can do to ensure
no loss of email during this phase? For example, I could create a new MX
record for the Dachstein router leaving the original MX record in place but
assigning a different priority to the new MX record. When external mail
server checks for MX records, they would attempt to contact our mail server
with the first MX setting and failing that, check the next MX record and
find the mail server active at that MX record. Does this make sense? Is this
do-able? Should the MX record contain the name of the router port-forwarding
the mail to the Exchange box instead the name of the Exchange box?
Thanks for all of your help!
~Doug
> I agree with Ray that the place to look now is your Exchange
> machine's
> network configuration. Please understand that just because
> GRC reports
> your port 25 as "stealth" doesn't mean the packets are being
> firewalled.
> What it means is that the GRC system sent out a TCP packet
> to port 25
> at your IP and didn't get a response back. From the firewall
> information it looks like the packets are passing through
> your Dachstein
> firewall, which means either you've got port-forwarding setup to the
> wrong IP, the exchange server isn't really running, or the exchange
> server is incorrectly sending back the reply packets (ie
> sending them to
> the proxy-server instead of the Dachstein router).
>
> Make sure the exchange server is using Dachstein as it's default
> gateway, and I think everything will begin working. If you
> continue to
> have problems, post the network confiuration ("ipconfig /all"
> and "route
> print") from the Exchange box for debugging.
>
> --
> Charles Steinkuehler
> [EMAIL PROTECTED]
>
>
-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com
------------------------------------------------------------------------
leaf-user mailing list: [EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/leaf-user
SR FAQ: http://leaf-project.org/pub/doc/docmanager/docid_1891.html
