• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 731
  • Last Modified:

One-to-one Nat configuration in Sonicwall Pro 2040 Standard for Terminal Services

Good afternoon-

I'm trying to configure my Sonicwall Pro 2040 Standard for one-to-one NAT to my internal Server. I was provided an additional public IP address from my ISP. I believe I configured the settings on the Sonicwall correctly but I still cannot connect to my server via home using the Public IP Address in MSTSC (RDP).

Please assist if possible.

Thanks.
0
rbonds
Asked:
rbonds
  • 2
1 Solution
 
amatson78Sr. Security EngineerCommented:
There are two important things to remember when configuring. One is to setup the NAT, two is to setup the firewall access for the zone. After configuring the NAT and the firewall rule you should be able to access it. Have you checked the logs for your public IP when testing? Sounds like there may be something miss-configured, I would also run a Wireshark Capture on the box you are trying to RDP too and see if by chance the traffic is getting there but blocked by the host OS.

http://www.sonicwall.com/app/projects/file_downloader/document_lib.php?t=TN&id=57
http://help.mysonicwall.com/sw/eng/general/ui1/6600/Advanced/One_to_One_NAT.htm
0
 
Blue Street TechLast KnightCommented:
Hi rbonds,

Run the Public Server Wizard. It is setup as one of the options for Terminal Server. Select that and follow the onscreen guide. This will setup all the necessary configuration needed. It's located at the top right hand side of the GUI once you login to the SonicWALL.


Let me know how it goes!
0
 
rbondsAuthor Commented:
Thank you, It seems as though the host was blocking the connection due to the default gateway. I had to change the default gateway on the host to reflect the sonicwall internal IP Address.
0
 
amatson78Sr. Security EngineerCommented:
Glad to hear its all working now. And thank you for the points. ;)
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Simple Misconfiguration =Network Vulnerability

In this technical webinar, AlgoSec will present several examples of common misconfigurations; including a basic device change, business application connectivity changes, and data center migrations. Learn best practices to protect your business from attack.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now