• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 654
  • Last Modified:

Wsus3 Clients connected to wrong wsus Server

Hi


We have an issue where a few clients from a few offices are connected to the wrong wsus server. It is also downloading something from the wsus3 server and causing heavy network traffic

If i run a netstat on a client that is registred to stockholmwsus, i see connections to glasgowwsus.

We have used tpcview, and the connections are: system:4 connections.

Why are some clients connected to a diffrent wsusbox while they are registred on the correct one and can be seen as active on the correct wsusserver, but still is downloading stuff from another wsusserver which is not specified in gpo??

All XP, GPO's used. Clients are in correct GPO.

Thanks /Dabosa
0
Dabosa
Asked:
Dabosa
  • 3
  • 2
1 Solution
 
rentoncCommented:
Assuming you have checked the GPO and confirmed by looking at the registry settings on the affected machines
in the follwoing key
HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate

It couild be a DNS issue on the affected machines, can you ping to your stockholmwsus from the affected machines to make sure they are not resolving to the ip of the glasgowwsus

0
 
DabosaAuthor Commented:
GPO is checked and correct, also the correct server stockholmwsus is specified in this registry key.
Still there are connections to the glasgowwsus.

The clint ip settings are correct, the stockholmwsus resolves fine.

I have now checked the IP config on both wsus servers and they have the same correct  dns's and wins's.
0
 
rentoncCommented:
1 final thought - is that maybe it is in the middle of a large update so the cookie may still point to the old server - maybe you could try this from the command prompt
wuauclt /resetauthorization /detectnow

0
Making Bulk Changes to Active Directory

Watch this video to see how easy it is to make mass changes to Active Directory from an external text file without using complicated scripts.

 
DabosaAuthor Commented:
Just tried it, command went fine, but still i see connection to wrong wsus server.

I have used the taskkill /F /PID "nr" on client tio kill connection and it sussessfully removes the connection but its instantly re-establishes connectivity once removed.
0
 
DonNetwork AdministratorCommented:
What does this command return?
 
reg query "HKLM\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate" /s  
0
 
DabosaAuthor Commented:
It is solved now. This was the problem: In the same subnet we had a rightfax server

It just so happens that it used  to be the same IP address as the new Glasgow WSUS Server. No IP confilct events on the wsus though:(

The problem is arising when users have accidently printed to the Rightfax driver (possibly because it was set a default at one point.)

These then attempt to connect to the WSUS Server.

The size of the print seems to have some bearing on the connections also, but Im not sure where the downloading is coming from, or if the prints determine the size.

WSUS was fine all along - All fine now.

Thanks for all troubleshoot input! /D

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.

Join & Write a Comment

Featured Post

Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now