Re: WSUS port issue
- From: "Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]" <sbradcpa@xxxxxxxxxxx>
- Date: Tue, 08 Aug 2006 19:52:25 -0700
SBS needs to have it on 8530
Greg O wrote:
Couldn't he change the port back to port 80 instead of 8530? If he did.
then nothing would be needed to be changed in group policy.
kj wrote:
Mark,
Is this just one workstation or all workstations?
Do any workstations show up in the WSUSAdmin console?
There are a couple of other possibilities (at least) besides a superseding
GPO.
One; the GPO isn't applying. Change or delete the registry setting and see
if returns. If it does, then *something* is setting it. Check the event log
and verify group policy is being applied successfully.
Two; something is coming along after the GPO applies and setting this back.
I took over a site where the admin had deployed a login script with .reg
files apparently because he couldn't fix the problem with group policies.
When we upgraded them from SUS to WSUS and modified the GPO's the clients
wouldn't stay associated with the WSUS server. That one was really weird to
track down.
--
/kj
"Mark" <info-nospam@xxxxxxxxxxxx> wrote in message
news:%237W$pwpuGHA.5084@xxxxxxxxxxxxxxxxxxxxxxx
KJ is correct, the GPO shows :8530 but the reg key doesn't and all are XP
SP2, quite odd!
"kj" <kj@xxxxxxxxxxx> wrote in message
news:eXU0jrnuGHA.4292@xxxxxxxxxxxxxxxxxxxxxxx
As I recall the really old windows update clients didn't handle the non
80 port numbers. Is this an RTM XP client or pre SP4 Win 2K machine? I'd
still be surprised if the registry wasn't correct with the presiding
policy setting.
No running the clientdiag would just confirm the settings but perhaps
provide something missed or overlooked.
--
/kj
"Mark" <info-nospam@xxxxxxxxxxxx> wrote in message
news:e6Zd%23hnuGHA.1852@xxxxxxxxxxxxxxxxxxxxxxx
negatory, triple checked the GPO. will run the diag but if the
location isn't correct, that won't help.
"kj" <kj@xxxxxxxxxxx> wrote in message
news:OukaXYnuGHA.4544@xxxxxxxxxxxxxxxxxxxxxxx
No, WUServer and WUStatusServer should look like http://server:8530
Fat finger on the colon in the GPO and perhaps a semicolon got inserted
instead?
Run the (wsus) clientdiag.exe and check the results.
--
/kj
"Mark" <info-nospam@xxxxxxxxxxxx> wrote in message
news:enHHHQnuGHA.4544@xxxxxxxxxxxxxxxxxxxxxxx
Installed WSUS on SBS2003, no problem except in GPO I specified
http://server:8530 for the location yet in the registry it just puts
http://server but is that normal???
- Follow-Ups:
- Re: WSUS port issue
- From: Greg O
- Re: WSUS port issue
- References:
- WSUS port issue
- From: Mark
- Re: WSUS port issue
- From: kj
- Re: WSUS port issue
- From: Mark
- Re: WSUS port issue
- From: kj
- Re: WSUS port issue
- From: Mark
- Re: WSUS port issue
- From: kj
- Re: WSUS port issue
- From: Greg O
- WSUS port issue
- Prev by Date: Re: DHCP with SBS 2003 and Wireless Router assigning IP out of subnet
- Next by Date: Re: WSUS port issue
- Previous by thread: Re: WSUS port issue
- Next by thread: Re: WSUS port issue
- Index(es):
Relevant Pages
|