LIttle Trouble, WIndows SBS 2003

[fenderltd]

I have about 20 computers on the network and for the life of me a few of them are not auto sync'n the time with the primary server therefore not allowing others into shared folders. I googled this but coming back with things that are not really related to me problem. Where in SBS or maybe it's in Active Directory to make each computer auto sync. I thought with the computer being on the domain and part of the Active Dir, that it would sync the time it self. Also, some computers also have the update time from internet and some don't... Thanks in advance!


http://www.hardfolding.com/ftag1.php/mem/166014/216/0.png (http://www.hardfolding.com?go=38&tnum=33&id=166014)

[fenderltd]

no one:(

[pigster]

Sounds like the clients are not properly joined to the domain.

How did you join them, the ConnectComputer wizard or manually? Where do the client computers show up in AD ?

[slowbiznatch]

I would remove them from the domain (and remove the computer account from AD Users and Computers) and rejoin them. When you rejoin the computer, make sure the computer account is recreated in AD Users and Computers.

[nessus]

If the clients aren't members of the domain, but you want them to synch anyway, run "net time /SETSNTP:SBS2003_servername".

Run "w32tm /s" to verify the results.

[swatbat]

I agree with nessus. You can also throw the net time into the login bat files. That way they update their time with the servers each time they login.

[fenderltd]

The users are under my AD>domain > MyBusiness>Users>SBSUSERS I joined the clients to the domains through user accounts if I not mistaken.
The only thing right now that I have in the SBS login script is \\SERVER\Clients\Setup\setup.exe /s SERVER
net use o: \\server\ddrive
net use p: \\ups\cdrive


What is the update time script to force time sync every logon? anything else I should have in the script while I am at it? :D

Also, I am fairly new to sbs2003 and anything server related but I am learning. What is the proper way to join a user to a domain? all workstations are Windows XP Pro.

Thanks in advance everyone, I thank you for all your help

[lAciDl]

open IE and in the address bar type the following.

\\server\connectcomputer

follow the wizard and when it asks for the username/password you use the users information(not admin). It will also ask you to choose an available computer name. You will have to make these before running the wizard.

[swatbat]

http://support.microsoft.com/kb/314090

"For example, assume that you have a server named Timesrv that has a reliable system clock. Here is an example batch file that can either run from the workstation or be called from (or be part of) a logon script:
net time \\timesrv /set /yes
Using just a server name instead of using the /domain or /workgroup parameter avoids the complexity of maintaining different logon scripts or batch files for the different types of network client software. If all of your workstations run the same type of network client software, you can use the /domain or /workgroup parameter. However, in a network that has a variety of network client software, it is easier to use the \\computername parameter."

[fenderltd]

Thanks for all the help and links, I have added net time \\timesrv /set /yes to the login script located in C:\WINDOWS\SYSVOL\sysvol\mydomainhere.local\scripts\SBS_LOGI N_SCRIPT.bat

[fenderltd]

open IE and in the address bar type the following.

\\server\connectcomputer

follow the wizard and when it asks for the username/password you use the users information(not admin). It will also ask you to choose an available computer name. You will have to make these before running the wizard.

When I tried this it gave me an error about spelling?

[swatbat]

Thanks for all the help and links, I have added net time \\timesrv /set /yes to the login script located in C:\WINDOWS\SYSVOL\sysvol\mydomainhere.local\scripts\SBS_LOGI N_SCRIPT.bat

now in place of timesrv you used your servers name right?

IE if your sbs box is called fileserver you would use "net time \\fileserver /set /yes"
If it is pornstar it would be "net time \\pornstar /set /yes"

[fenderltd]

Yes, I am sorry I didn't point that out, thanks for double checking with me. ANything else on why the \\servername\connectcomputer is not working?

[fenderltd]

Also, maybe I should start a new thread for this, but for the remote desktop app
example. (www.domainname.com/remote) etc. for average users, if they login in, and the hit connect to my computer at work it brings up the COMPLETE list. How do you make it so "Bill" can only connect to "Bill's Computer" ? Thanks everyone, you are lifesavers!

[slowbiznatch]

Here's a good read on network time & Active Directory:

http://www.windowsnetworking.com/articles_tutorials/Configuring-Windows-Time-Service.html

Basically, ever system connected to the domain should sync it's clock with the DC it authenticates with. If it cannot sync and the times do not match correctly, you will have problems authenticating using Kerebos.

The reason I'm pointing this out to you is because the solution to run a logon script in GP may seem to fix the problem, but it won't completely. The fact that those systems are not syncing leads me to believe there is something bigger to this issue.

[pigster]

Yes, I am sorry I didn't point that out, thanks for double checking with me. ANything else on why the \\servername\connectcomputer is not working?

Try http://servername/connectcomputer

[fenderltd]

Here's a good read on network time & Active Directory:

http://www.windowsnetworking.com/articles_tutorials/Configuring-Windows-Time-Service.html

Basically, ever system connected to the domain should sync it's clock with the DC it authenticates with. If it cannot sync and the times do not match correctly, you will have problems authenticating using Kerebos.

The reason I'm pointing this out to you is because the solution to run a logon script in GP may seem to fix the problem, but it won't completely. The fact that those systems are not syncing leads me to believe there is something bigger to this issue.

What could be causing such an issue? I don't notice any other things wrong, it's just with this one IBM box we got for free from UPS that it is having trouble letting all clients connect to it. Some clients have zero problems, a few other clients are having trouble with the error of primary domain clock BS...
But so far, none after I added the set time to the login script.