Hey guys. Im trying to install a secondary site (working with SCCM 2007 R3) which is in a different subnet than its primary.
Now the initial setup completes fine (i've checked the configmgr setup log). but then the site remains in peding state. so i check the sender log and this is what I see over and over: sender.txt
also i checked the despooler and i see this over and over:despooler.txt
So, im confused because i can connect via RDP to the primary server, and i can ping the primary server with its FQDN, so clearly there is something wrong somewhere. i have tried before to manually exchange keys en control file. and then the site did turn active. but i could not push anything to the site because there was still that communication error. then i deleted the secondary site and build it up again but same error, same problem. need help with this!
We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.
Hey guys. Im trying to install a secondary site (working with SCCM 2007 R3) which is in a different subnet than its primary.
Now the initial setup completes fine (i've checked the configmgr setup log). but then the site remains in peding state. so i check the sender log and this is what I see over and over: sender.txt
also i checked the despooler and i see this over and over:despooler.txt
So, im confused because i can connect via RDP to the primary server, and i can ping the primary server with its FQDN, so clearly there is something wrong somewhere. i have tried before to manually exchange keys en control file. and then the site did turn active. but i could not push anything to the site because there was still that communication error. then i deleted the secondary site and build it up again but same error, same problem. need help with this!
Share this post
Link to post
Share on other sites