This discussion has been locked.

You can no longer post new replies to this discussion. If you have a question you can start a new discussion

DCOM Error on DC - Unable to communicate with ASG 110/120

Since setting up an ASG 110/120 device and using the AD SSO section to add the ASG to the domain, I am receiving 8 DCOM errors every 30 mins in the System event log:

Log Name: System
Source: DCOM
Event ID: 10009
Level: Error
User: N/A
OpCode: Info

DCOM was unable to communicate with the computer asg.mydomain.local using any of the configured protocols.

The DC is a Windows Server 2008 R2.

I followed the manuals instructions:

1. Time Zones are the same.
2. The time is the same
3. Added ASG name to DNS
4. Created a request route for the domain pointing to the AD DNS.

Anyone have any ideas please [:)]

This thread was automatically locked due to age.

Parents

0 BAlfson over 13 years ago

I did look at the firewall log but there was no logs from my DC to the ASG. I had created a rule to allow all traffic from my DC to the internal eth0 of the ASG too.

If there's no traffic blocked between the ASG and your DC, then I can't think of anything in the ASG that can be changed to fix this or anything special about it that should be taken into account by your server. You might try deleting the ASG in AD and adding it again.

Cheers - Bob
Cancel
Vote Up 0 Vote Down

Cancel

Reply

0 BAlfson over 13 years ago

I did look at the firewall log but there was no logs from my DC to the ASG. I had created a rule to allow all traffic from my DC to the internal eth0 of the ASG too.

If there's no traffic blocked between the ASG and your DC, then I can't think of anything in the ASG that can be changed to fix this or anything special about it that should be taken into account by your server. You might try deleting the ASG in AD and adding it again.

Cheers - Bob
Cancel
Vote Up 0 Vote Down

Cancel

Children

No Data