Are the ports open from the DMZ sup to the internal sup? Any errors in wcm.log/wsyncmgr.log? It sounds like the dmz sup just may not have been able to finish configuring yet due to firewall ports or something, so it hasn't gotten far enough to show that it's syncing with the internal sup. You should have a port (80/443 or 8530/8531) open from DMZ sup to internal SUP so they can sync.
From: [email protected] [mailto:[email protected]] On Behalf Of David O'Brien Sent: Tuesday, September 30, 2014 4:38 PM To: [email protected] Subject: [mssms] SUP in DMZ Hi all, A quick sanity check for me please: I've got an internal domain with a SUP (Software Update Point) that's allowed to communicate with Microsoft (the internet for that matter) and synchronise all the updates. I've got a second SUP in that internal domain that's sharing a SQL DB with that first SUP. That second SUP syncs without any issues from the first SUP. I've also got an untrusted forest with third SUP. That third SUP, for whatever reason, thinks it doesn't need to sync from the first SUP, but from Microsoft. Because it's an untrusted forest I can't have it share the SQL DB with the others, so I've told it to use its own SQL DB. That shouldn't however be the reason why it goes out to Microsoft instead of to the first SUP. Am I missing something here? To be clear, I'm talking about the SUP itself, not clients. Thanks for clearing that up for me :) David
