Windows 2003 - SUS - clients cant connect?

But that is for windows 2000 only is it no as the new auto updated was only
include in XP and SP's of win 2k?


[quote]
SUS requires a special version of Automatic Updates. This updated Automatic
Updates client software builds on the Automatic Updates client that was
shipped in Windows XP. It now runs on Windows 2000 Professional, Windows
2000 Server, and Windows 2000 Advanced Server (Service Pack 2 or higher). It
also runs on computers running Windows XP Professional, Windows XP Home
Edition, and the Windows Server 2003 family.






i was reading over the

SUSOverview.doc
SUS_Deployguide_sp1.doc

i even tried using the reg files it suggests on Page 64 under trouble
shooting. According to that document if i left everything at defualt it
should work, yet it is not so i went ahead with the instructions for
Configuration Options in a Non-Active Directory Environment

since i am not using an active dir.


i ahd it set up as such

[quote]
Working in DNS and NetBIOS Environments
Your client computers running the Automatic Updates client will need to
connect and download content from your server running SUS.

In most environments, the client computers will be able to locate the
Intranet server running SUS using the NetBIOS name of the server (for
example, <a style='text-decoration: underline;' href="http://SUSServer1" target="_blank">http://SUSServer1</a>). If this matches your environment, no additional
configuration is required.

Other environments may require client computers to use the DNS name to
locate the server running SUS (for example, <a style='text-decoration: underline;' href="http://servername.domain" target="_blank">http://servername.domain</a>). If
this is the case, you must configure a DNS name for that server. This is
important because clients use this DNS name to download updates from SUS.

To configure the DNS name that clients use to locate the SUS server, enter
the DNS name under Specify the name your clients use to locate this update
server, in the Server Name: field. Make sure that clients can use this DNS
name to connect to your server running SUS.



"

I had this working once before on defualt settings but now i cant - maybe
just reinstall it an try again!

"Ken Schaefer" <kenREMOVE.TakeThisOut@THISadOpenStatic.com> wrote in message
news:uIBp2tJhDHA.4024@TK2MSFTNGP11.phx.gbl...
 > Please read the SUS Deployment Whitepaper:
<font color=purple> > <a style='text-decoration: underline;' href="http://www.microsoft.com/windows2000/windowsupdate/sus/susdeployment.asp</font" target="_blank">http://www.microsoft.com/windows2000/windowsupdate/sus/susdeployment.a...lt;/fon</a>>
 >
 > When using SUS, you do not have a website like
WindowsUpdate.microsoft.com.
 > Instead, the AU client and BITS service downloads updates in the
background
 >
 > Cheers
 > Ken
 >
 > "Mathiau" <mathiau.TakeThisOut@quickring.com> wrote in message
 > news:u8v3fzIhDHA.3636@tk2msftngp13.phx.gbl...
 > : Heyall
 > :
 > : i set up SUS (windows update server)on my 2k3 box and got it all
 > : synchronize - how ever when i go to a client computer (xpSP1 ) and type
in
 > : the URL
 > :
 > : <a style='text-decoration: underline;' href="http://10.10.10.10" target="_blank">http://10.10.10.10</a> (fake) IP to the SUS server - it just bring up the
 > : "under contrcutions page from IIS
 > :
 > :
 > : i did not change anything in IIS and left it all as default and
according
 > to
 > : MS - it should work like this but is not?
 > :
 > : Any suggestions please.
 > :
 > :
 > :
 >
 ><!-- ~MESSAGE_AFTER~ -->
 >> Stay informed about: Windows 2003 - SUS - clients cant connect? 

a) I have no idea what you're talking about WRT to the SUS client software.
The SUS client software is included in Windows 2000 Service Pack 3, and
Windows XP SP1. If you don't have those SPs installed, you need to install
the SUS client manually on each machine. You CAN NOT browse to the SUS
server's website to see whether the clients are connecting.

IE, on the client machine, YOU DO NOT goto http://susservername/
Instead, the AU client goes to the SUS server, and checks the catalog. The
BITS service downloads any updates.

PLEASE READ THE SUS DEPLOYMENT WHITEPAPER which details how the clients get
the updates.

TO TROUBLESHOOT SUS CLIENT PROBLEMS
b) If you look in the Windows Update.log file, are the clients connecting to
the SUS server?

b) What are the registry settings under:
HKLM\Software\Policies\WindowsUpdate\ and
HKLM\Software\Policies\WindowsUpdate\AU

c) Post the relavant information to the SUS server newsgroup:
news://microsoft.public.softwareupdateservices

Cheers
Ken

"Mathiau" <mathiau.DeleteThis@quickring.com> wrote in message
news:%23TyGe4KhDHA.1952@TK2MSFTNGP10.phx.gbl...
: But that is for windows 2000 only is it no as the new auto updated was
only
: include in XP and SP's of win 2k?
:
:
: [quote]
: SUS requires a special version of Automatic Updates. This updated
Automatic
: Updates client software builds on the Automatic Updates client that was
: shipped in Windows XP. It now runs on Windows 2000 Professional, Windows
: 2000 Server, and Windows 2000 Advanced Server (Service Pack 2 or higher).
It
: also runs on computers running Windows XP Professional, Windows XP Home
: Edition, and the Windows Server 2003 family.
:
:
:
:
:
:
: i was reading over the
:
: SUSOverview.doc
: SUS_Deployguide_sp1.doc
:
: i even tried using the reg files it suggests on Page 64 under trouble
: shooting. According to that document if i left everything at defualt it
: should work, yet it is not so i went ahead with the instructions for
: Configuration Options in a Non-Active Directory Environment
:
: since i am not using an active dir.
:
:
: i ahd it set up as such
:
: [quote]
: Working in DNS and NetBIOS Environments
: Your client computers running the Automatic Updates client will need to
: connect and download content from your server running SUS.
:
: In most environments, the client computers will be able to locate the
: Intranet server running SUS using the NetBIOS name of the server (for
: example, http://SUSServer1). If this matches your environment, no
additional
: configuration is required.
:
: Other environments may require client computers to use the DNS name to
: locate the server running SUS (for example, http://servername.domain). If
: this is the case, you must configure a DNS name for that server. This is
: important because clients use this DNS name to download updates from SUS.
:
: To configure the DNS name that clients use to locate the SUS server, enter
: the DNS name under Specify the name your clients use to locate this update
: server, in the Server Name: field. Make sure that clients can use this DNS
: name to connect to your server running SUS.
:
:
:
: "
:
: I had this working once before on defualt settings but now i cant -
maybe
: just reinstall it an try again!
:
: "Ken Schaefer" <kenREMOVE.DeleteThis@THISadOpenStatic.com> wrote in message
: news:uIBp2tJhDHA.4024@TK2MSFTNGP11.phx.gbl...
: > Please read the SUS Deployment Whitepaper:
: > http://www.microsoft.com/windows2000/windowsupdate/sus/susdeployment.asp
: >
: > When using SUS, you do not have a website like
: WindowsUpdate.microsoft.com.
: > Instead, the AU client and BITS service downloads updates in the
: background
: >
: > Cheers
: > Ken
: >
: > "Mathiau" <mathiau.DeleteThis@quickring.com> wrote in message
: > news:u8v3fzIhDHA.3636@tk2msftngp13.phx.gbl...
: > : Heyall
: > :
: > : i set up SUS (windows update server)on my 2k3 box and got it all
: > : synchronize - how ever when i go to a client computer (xpSP1 ) and
type
: in
: > : the URL
: > :
: > : http://10.10.10.10 (fake) IP to the SUS server - it just bring up
the
: > : "under contrcutions page from IIS
: > :
: > :
: > : i did not change anything in IIS and left it all as default and
: according
: > to
: > : MS - it should work like this but is not?
: > :
: > : Any suggestions please.
: > :
: > :
: > :
: >
: >
:
:
 >> Stay informed about: Windows 2003 - SUS - clients cant connect?