Hot!FSAE collectoragent.exe DCOM errors Event ID 10028

Author
Cem KIZIL
New Member
  • Total Posts : 3
  • Scores: 0
  • Reward points: 0
  • Joined: 2019/05/02 02:36:25
  • Status: offline
2019/05/02 02:43:24 (permalink)
0

FSAE collectoragent.exe DCOM errors Event ID 10028

Hello,
 
We installed FSSO Agent 6.0.4 on Windows Server 2016 Active Directory DC and we are using Fortigate 300D 6.0.4 Firmware. 
 
We have 2 issue first one
 
1. My some VLAN have problem about fsso. They cant access internet via their AD User. When i check the logs they are going the internet with IP Address. But some VLAN working excellent.
 
2. On my AD DC i see a lot of really very much error 
"DCOM was unable to communicate with the computer X.X.X.X using any of the configured protocols; requested by PID     1be4 (C:\Program Files (x86)\Fortinet\FSAE\collectoragent.exe)."
 
Do you have any idea?
 
Thank you guys.
post edited by Cem KIZIL - 2019/05/02 03:17:03
#1

2 Replies Related Threads

    xsilver_FTNT
    Expert Member
    • Total Posts : 429
    • Scores: 91
    • Reward points: 0
    • Joined: 2015/02/02 03:22:58
    • Status: offline
    Re: FSAE collectoragent.exe DCOM errors Event ID 10028 2019/05/02 04:22:59 (permalink)
    0
    1. for those non-working VLAN there might be simple IP based no-identity policy allowing traffic.
    2. workstation check is probably enabled on Collector Agent and that collector is unable to connect to workstations through use of  tcp.445 .. tcp.135 + tcp.139 + udp.137 (as fallback ports/methods).

    Kind Regards,
    Tomas
    #2
    Cem KIZIL
    New Member
    • Total Posts : 3
    • Scores: 0
    • Reward points: 0
    • Joined: 2019/05/02 02:36:25
    • Status: offline
    Re: FSAE collectoragent.exe DCOM errors Event ID 10028 2019/05/02 07:30:13 (permalink)
    0
    1. I tried source "all" in this policy.
    2. I checked client to dc - dc to client tcp 445 + tcp 135 + tcp 139 + udp 137 They can access these ports.
    #3
    Jump to:
    © 2019 APG vNext Commercial Version 5.5