All wcm content pages are stuck in a publish-pending status. ASI Tech Support seems to have run out of ideas for how to fix this problem. I'm wondering if the client did something to cause this problem since we were able to publish just fine until a couple of weeks ago. Now whenever we publish, the changes don't show up on the website, obviously because of the publish-pending problem. Restarting the ASI Publishing service does not resolve the issue. We have more than one instance of iMIS, but each one has its own port number (searchRemoting.confg and PublishService.exe.config), so that potential problem has been ruled out. We previously had some internal DNS problems, so I changed all the servername and/or domain name references to IP addresses within the config files. At least one other consultant has looked at this problem, but so far the solution remains elusive. Any suggestions?