How do I Block Remote Desktop via the Firewall?

I'm using a Pix 515E software 6.2(3).  I have setup an XP Machine in my office and connected through the Firewall to my Home Computer Windows 2003 Server using Remote logging of this activity is present.  My fear is users will be able to do this and surf the web on their home computer by-passing my web inspector monitor.  I have tried blocking ports GT 1024 with no I need to block a certain port or protocol comm???   Any Suggestions!
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

blc92562Author Commented:

THanks for the Link...This is the first thing I tried, I had the Office workstation connected when I applied the ACL to block 3389 and it locked the Office Computer.... I shut down RemoteDesktop and restarted... connected to the Home Computer with no problems.

After aplling the ACl I ran the command clear xlate and clear Local-host.  I will try this again and probably just save to flash and reboot the pix to insure the acl takes effect.

Any ideas why no logging is happening with this remote desktop?  The Pix logs all the internet sites but not the remote desktop connections.
How about just disabling the remote desktop service?
Redefine Your Security with AI & Machine Learning

The implications of AI and machine learning in cyber security are massive and constantly growing, creating both efficiencies and new challenges across the board. Check out our on-demand webinar to learn more about how AI can help your organization!

blc92562Author Commented:
That’s definitely an option when it’s all said and done I will probably block the ports and create a Group Policy to disable the functionality.
Pete LongTechnical ConsultantCommented:
Yup 3389 is the usuall port to block check you pix config for an inbound deny for 3389 from any to any, you can also apply an outbound deny as well if you are really paranoid.

It would seem you have ports open anyway? this is not good! the bottom of your access list should have a "deny any any"
to lock all the non permitted ports down.

Pete LongTechnical ConsultantCommented:
You probably won't get away with setting up an inbound block because the traffic in question has the ack bit set and will be allowed back in by NAT.

Instead, block the inside connection to 3389 for all internal addresses.

I think you would add something like this:

access-list inside_access_in deny tcp any any eq 3389
access-list inside_access_in permit ip any any
access-group inside_access_in in interface inside

Good luck!

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
blc92562Author Commented:

I have been told by TAC that all outside ports are closed by default and all
Inside ports are open by default.

1. This is what I have applied to inside Interface

access-list acl_inside deny tcp any any eq 3389
access-list acl_inside deny tcp any any eq 135
access-list acl_inside deny udp any any eq 135
access-list acl_inside deny udp any any eq tftp
access-list acl_inside deny tcp any any eq 137
access-list acl_inside deny udp any any eq netbios-ns
access-list acl_inside deny tcp any any eq 138
access-list acl_inside deny udp any any eq netbios-dgm
access-list acl_inside deny tcp any any eq netbios-ssn
access-list acl_inside deny udp any any eq 139
access-list acl_inside deny tcp any any eq 445
access-list acl_inside deny tcp any any eq 593
access-list acl_inside permit ip any any

access-group acl_inside in interface inside

2. Would it be safer to close ports to inside Interface and only open the ones I need?  I believe if I add one permit statement the Pix automatically denies all traffic i.e. automatically adds a access-list acl_inside deny ip any any

access-list acl_inside permit tcp any any eq 80
access-list acl_inside permit tcp any any eq 21
access-list acl_inside permit tcp any any eq 53
access-group acl_inside in interface inside

What ports should automatically be set to open?
It is safer, but can become a bit of a management nightmare, specifically because you have to figure out what ports to keep open.  

If I was tempted to do it, I would include 25, (or 110), 20 (FTP data channel), 443, and any other port that your inside applications require.  Even then, you'll have trouble downloading from some sites.  

I would also include the 'access-list acl_inside deny ip any any' line to the config.  If you do, it will help you out a lot when troubleshooting the ACL.  With it, while you are troubleshooting, you can see how often packets are hitting the deny line and are being blocked, without it, you only see the permit lines and how often they get hit.

But to be honest, I wouldn't do it this way.  I would go with the permit all and block as per the list you provided.  If you are concerned about people doing remote control of their machines at home, you aren't going to be able to stop them this way.  At best, you will stop the less determined.  Most of the remote takeover packages can be configured as to what port to use.  In this case, a home user could just change the port from default to port 80, and off they go.  

Good luck!
blc92562Author Commented:
Thanks for the assistance!!!
as long as you allow Remote DeskTop and allow at least one port open, you're unsafe. Dot.
Disable Remote DeskTop access, or forget thinking about security.
If you have experianced users, they'll find a way to use Remote DeskTop on other than default, but open ports.
If you have unexperianced users, the risk might be less, but keep in mind that these unexperianced users are subject to any kind of malware, which then becomes your problem ('cause it's programmed by experianced users, usually;-)
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Software Firewalls

From novice to tech pro — start learning today.