Usually a good starting point is to start checking the relevant logs on the relevant replication server ... and see what errors it's run into (say "I ran out of disk space") and such.
Other than that, this should help -- Troubleshooting Replication .
Sorry but Could you tell what log files i have to check please ?
Thank you in advance
*fixes link to actual Content Replication article(s) ...*
- Issue: Content Replication fails to replicate some files (gives an example of the log - the log you usually want to look at is the vulscan.log IIRC)
- How to use Ivanti EPM Content Replication
- How To: Enable XTrace Diagnostic Logging for the LANDESK Core and Clients (how to enable additional logging detail)
- About the Ivanti EPM Content Replication Process
Sorry - the thing I originally linked related to HEAT stuff, not relevant for EPM replication.
So this should help better now .
OK - so it's unable to talk to the Core / the Core's WWW-service.
Double-check / cross-check against the Core's IIS logs to see whether you've actually *GOT* requests coming in.
Could be anything from DNS issues (i.e. "I try to reach the Core, but can't get through to it"), to IIS issues on the Core ("I see a request, but I'm overloaded so can't service it...") type stuff. IIS configuration (and/or resourcing) is a separate, and potentially rather lengthy subject.
If you do NOT see any requests in the IIS log from that client, chances are you don't really get through & likely have DNS issues for instance to contend with (or networking / network routing) -- so Wireshark may help you there for instance.
A few starting points with IIS (there's a lot to find on IIS, and support can help you with locating a few breadcrumbs if needed, but this can got a multitude of ways...).