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

Hi, npharvey, and welcome to the User BB!

This sounds like a networking issue outside the Astaro. Is it possible that the WinServer doesn't have a route to the ASG? You might want to ask your reseller to submit a support request to Astaro.

Cheers - Bob
Cancel
Vote Up 0 Vote Down

Cancel
0 npharveyuk over 13 years ago in reply to BAlfson

Hi, npharvey, and welcome to the User BB!

This sounds like a networking issue outside the Astaro. Is it possible that the WinServer doesn't have a route to the ASG? You might want to ask your reseller to submit a support request to Astaro.

Cheers - Bob

Hi Bob

Thanks for replying.

The ASG name is in my Active Directory structure ok, I presume this means that communication is working ok. I also added the name to DNS and the name is resolved ok. The default gateway of the DC is to the ASG.

I presuming there is a protocol issues with DCOM to the ASG going from the error. DCOM is fine with all other machines (XP based).

Anything anyone can think of I could try DCOM wise?

Kind Regards

Neil Harvey
Cancel
Vote Up 0 Vote Down

Cancel

Reply

0 npharveyuk over 13 years ago in reply to BAlfson

Hi, npharvey, and welcome to the User BB!

This sounds like a networking issue outside the Astaro. Is it possible that the WinServer doesn't have a route to the ASG? You might want to ask your reseller to submit a support request to Astaro.

Cheers - Bob

Hi Bob

Thanks for replying.

The ASG name is in my Active Directory structure ok, I presume this means that communication is working ok. I also added the name to DNS and the name is resolved ok. The default gateway of the DC is to the ASG.

I presuming there is a protocol issues with DCOM to the ASG going from the error. DCOM is fine with all other machines (XP based).

Anything anyone can think of I could try DCOM wise?

Kind Regards

Neil Harvey
Cancel
Vote Up 0 Vote Down

Cancel

Children

No Data