new image issue Marc Castadot <Marc.Castadot[ at ]dot.state.nj.us> 6/25/2007 3:31:23 PM We have a segment of our network that has no internet access by design. When we build a new machine (or image) it refuses to check in with our WSUS server from that segment. It is only after the pc (or imaging machine) gets moved to a segment that has internet access that it checks in with the Wsus server. Is that by design or is there flaw? Info: winXP pc SP1 WSUS 2.0 and 3 (both tried and failed)

RE: new image issue eddieb[ at ]online.microsoft.com (Eddie Bowers [MSFT]) 6/25/2007 9:15:36 PM I would guess that your selfupdate directory isn't working on port 80 and your WSUS site is on 8530. The older clients can only selfupdate over port 80. You can do a few things to test this. First see what version of wuaueng.dll is on these machines originally. See if you manually update the client to the most recent version: http://download.windowsupdate.com/v7/windowsupdate/redist/standalone/Windows UpdateAgent30-x86.exe if it then checks in. Eddie Bowers Security Support Microsoft Corporation This posting is provided "AS IS" with no warranties, and confers no rights.

Re: new image issue "Lawrence Garvin \(MVP\)" <onsitech[ at ]community.nospam> 6/26/2007 2:04:19 AM "Marc Castadot" <Marc.Castadot[ at ]dot.state.nj.us> wrote in message news:178ea80e180ea8c985337e548eaa[ at ]msnews.microsoft.com... [Quoted Text] > We have a segment of our network that has no internet access by design. > When we build a new machine (or image) it refuses to check in with our > WSUS server from that segment. It is only after the pc (or imaging > machine) gets moved to a segment that has internet access that it checks > in with the Wsus server. > > Is that by design or is there flaw? > > Info: winXP pc SP1 There's a couple of possibilities, here, Marc. First,when you say that you have a segment that has no internet access by design, but your WSUS server does have access, it begs two questions: [a] How does that segment get to the WSUS server, in general? [b] How are you blocking Internet access from that segment? Possibly the issue is not getting *to* the WSUS server, per se, but merely getting *out* of that restricted subnet in any fashion? Eddie makes this suggestion >I would guess that your selfupdate directory isn't working on port 80 and >your WSUS site is on 8530. >The older clients can only selfupdate over port 80. But I can't see how those symptoms would be specific to one subnet over another. If the WSUS site wasn't functioning on port 80, and XP SP1 system wouldn't get selfupdated, even if it were plugged into the physical port right next to the WSUS server. However, if the *router* between the restricted subnet and the rest of the world had port 80 blocked (Is that how you're "restricting access to the Internet"?) -- then that would definitely muck with WSUS functionality. I believe you're going to find this is likely to be a networking infrastructure issue. -- Lawrence Garvin, M.S., MCTS, MCP Independent WSUS Evangelist MVP-Software Distribution (2005-2007) https://mvp.support.microsoft.com/profile=30E00990-8F1D-4774-BD62-D095EB07B36E Everything you need for WSUS is at http://technet2.microsoft.com/windowsserver/en/technologies/featured/wsus/default.mspx And, almost everything else is at http://wsusinfo.onsitechsolutions.com .....