RE: [SonicWALL]- One to One NAT question.

[Dude, Curtis]

When this happened to me, I later found that I had my private and public address in the NAT table swapped. Oops. I hope that's all you did, because otherwise I can't think of anything that would stop it from working.   And I did try to get to that address on port 80 & 443. It didn't work.   -Curtis   -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Nick Goodman Sent: Friday, June 21, 2002 3:47 PM To: '[EMAIL PROTECTED]' Subject: [SonicWALL]- One to One NAT question. Ok Here is a weird one.   I had a machine that was 216.60.34.52 on the DMZ, was old winproxy server that I had during a switchover.  And it had a mapped port being used on it for Exchange OWA...Anyways, thank god it is all gone now, but another problem has arisen.   I removed that IP from the DMZ addresses, and now I added 216.60.34.52 as a one to one NAT with my internal IP of the exchange box.  And there is a rule that allows web to that IP from *.  But anytime I go to that 216.60.34.52 I just get a server not found, and I know one to one NAT is working because I am using another server with it for Windows 2000 VPN.   So basically, would the sonicwall be remembering the MAC or something of the old server that had the address previously?  Could that be my problem?  I know the web server works fine, I can use it all day long internally...Oh I have restarted and powered off and on the sonicwall too.     Hope that made sense I'm in a hurry as I type this....Any ideas?