Michael C
asked on
SonicWall NAT problem
We have a Sonicwall firewall and there are NAT working well.
Recently, we need to setup a new NAT (TCP: 19832) from external to our internal server. My setup is as below:
1. Copy other NAT rule, and allow the port, but no luck
2. telnet the port by internal network, it works
3. To setup NAT by tp-link, it works by telnet in external network
4. Change to another tcp port, not luck
I have double check the NAT and firewall rule, there is no hints on it.
Anyone has hints on it? Is there magic difference between TP-Link and Sonicwall NAT (port forwarding)?
I check on firewall, there is activity on hitting the NAT rule, but no traffic...
Recently, we need to setup a new NAT (TCP: 19832) from external to our internal server. My setup is as below:
1. Copy other NAT rule, and allow the port, but no luck
2. telnet the port by internal network, it works
3. To setup NAT by tp-link, it works by telnet in external network
4. Change to another tcp port, not luck
I have double check the NAT and firewall rule, there is no hints on it.
Anyone has hints on it? Is there magic difference between TP-Link and Sonicwall NAT (port forwarding)?
I check on firewall, there is activity on hitting the NAT rule, but no traffic...
masnrock
The easiest way to do it is to the Public Server Wizard. If you were to do it manually, you have to add entries in the NAT policies and the access policies.
Create the Service object at TCP: 19832.
Create the destination server as an Address Object.
Set up a Firewall Rule WAN ANY Service 19832 Inbound ALLOW.
Set up a NAT rule WAN ANY to Address Object internal server and ENABLE.
That should do it.
Create the destination server as an Address Object.
Set up a Firewall Rule WAN ANY Service 19832 Inbound ALLOW.
Set up a NAT rule WAN ANY to Address Object internal server and ENABLE.
That should do it.
ASKER
our fw is old version (boss dont want to replace), so dont have the wizard..
i have tried the rule already.. what i think the NAT different between TP-Link and Sonicwall... is it there sth about transparent NAT, destination NAT, source nat?
i am afraid tp link one is not transparent and default to be internal IP... that’s why it is successful
i have tried the rule already.. what i think the NAT different between TP-Link and Sonicwall... is it there sth about transparent NAT, destination NAT, source nat?
i am afraid tp link one is not transparent and default to be internal IP... that’s why it is successful
What model Sonicwall and which version of firmware?
ASKER
os is 5.x i remember... model is 200? around 4-5 years ago
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Hi Masnrock
it works ... billion thanks for you..
it makes me cannot sleep for two weeks and i can sleep tonight
many thanks
it works ... billion thanks for you..
it makes me cannot sleep for two weeks and i can sleep tonight
many thanks