Discussion Locked

RDP w/ SOHO3 SonicWall

0 helpful
3 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
I'm having trouble creating an RDP session to my 2003 Server. I think the firewall might be the problem -has anyone configured a SOHO3 Firewall to allow Terminal Services and RDP? Any thoughts would be appreciated.

3 replies

by jamwel

It's pretty straightforward --

First, add a custom service for RDP:

Click the Access menu, then Add Service
Under Custom Service, fill in:

Name - RDP
Port Range - 3389 to 3389
Protocol - TCP (6)

Click Rules, Add New Rule
Choose "allow"
Service=RDP
Source: configure this to meet your security requirements. If you will only be coming from one IP or a range, select WAN and enter the source IPs. If you want to allow RDP traffic from anywhere on the internet, Leave it as From:* To:8.

Destination: Choose LAN and enter the IP address of the server you want to RDP to.

These are basic instructions for a normal installation with one WAN IP. If you have multiple IPs secured by your SOHO3, you will have to worry about static NAT config.

by roguebear.software

James, thanks for the info -I configured the SOHO3 like you said -but still can't connect. I can connect to the user using a workstation and the private/local IP address -so I know that Terminal Services/RDP is running on the server. Is it possible that our broadband provider is blocking that type of traffic? -can you think of anything else to try?

Thanks again

by wwojkowski

We have one "central" SOHO3 and 4 remote sites with various models of Sonicwalls and all form VPN tunnels with the central hub. All 4 of our remote sites utilize RDP and older Terminal Services clients to connect with a Windows 2000 server here running Terminal Services. Are you using VPN's between the local ad remote Sonicwalls?

This discussion is closed to new replies.