How can I use a network pc to be a time server?

one pc is going south by losing time, even after changing the battery.
I want the failing pc to use the time on another pc on the network.
No internet access for any computers.
win98se peer to peer.
Thanks in advance.

Check out Tardis, been using it for many years on a couple of networks.

http://www.kaska.demon.co.uk/tardis.htm

In article <(E-Mail Removed)>, "jd"
<jdumont@@novuscom.net> wrote:
>one pc is going south by losing time, even after changing the battery.
>I want the failing pc to use the time on another pc on the network.
>No internet access for any computers.
>win98se peer to peer.
>Thanks in advance.

Run this command on the failing pc, substituting the name of the
working pc for "computer":

net time \\computer /set /yes

You can put the command in a batch file and run it at startup or
whenever you need to have the right time.
--
Best Wishes,
Steve Winograd, MS-MVP (Windows Networking)

Please post any reply as a follow-up message in the news group
for everyone to see. I'm sorry, but I don't answer questions
addressed directly to me in E-mail or news groups.

Microsoft Most Valuable Professional - Windows Networking
http://mvp.support.microsoft.com

Steve Winograd's Networking FAQ
http://www.bcmaven.com/networking/faq.htm

hmmm... I did try this in the autoexec.bat file but got some error message.
I will try it in a batch file and put that in the startup folder or task
scheduler.
Thanks for all the replies everyone.

"Steve Winograd [MVP]" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> In article <(E-Mail Removed)>, "jd"
> <jdumont@@novuscom.net> wrote:
> >one pc is going south by losing time, even after changing the battery.
> >I want the failing pc to use the time on another pc on the network.
> >No internet access for any computers.
> >win98se peer to peer.
> >Thanks in advance.
>
> Run this command on the failing pc, substituting the name of the
> working pc for "computer":
>
> net time \\computer /set /yes
>
> You can put the command in a batch file and run it at startup or
> whenever you need to have the right time.
> --
> Best Wishes,
> Steve Winograd, MS-MVP (Windows Networking)
>
> Please post any reply as a follow-up message in the news group
> for everyone to see. I'm sorry, but I don't answer questions
> addressed directly to me in E-mail or news groups.
>
> Microsoft Most Valuable Professional - Windows Networking
> http://mvp.support.microsoft.com
>
> Steve Winograd's Networking FAQ
> http://www.bcmaven.com/networking/faq.htm

won't work in autoexec.bat, because this runs before the network starts up.

"jd" <jdumont@@novuscom.net> wrote in message
news:(E-Mail Removed)...
> hmmm... I did try this in the autoexec.bat file but got some error
> message.
> I will try it in a batch file and put that in the startup folder or task
> scheduler.
> Thanks for all the replies everyone.
>
> "Steve Winograd [MVP]" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
>> In article <(E-Mail Removed)>, "jd"
>> <jdumont@@novuscom.net> wrote:
>> >one pc is going south by losing time, even after changing the battery.
>> >I want the failing pc to use the time on another pc on the network.
>> >No internet access for any computers.
>> >win98se peer to peer.
>> >Thanks in advance.
>>
>> Run this command on the failing pc, substituting the name of the
>> working pc for "computer":
>>
>> net time \\computer /set /yes
>>
>> You can put the command in a batch file and run it at startup or
>> whenever you need to have the right time.
>> --
>> Best Wishes,
>> Steve Winograd, MS-MVP (Windows Networking)
>>
>> Please post any reply as a follow-up message in the news group
>> for everyone to see. I'm sorry, but I don't answer questions
>> addressed directly to me in E-mail or news groups.
>>
>> Microsoft Most Valuable Professional - Windows Networking
>> http://mvp.support.microsoft.com
>>
>> Steve Winograd's Networking FAQ
>> http://www.bcmaven.com/networking/faq.htm
>
>

On Tue, 12 Jul 2005 12:10:21 -0600, "j9" <(E-Mail Removed)> wrote:

|won't work in autoexec.bat, because this runs before the network starts up.

Forget autoexec.bat. Run commands from \windows\startup after testing.

First create and test your batch file. I'll use as an example one from 98SE
network I manage as a volunteer. Computer used for time reference, and for
shared folders, has name "data". For this example fixit.bat is name of batch
file, and a shortcut is placed on both desktop, for running easily stand
alone, and in \windows\startup folder for running at startup after windows
starts.

It can be as simple as four lines

net time /set \\data /yes
echo off
cls
exit

where the last 3 lines are to make sure window closes when it is run. You
can leave them out for initial tests. If you can make it work manually,
then it should work at startup since windows will have started.

I also mount all drives in the file with the net use command, such as

net use * /d
net use s: \\data\docs /yes
net use p: \\data\petwhere /yes

before the final three lines. That way if 98se file server reboots, or
wiring screws up, no need to reboot workstations -- just double click on
desktop icon on each one.

On Tue, 12 Jul 2005 12:10:21 -0600, "j9" <(E-Mail Removed)> wrote:

Corrected version, (startup folder identified in wrong place in prior message)

|won't work in autoexec.bat, because this runs before the network starts up.

Forget autoexec.bat. Run commands from Start Menu's Startup Folder, which is
also \Windows\Start Menu\Programs\StartUp on a Windows 9x machine

First create and test your batch file. I'll use as an example one from 98SE
network I manage as a volunteer. Computer used for time reference, and for
shared folders, has name "data". For this example fixit.bat is name of batch
file, and a shortcut is placed on both desktop, for running easily stand
alone, and in \windows\startup folder for running at startup after windows
starts.

It can be as simple as four lines

net time /set \\data /yes
echo off
cls
exit

where the last 3 lines are to make sure window closes when it is run. You
can leave them out for initial tests. If you can make it work manually,
then it should work at startup since windows will have started.

I also mount all drives in the file with the net use command, such as

net use * /d
net use s: \\data\docs /yes
net use p: \\data\petwhere /yes

before the final three lines. That way if 98se file server reboots, or
wiring screws up, no need to reboot workstations -- just double click on
desktop icon on each one.