Quote:
| Originally Posted by obelix We are seeing this with SecureClient (NGX R60 Build 191) when LAN connected, though we are seeing a Reject, as opposed to a drop, on Rule 995 for epmap/135. This occurs immediately after an Accept from the same sourceAddr/port combination!
Thoughts anyone? |
We, too, have the exactly same issue. (SC, NGX R60 HFA1 Version: 019) Our support-team, too, is currently investigating this issue.
Obviously disabling any options ralated to DCE in SmarDefense does not help, because these options are only applied to the central gateway, but not to the SecureClient, aren't they?
The issue seems to be quite critical, because our Windows AD group policies are not able to getting deployed this way!
Isn't there any possibility to centrally disable certain SD-features for the SC?
***
Has anyone yet tried the solution from
MS AD replication across firewall ? Creating a service matching port 135 and allowing this service explicitly ? I'll try out tomorrow...