Jump to content

hauke81

Members
  • Posts

    2
  • Joined

  • Last visited

About hauke81

  • Rank
    Newbie
    Newbie

Profile Information

  • Location
    Germany
  1. Yes, its Eset Endpoint Security, sorry! And thanks!! The troubleshooting wizard showed me, that I forgot to let raserver.exe communicate through the fw. Problem solved
  2. Hello, we are using the Windows 7 built-in Remote Assistance for Remote Support in our company. Since we released Eset Internet Security with the Eset Firewall, tthe MS Remote Assistance doesnt work anymore. I tried to configure the Eset Personal Firewall in the Eset Remote Administrator to fit our needs, but no success. The Firewall Filtermode is "Automatic". I specified some rules to let all MSRA traffic through: Protocol: upd AND tcp any profile Action: allow both directions Local Ports: 135, 3389, 1000-65535 Remote Ports: 135, 3389, 1000-65535 Application: C:\Windows\System32\msra.exe; C:\Windows\SysWOW64\msra.exe; C:\Windows\System32\svchost.exe; C:\Windows\SysWOW64\svchost.exe A Wireshark analysis tells me that while remote assistance initiation there is a SYN from me to remote (port 18090 -> 53223) which is usually (without Eset Firewall) answered by a SYN ACK from remote to me (port 53223 -> 18090), but with active Eset FW the SYN ACK answer is not passed through to me (or the initial SYN is not passed through to the remote pc so he doesnt answer). Help anyone? Hauke
×
×
  • Create New...