cssunetadmin
asked on
SonicWall NAT
We have natt'ed out a machine using a SonicWall NSA 3500. We need the outside world to see the natt'ed outside address but it sees the public address of the SonicWall WAN port. Other machines natt'ed out in our network show their external address. What are we missing?
MikeKane
Do you have a static one to one nat, a port forward? What is different between the other machines and this machine. Do you NAT outbound using the Sonic wall interface address?
please provide more information, how this machine is connect into the NSA3500? LAN, DMZ? are you using 1 of the additional public IP to this machine which is routed via main gateway (nsa3500) WAN IP? if it is not directly exposed to outside world (behind firewall), please provide more info on your network connection.
How did you setup your NAT policy on the NSA3500?
How did you setup your NAT policy on the NSA3500?
ASKER
We do one-to-one natting and the machine in question is on the LAN interface. Several machines have outside IP addresses for web services, e-mail, etc. We use the wizard when creating the NAT. It has worked fine in the past and seems to have created the required rules this time. In thinking about difference, the only thing different is that the machine in question is a virtual machine. This is our first one so I am wondering if it is possible to NAT out a virtual machine so that the virtual machines external IP address is seen.
The sonicwall ( or any firewall for that matter) doesn't care if its a virtual machine vs. a physical machine. It doesn't matter (so long as the virtual machine gets its own internal IP on the internal LAN).
Do you have 2 NATs going to the same machine perhaps?
From the virtual, visit www.canyouseeme.org and check the IP the world sees and test the inbound port as well.
What IP do you see? is it the interface ip of the firewall?
If you assign this static to another host, does the 2nd host exhibit the same behavior?
Do you have 2 NATs going to the same machine perhaps?
From the virtual, visit www.canyouseeme.org and check the IP the world sees and test the inbound port as well.
What IP do you see? is it the interface ip of the firewall?
If you assign this static to another host, does the 2nd host exhibit the same behavior?
ASKER
Yes, when we check the ipaddress from the machine, it shows the public address of the firewall. If I move the IP address to a different machine same thing and if I assign a different external to this machine, same thing.
So If I understood, if you take a working 1 to 1 nat where the working machine would display the correct external IP ( using canyouseeme.org) and now assign the internal IP to the questionable box, the IP that did translate correctly is now showing a different IP at conyouseeme? That makes no sense whatsoever.
Does the questionable box have multiple IP's assigned to the same NIC? Does it have multiple NICs? Does it have a wireless and wired connection at the same time?
Make sure you run a clear xlate and show xlate durign these tests as well.
Does the questionable box have multiple IP's assigned to the same NIC? Does it have multiple NICs? Does it have a wireless and wired connection at the same time?
Make sure you run a clear xlate and show xlate durign these tests as well.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.