Problems closing port 135

  jake2 16:17 04 Sep 07
Locked

Shields up scan has revealed that port 135 open and suggested closing it.
I have followed the instructions here:

click here

both editing the registry AND in
Dcomcnfg.exe.

Yet shields up still shows it as being open.
Can anybody tell me why this would be?

This thread is now locked and can not be replied to.

Huawei P10 review

1995-2015: How technology has changed the world in 20 years

An overview: What leading creative agencies are doing to improve diversity

New iPad, iPhone SE & Red iPhone 7 on sale now