Computers are Unable to contact WSUS on a 2008 server

Computers on the network are Unable to contact WSUS on a 2008 server.
in the application event log on the server I keep getting

Log Name:      Application
Source:        Windows Server Update Services
Date:          9/6/2008 8:54:49 PM
Event ID:      13051
Task Category: 6
Level:         Warning
Keywords:      Classic
User:          N/A

No client computers have ever contacted the server.


Where do I start?? we had a WSUS that was installed on a 2003 box and was working
HBICalgaryAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Eraser63Commented:
Hi.
I guess you already have configured the GPOs to tell the computers which server to look for updates.
Have you already configured the Windows Server 2008 firewall to open the good tcp port ?
0
NickperfCommented:
Hi,

You need to put in the name or ip address of your WSUS server in the group policy..

1. Open Domain GPO or you custom GPO and browse to following GP:
Computer configuration | Administrative templates | Windows Components | Windows Update

"Specify intranet Microsoft update service location Policy"

2. Open port 80 or 443..


0
AmericomCommented:
If you use the same GPO that was used when your WSUS was running on Win2k3 server, then all you need to do is update the appropriate server in the URL link http://YourWsusServer of your GPO. If you created a complete new GPO, other than the configuration above, may sure you apply the GPO to the OU where your computers is placed in and not the Users OU as the WSUS is a computer policy.
Otherwise, do the followings:

1. Force a group policy update (if client machine is in a domain): type gpupdate /force
2. You may run gpresults at the command prompt to verify if the GPO did get applied.
3. Force a detection: type wuauclt.exe /resetauthorization /detectnow, wait 10 minutes for a detection cycle to finish before verification.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Creating Active Directory Users from a Text File

If your organization has a need to mass-create AD user accounts, watch this video to see how its done without the need for scripting or other unnecessary complexities.

HBICalgaryAuthor Commented:
Port 80 is open.
It was configured as http://eros:8530
and I changed it to http://eros:80

??
0
HBICalgaryAuthor Commented:
Do this on the client machine or the wsus server??
3. Force a detection: type wuauclt.exe /resetauthorization /detectnow, wait 10 minutes for a detection cycle to finish before verification.
0
AmericomCommented:
on the client machines, just pick a test machine and run those commands and see if it will eventually appear in the WSUS console.

I'm assuning your "eros" is your Windows server 2008 where your WSUS is installed and configured...
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2008

From novice to tech pro — start learning today.

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.