Solved

WSUS 3.0 and client configuration

Posted on 2008-06-10
1
2,282 Views
Last Modified: 2012-08-14
I have set up a wsus 3.0 update server on a windows 2003 server... We run in a mixed server enviroment with NT 4.0/2000 and the majority of the workstations are 2000 Pro SP4 or XP pro SP2...   I followed the instructions in the Microsoft guide on WSUS 3.0 to set it up on the server... I also followed the instructions from microsoft on setting up self update on clents in a non-active directory enviroment on a test PC running Windows XP sp2 ( we do  not use active directory, so I modified the register on the PC to make the change) .  The PC is not showing up on the WSUS as a connected PC... When I run the WSUS client diagnosis software on the XP machine, all pass until I get to the connection to WSUS server section and it failes with a "Verify WUServer URL<failed> with hr=0x80072ee6 error.
The URL doeesn't use a recognized protocol..." .  When I do a port scan on the IP of the server, it shows me that port 80 is open ( I used the standard ports of 80 and 443 for the wsus site).. I can ping the IP of the server from the client just fine... Why is this client not connecting to self update? If i can configure one client to connect and self update, I am sure the next 70 or so will be easy.. Any help would be appreciated. Thanks
John
0
Comment
Question by:magickman666
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
1 Comment
 
LVL 11

Accepted Solution

by:
pcfreaker earned 500 total points
ID: 21751442
Hi,

You may want to download a good tool for wsus working in workgroup environment:

http://msmvps.com/blogs/athif/archive/2006/05/09/94106.aspx

Basically, you should aim to have at least the computers recognized by the WSUS server, by this, try the basics, are your computers being able to connect to your wsus server and back?

Let me know your update,

Rgds.
0

Featured Post

Get your Disaster Recovery as a Service basics

Disaster Recovery as a Service is one go-to solution that revolutionizes DR planning. Implementing DRaaS could be an efficient process, easily accessible to non-DR experts. Learn about monitoring, testing, executing failovers and failbacks to ensure a "healthy" DR environment.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Hello, As I have seen there a lot of requests regarding monitoring and reporting for exchange 2007 / 2010 / 2013 I have decided to post some thoughts together and link to articles that have helped me. Of course a lot of information you can get…
If, like me, you have a lot of Dell servers in the estate you manage this article should save you a little time. When attempting to login to iDrac on any server I would be presented with two errors. The first reads "Do you want to run this applicati…
Michael from AdRem Software outlines event notifications and Automatic Corrective Actions in network monitoring. Automatic Corrective Actions are scripts, which can automatically run upon discovery of a certain undesirable condition in your network.…
If you’ve ever visited a web page and noticed a cool font that you really liked the look of, but couldn’t figure out which font it was so that you could use it for your own work, then this video is for you! In this Micro Tutorial, you'll learn yo…
Suggested Courses

623 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question