|
When I do a ping from the internal network via name,or IP it
fails to resolve. NSLOOKUP gives the correct address. If I ping from
outside or check mail (connect to a remote machine via terminal service
and come back in) it works fine via name, IP or Web mail. What I do not
understand is name resolution should be changed with one to one nat set to the
mail server. I think Todd has the right idea.
----- Original Message -----
Sent: Friday, April 12, 2002 3:45
PM
Subject: RE: [SonicWALL]- [IMail Forum]
Mail fails to connect through SonicWall from LAN
I
agree with Chris. Try pinging the IMail server from an internal
client. See if the DNS resolves to the public
address.
Todd
I thought the DMZ is for public IPs. According
to my manual
"Servers in the DMZ need unique, valid IP addresses in
the same subnet as the Sonicwall WAN IP address."
What does your
IMail log show and/or client error? Tried using the
IP?
Chris
At 03:04 PM 04/12/2002 -0500, you
wrote:
I have set up my iMail Server on a one to one
NAT (192.168.155.98) behinf my SonicWall DMZ. I can send and
receive mail from machines that have a public address but my
mail now fails on our LAN. Has anyone ever had this issue. I can
access secure web mail from a pub
Ports that are open are 25,
110 and 443 (or SSL Web Mail)
Rules for each
service:
Allow SMTP *
192.168.155.98 Enabled
Allow POP3
* 192.168.155.98 Enabled
Allow
SSL * 192.168.155.98
Enabled
Anything
missing?
|
