Terminal Services thru Sonic Wall

Posted on 2005-03-23
Medium Priority
Last Modified: 2008-01-09
I am trying to use Remote Desktop to access a 2003 Server thru a Sonic Wall Tele3.  I have opened up Terminal Services port 3389 for TCP and UDP traffic and am routing it to  the internal address of the server (192.168.x.x).

I can Remote in directly to the server from within the network without a problem.  However, when I try to go to the address that is assigned to the Sonic Wall, it immediately comes back with the message "The client could not connect to the remote computer".  The address can be pinged, so it appears to be a configuration with the sonic wall.

The Sonic Wall is set up to accept VPN connections.  I don't think that should be a problem however.

Any suugestions would be appreciated.
Question by:btmtech
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 2

Author Comment

ID: 13615588
Additional Note: This appears in the Sonic Wall log:
Time                              Message                               Source                    Destination                            Notes             Rule  
 03/23/2005 14:21:03.336 Web access request dropped, 1596, LAN (admin), 80, LAN Web (HTTP) 6
LVL 33

Accepted Solution

NJComputerNetworks earned 2000 total points
ID: 13615719
Im not 100% on this...

Your problem is most likely with the Sonic Wall (this problem has nothing to do with Windows 2003).

"I have opened up Terminal Services port 3389 for TCP and UDP traffic and am routing it to  the internal address of the server (192.168.x.x)"

I think you currently have a rule that says allow incoming TCP 3389 traffic to

Can you change this rule to allow incoming TCP 3389 to (the router IP) instead.

I've come across this before, where I was trying to open ports using a sonicwall directly to the internal NATTED IP address.  ... but it never worked.  I then learned I had to open ports to the inside LAN address of the sonicwall.  Then things started working for me.

-just a hunch here...

Author Comment

ID: 13617409
Thanks for the hint.
These are the rules that I added:
4 Allow   All   Terminal Services   WAN (LAN)            
6 Allow   All   Terminal Services   * (LAN)        


Featured Post

On Demand Webinar: Networking for the Cloud Era

Did you know SD-WANs can improve network connectivity? Check out this webinar to learn how an SD-WAN simplified, one-click tool can help you migrate and manage data in the cloud.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

by Batuhan Cetin In this article I will be guiding through the process of removing a failed DC metadata from Active Directory (hereafter, AD) using the ntdsutil tool in a Windows Server 2003 environment. These steps are not necessary in a Win…
Numerous times I have been asked this questions that what is it that makes my machine log on so slow, there have been cases where computers took 23 minute exactly after taking password and getting to the desktop. Interesting thing was the fact th…
Do you want to know how to make a graph with Microsoft Access? First, create a query with the data for the chart. Then make a blank form and add a chart control. This video also shows how to change what data is displayed on the graph as well as form…
In this video, Percona Solution Engineer Rick Golba discuss how (and why) you implement high availability in a database environment. To discuss how Percona Consulting can help with your design and architecture needs for your database and infrastr…
Suggested Courses

777 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question