Solved

Configuring Netscreen/Juniper Firewall to allow remote desktop access to server

Posted on 2006-11-15
7
19,139 Views
Last Modified: 2013-11-21
Hi,

I need help configuring a netscreen/Juniper NS5GT firewall so that someone from outside can connect to a server on our LAN (IP address is 10.10.10.3) through Windows Remote Desktop.

Here is what I have tried and is NOT working.

I created a new custom service object named "MSTSC (desktop sharing)" with parameters of:
TCP src port: 0-65535, dst port: 3389-3389
UDP src port: 0-65535, dst port: 3389-3389

Then I created a new policy from Untrust to Trust with the following parameters:
Source Address: any
Destination address: any
Service: MSTSC (desktop sharing)
Application: (ignore)
Action: permit
Antivirus profile: none
Tunnel-VPN: none
Tunnel-L2TP: none

And under "Advanced"
NAT-Destination Translation is checked with Translate to IP set to 10.10.10.3 (map to port is unchecked)
Authetication is unchecked
Traffic shaping is unchecked

I have two other policies from Untrust to Trust:  One is to allow pinging (not sure it is doing anything) and one that was used to set up our VPN (which is working).  Both of those policies come before this new one I created for desktop sharing.

I only have one policy from Trust to Untrust which permits anything from any address to any address.

From outside the company LAN (e.g., at home), I try to connect through Remote Desktop sharing (from Win XP Pro) to the public IP address we all have when we are on the LAN (i.e., what www.showmyIP.com reports when I'm at the office), but the Remote Desktop App on my computer doesn't seem to be able to get a response from the server (don't remember the exact message, but it seems to time out)

Any suggestions?

I'm also planning to modify the policy to specify the From IP address for better security once I get it working, but let me know if you have any suggestions related to that or other issues of security.

Thanks!
Tim
0
Comment
Question by:timwhunt
7 Comments
 
LVL 25

Expert Comment

by:mikeleebrla
ID: 17948645
1.  i wouldn't open this up since it is a rather large security hole. I would setup a VPN and have external users VPN in and THEN access remote desktop
2.  but if you want to use remote desktop and have external users directly remote in, then you will need to do one of two things
a) setup port forwarding so any request for port 3389 gets redirected to the LAN ip of 10.10.10.3
b. setup a static mapping of another external public IP (if you have one) that is mapped to 10.10.10.3
0
 

Author Comment

by:timwhunt
ID: 17948836
Thanks for the quick comments.  For employees we have VPN set up, but this is our phone PBX vendor who wants to remotely tweak configs just on our dedicated computer for the phone system.  It doesn't sound like they have the same VPN client, but it is very possible I could give them the parameters that they could use with their client.  But I thought this would be easier to set up (less/no configuration on their side) and I would think restricting this to their IP address would make it pretty secure.

I thought the configuration I described above would do what you call 2a, but please explain if and how it is different.

Thanks again,
Tim
0
 

Author Comment

by:timwhunt
ID: 18147201
Any other suggestions or thoughts?
0
The Eight Noble Truths of Backup and Recovery

How can IT departments tackle the challenges of a Big Data world? This white paper provides a roadmap to success and helps companies ensure that all their data is safe and secure, no matter if it resides on-premise with physical or virtual machines or in the cloud.

 
LVL 9

Expert Comment

by:David Piniella
ID: 19453849
set up a VIP in your interfaces for that particular client machine

it should be a CLI command like
set interface untrust vip untrust 3389 "RDP" 10.10.10.1

and then change the policy -- it should be from untrust to untrust (from outside your network to the untrust interface of your netscreen) and should look something like
set pol id 5 from "Untrust" to "Untrust" "Any" "VIP(untrust)" "3389" permit log

(the policy id "5" is just whatever policy # you have already...I used 5 as an example because I'm guessing you have 5 policies already)

Once that is done, have the vendor (or whoever) RDP to the FIREWALL's untrust address; it will do the PAT magic for you and then it'll work.
0
 
LVL 5

Accepted Solution

by:
ccreamer_22 earned 250 total points
ID: 20082325
If you have another public ip address your not using, Creating a MIP would work and just allow destination 3389 tcp/udp through. Also make sure that you can RDP to the server from inside your network so that you know that Windows firewall or allow RDP is not interfering. Making a MIP is found on http://kb.juniper.net/CUSTOMERSERVICE/index?page=kbdetail&record_id=0244022611e8310108012c3c1906630
0
 
LVL 9

Expert Comment

by:David Piniella
ID: 20082762
the way you describe it being setup, the NAT is only outbound, not inbound. For the inbound translation to be set (so that it works as you seem to expect it in situation 2a above -- this is better known as inbound PAT, not NAT btw), you have to setup a VIP or MIP as detailed above by mikeleebrla, myself or ccreamer_22.
0
 

Expert Comment

by:explorer648
ID: 24425071
I do not understand can you elebrate telling me how to do this using the web interface
0

Featured Post

Simplifying Server Workload Migrations

This use case outlines the migration challenges that organizations face and how the Acronis AnyData Engine supports physical-to-physical (P2P), physical-to-virtual (P2V), virtual to physical (V2P), and cross-virtual (V2V) migration scenarios to address these challenges.

Question has a verified solution.

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

Suggested Solutions

Issue: One Windows 2008 R2 64bit server on the network unable to connect to a buffalo Device (Linkstation) with firmware version 1.56. There are a total of four servers on the network this being one of them. Troubleshooting Steps: Connect via h…
Most of the applications these days are on Cloud. Cloud is ubiquitous with many service providers in the market. Since it has many benefits such as cost reduction, software updates, remote access, disaster recovery and much more.
Viewers will learn how to connect to a wireless network using the network security key. They will also learn how to access the IP address and DNS server for connections that must be done manually. After setting up a router, find the network security…
Internet Business Fax to Email Made Easy - With  eFax Corporate (http://www.enterprise.efax.com), you'll receive a dedicated online fax number, which is used the same way as a typical analog fax number. You'll receive secure faxes in your email, f…

778 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