Jump to content

Aeropars

Members
  • Posts

    8
  • Joined

  • Last visited

Reputation

0 Neutral

About Aeropars

Personal Information

  • Location
    UK
  1. Yes, group policy has been checked and the WUS diagnostics tool shows that the settings are being applied to the workstations. we're on a standard ethernet network. Yes, I'm aware of the service packs needed and we are up to XP service pack 2 on most while 200 is sp4. Could well be a server side problem but i'm stumped as to what it could be! I was wondering whetehr setting up another server with a different website (other than the default one) so see if its something wrong with IIS but not sure if this would be worth doing.
  2. Whats an RM Network? Dont worry about the 3 locations, that only temporary to see if all sites will have the same problem. This will be part of a UK wide WAN so downstream servers will be needed. Its WSUS 3 on Windows 2003 Server which is hosted on a VMware box. The install of WSUS has been done exactly as per the documentation on the MS technet site. The only thing I havent added is that this domain was recentl migrated from NT4 to a new domain. User and computer accounts were migrated with SID history but this shouldnt have created duplicate SIDs. Either way, the script was run but it had no effect on the problem. Workstations dont appear at all apart from the odd 2 or 3 which makes it a really odd scenario.
  3. I've tried all of that but to no avail. One thing worth mentioning is that I cannot telnet to the web server on port 8530. I can only get in on port 80. I did use the default website during the installation as reccomended.
  4. Sorry to disagree but version 3 does need IIS installed to function. The update client uses an internet type url to connect to the service but in version 3 the admin consol is MMC based, although there is still need for IIS.
  5. I was hoping that script might work as its slightly different form another I ran. It still didnt work though. Incidentally, I've just built a VMware machine and it happens on brand new clients so I'm not so sure it could be the registry keys lingering around. Could there be something wrong on my IIS install or perhaps a permission that needs looking at? Thanks for your help so far.
  6. That link points back to this thread?? Even though the Id is different? Am I missing something?
  7. I've just tried this on a computer next to me and then ran the diagnostics again but its still giving the same error. I've also ran the /resetauthorization switch to no avail. Any mother ideas??
  8. Hi guys, first post so i'm hoping you can help me out on this! I'm deploying a wsus infrastucture but it has been set up previously, although it seems incorrectly. I have set up 3 servers where each one will serve a different location. Upon setting it up i noticed that there was hardly any computers being detected by the wsus consol and when I ran the WSUCLIentDiagnostic tool i got the following response We can ping the server, telnet to it on port 80 and remotely manage it so I'm certain the server isnt having a problem. DNS is working correctly for the clients as they can pint the server. Nothing is blocking traffic on port 80 either. The tool is also confirming group policy is being pushed out correctly. Does anyone have any ideas on what the problem here could be? Any help, greatly apreciated. Lee
×
×
  • Create New...