Remote Desktop (RMD)

[ImpactMaster]

Hi there,

I have deployed the untangle server in my network, i try to reatch my sbs server with remote desktop. No response...

Can anyone tell me how to set-up the untangle server to accept remote desktop.

I'm running Build: 6.2.0

Thx ahead for you help.

[WebFooL]

Hi and Welcome to the Forum,

Do you want a simple Portforward on a External ip to your SBS server? (for RDP)
In that case:

Step 1:
In Untangles WebGui.
Go to: Config>Netwokring
Then to: Portforwards

Step 2:
add A portforward rule.
Hit the "add" button.
Make sure that "Enable" is checkt.
In the "Description" field enter "RDP To SBS server"
In the "Destination Port" field enter "3389" (standard RDP port)
Let the "Destination Local" be.
If i remeber right RDP is only a TCP base application but check UDP As well.
In the "New Destination" Field enter your SBS servers local IP.
Now hit Save.

All done.

If you have the Firewall Application you need to add a pass rule for port 3389 to your SBS server.

Good luck

[ImpactMaster]

Hi WebFool,

Thanks for your warm welcome! and thx for your response!

I fixed it another way... Because the port forward didn't work for web access, so i had to modifie some settings, can you coliform if i did it right?

Configuration > Administration > Enable External Quarantine Viewing.
External HTTPS port: 443 to [number]

----

Configuration > Networking > Port Forwards
add [Remote Desktop}
Source Interface [External]
Destination Port [3389]
Destined Local
Protocol [TCP]

New Destination: [SBS IP]
New Port (optional) []

---
Configuration > Networking > Port Forwards
Add [ssl]
Source Interface [External]
Destination Port [443] (that is the port Untangle claimed]
Destined Local
Protocol [TCP]

New Destination: [SBS IP]
New Port (optional) []

---
Configuration > Networking > Port Forwards
Add [Forward web traffic to an internal web server at [SBS IP]]
Destination Port [80]
Protocol [TCP]
Source Interface [External]
Destined Local


New Destination: [SBS IP]
New Port (optional) []

---

Thx for your response!

[WebFooL]

Hi,
It looks correkt.
You moved the Untangle Webadmin from port 443 to something else so now you can use https://untangleexternalip/tsweb .

If you have any other question let us know :P

[ImpactMaster]

Hi,

I don't get ftp to work, i have made to rules one for port 20 and one for 21...

I hop that you can help me out!

Thx A head!

[ImpactMaster]

Also the connection to exchange with a phone doesn't work... do i have to make a port forward for that?

[WebFooL]

Hi,

read this post:
http://forums.untangle.com/firewall/...p-example.html

can you now access https://Untangle_external_ip/exchange ?

[JMC]

Hello

Had the same problem today with my SBS 2008 system, Terminal Services where blocked and RWW access gave a 50331656 ERROR. I have just set a "no rack" policy in the default rack, allowing protocol 3389 to go through the virtual UT (TCP and UDP).

All remote access are working now... no need for port forwarding in my case.

(Untangle 7.1 Beta 2 32bits, Router(DFL210)-> Untangle(Virtual bridge) -> Internal Virtual switch -> SBS 2008 and Main Switch)

[Joesappy]

This seems a bit illusive... if 3389 is forwarded to the SBS server and I wish to connect to a workstation via Remote Web Workplace (RWW), is the SBS server then going to then continue the forwarding process to the workstation? Or do I need to forward additional ports and then modify the receiving port in the registry of the workstation?

Thanks,

Joe

Originally Posted by JMC

Hello

Had the same problem today with my SBS 2008 system, Terminal Services where blocked and RWW access gave a 50331656 ERROR. I have just set a "no rack" policy in the default rack, allowing protocol 3389 to go through the virtual UT (TCP and UDP).

All remote access are working now... no need for port forwarding in my case.

(Untangle 7.1 Beta 2 32bits, Router(DFL210)-> Untangle(Virtual bridge) -> Internal Virtual switch -> SBS 2008 and Main Switch)

[mdh]

Use other ports (let's say 3390) on your call from the outside, and port forward requests to 3390 on to the local machine on its normal port (3389). Do that as many times as are needed for different machines. You start dicking around with registry, and it returns the favor ten-fold.