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

Terminal Services thru Sonic Wall

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.
0
btmtech
Asked:
btmtech
  • 2
1 Solution
 
btmtechAuthor Commented:
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 192.168.1.111, 1596, LAN (admin) 192.168.1.1, 80, LAN Web (HTTP) 6
0
 
NJComputerNetworksCommented:
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 192.168.1.111

Can you change this rule to allow incoming TCP 3389 to 192.168.1.1 (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...
0
 
btmtechAuthor Commented:
Thanks for the hint.
These are the rules that I added:
4 Allow   All   Terminal Services   WAN   192.168.1.1 (LAN)            
6 Allow   All   Terminal Services   *   192.168.1.106 (LAN)        

0

Featured Post

Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

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