WSUS 3.0 and client configuration

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
magickman666Asked:
Who is Participating?
 
pcfreakerConnect With a Mentor Commented:
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
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.