Server behind TMG to grab updates from WSUS server
hey guys,
the last topic created grab superseeded updates wsus, stil cause can't accept installing updates manually answer. went ahead did more research on this.
to keep simple went ahead , adjusted local group policy / computer conf / admin templates / windows comp / windows update / specify intranet microsoft update server (http://172.16.3.3:8530)
allowed rule through tmg allow directional traffic of tcp 8530 between server lan (172.16.8.x <-> 172.16.3.3)
when click check updates can see established connection using netstat on port 8530.
click download updates, tries grab internet based servers... can see syn_sent right away , can see blocked http traffic on tmg.
so went ahead , set gpo setting , removed port allocation behind (http://172.16.3.3) doing netstat after clicking check updates showed connection attempt 172.16.3.3 via http, added protocol allow rule between servers, , sure enough changed established, , see allow through tmg. gives error when click on check updates...
there has way me dang server updates our wsus server on other side of tmg firewall.. how?! doing wrong?!
*note* port specified in local gpo of 8530, can access http://wsus/selfupdate/wuident.cab fine. ran wuauclt /detectnow , no errors reported in windowsupdate.log file
*note* wsus server setup cache update local dir, attempted see files in there contained random string .cab files, wish contain kbnumber , msu files easier verification of updates available in cache.
the last topic created grab superseeded updates wsus, stil
a link post helpful absolutely clueless post about.
allowed rule through tmg allow directional traffic of tcp 8530 between server lan (172.16.8.x <-> 172.16.3.3)
the correct implementation tmg create web publishing rule wsus server , allow passthru of client identity.
when click check updates can see established connection using netstat on port 8530.
click download updates, tries grab internet based servers... can see syn_sent right away , can see blocked http traffic on tmg.so went ahead , set gpo setting , removed port allocation behind (http://172.16.3.3) doing netstat after clicking check updates showed connection attempt 172.16.3.3 via http, added protocol allow rule between servers, , sure enough changed established, , see allow through tmg. gives error when click on check updates...
i see that you've specified private ip address target of wsus server (172.16.3.3), first set of questions revolves around why there's tmg server involved in first place, "wsus client" located respect tmg interfaces, , wsus server located respect tmg interfaces. maybe of in original post... wherever might be. i'm going assume you're *routing* traffic through tmg 1 private network private network, dmz wsus server in internal lan. (just educated guess.)
the second set of questions... 172.16.3.3 ip address of wsus server on internal lan, or address of dmz interface on tmg. configured correctly, should former.
third set of questions.... question ask because invariably sheds amazing insights other network issues.... why configuring policy ip address, rather hostname of wsus server?
there has way me dang server updates our wsus server on other side of tmg firewall.. how?!
properly configure web publishing rule. it's simple. have wsus server "published" dmz can patch dmz servers , works perfectly.
lawrence garvin, m.s., mcsa, mcitp:ea, mcdba
solarwinds head geek
microsoft mvp - software packaging, deployment & servicing (2005-2014)
mvp profile: http://mvp.microsoft.com/en-us/mvp/lawrence%20r%20garvin-32101
http://www.solarwinds.com/gotmicrosoft
the views expressed on post mine , not reflect views of solarwinds.
Windows Server > WSUS
Comments
Post a Comment