Re: Remote Desktop weakness

lordergf · ‎01-16-2010

Sharing is not enabled, the Network Trust Level is "Protected." and Norton do not block this conection. One rule in firewall about Remote Desktop and case is closed. Is that so difficult?

dickevans · ‎04-08-2008

lordergf wrote:
Sharing is not enabled, the Network Trust Level is "Protected." and Norton do not block this conection. One rule in firewall about Remote Desktop and case is closed. Is that so difficult?

If a general rule to block remote desktop connections is included, what would have to be done to allow connections? Also, which case is more common - a user who will never need Norton customer support to connect to their computer to help them or users who have home networks and share things, including assistance with other users within the home?

I'm not positive but I have a very strong feeling that the law of unintended consequences will rule here and that block with cause more problems than it will solve.

On an individual level I'm sure that you can write a rule that will provide you with the feature you need.

Dick
Win7x64 SP1 current NIS V20

peterweb · ‎04-17-2008

hUstle wrote:
I support lordergf, because consumers should receive optimal protection by default. There are people who do not even know how to put password on the accounts will .. they spend money for your products ... think about them!

If they do not know how to password protect their account, do you really think they know how to use Remote Desktop?

Those that know how to set it up should be able to set up any necessary protection.

Things happen. Export/Backup your Identity Safe data.

SendOfJive · ‎02-07-2009

lordergf wrote:
One rule in firewall about Remote Desktop and case is closed. Is that so difficult?

If Remote Desktop is disabled, any incoming RDP traffic will be blocked by Norton automatically - no special rule needed. If Remote Desktop is enabled, the PC will need to have an RDP port open to listen, so I am not sure what a general firewall rule would look like - you can't, by default, allow some but not others, because the firewall can't possibly know what you want to allow or block. Obviously, it would be necessary for the user to create or modify a rule to specify who is and who is not allowed - not a job for the unsophisticated user.. As has been mentioned, the recommended safeguard when allowing incoming RDP traffic, is to use a strong, secure password to prevent unauthorized access.

hUstle · ‎03-23-2012

То peterweb

05-08-2012 04:03 PM

This is what I mean. When you do not know what is the Remote Access, Norton wall will warn connecting and everyone will decide, the user will have time to read on the Internet what it is. And when there is no question it will be late!

P.S: I will not write more on this topic, its no sense. I will stop to use Norton, I do not like your policy.

And let all user take own decision. Everyone decided.

Regards !

SendOfJive · ‎02-07-2009

Hi hUstle,

If you want the Norton firewall to provide warnings and permit you to make the "allow/deny" decisions, you can certainly do that, at least for outbound traffic, by turning off Automatic Program Control and enabling Advanced Events Monitoring. The firewall will block everything until you decide to allow it. You will be alerted every time a program, such as Remote Assistance, tries to connect out or is "attempting to access the Internet using one or more unrecognized modules" or "attempting to activate a controlled COM object." You will get to do the research and decide if it should be permitted or denied. Smart firewalls were developed to spare users, especially novices who are prone to make exactly the wrong choices, from having to go through all this. If you are serious about wanting to go back to this method, I would encourage you to try running the firewall in AEM mode for awhile.