Kurt
Fri Apr 22 07:07:55 CDT 2005
Here are some ideas:
1. Did you install Windows 2003 SP1? If so, it causes
problems with SUS.
2. Check the Event Viewer for services that are failing.
Remember that SUS uses IIS, so any changes or hotfixes you
applied that affect IIS could also be causing the issue.
3. Check for permission changes to the SUS virtual
directories in IIS as well as any changes to the NTFS
folders to which those virtual directories map.
4. Use Netdiag from the client computers to see if you
have any connectivity issues to the server.
5. Ensure that your clients are configured to contact
http://sus_server_host_name. Then, be sure that you can
run a successful nslookup to the name of the SUS server.
Could be a DNS issue for the host name of the SUS server
maybe. Even if you get an access denied, what if the
clients are being directed to the wrong address.
Also, it could be an ARP issue - however that is highly
unlikely. Still it is easy enough to check. Ping the IP
address of the SUS server and see if the MAC address in
your ARP cache (arp -a) entry for the IP address you
pinged matches the actual MAC address of the SUS server.
Good luck!
>-----Original Message-----
>I`ve been using a SUS Server for months.
>Suddenly, client computers report an error while trying
to access/install
>new versions of WUAU software (a wmi package...) which is
located in the same
>location when it was installed/configured.
>The result: nobody is installing updates automatically :(
>The message seems to tell the sysadmin that client
computers "do not have
>access or permission to it (?)"
>Policies, configurations and related topics are always
the same.
>Thanks in advance.
>
>.
>