I've got one of those boards. I can't swear to it but I believe one indicates connectivity and the other indicates the speed of the connection, such as 100Mbit.
Do any of you happen to run ntp (or better, ntpd) with a AN35N-based system? Will not stay sync'ed for nothing. Other 30+ systems in the lab (including Asus nForce2 boards and a few K7S5As) are fine.
You might try another CMOS battery, or a simple client installation of ntpd with a binary daemon to periodically connect to a time server at port 123 to update the system clock, and it rarely needs more than one argument fyi. I have not had a problemw ith it, but I do know that cheaper mainboards can and so have thos type problems from time to time.
I am running ntpd (server, not the client) on every machine in my lab. By running servers (all point to two specific, official NTP servers), I can set one machine to sync to all of the others, giving me a snapshot of all machines according to their 'reach'. Only the two AN35N systems are consistently off, at a referesh rate of 1024 seconds.
Is it possible that ntpd is not able to set the time properly on these machines in the first place, so as to leave them out of sync from the very begining?
Possibly. But then again, this is a 30+ system lab. The only flavor of Windows I'm running is 2000 Pro. No other Win2K boxes exhibit this behavior. Let's say that at least half of my systems are running Win2K, then I'm pretty sure that I've got a consistent configuration scheme. In other words, I doubt that there is something so different (software-wise) about these two PCs that makes them react differently than the dozen other Windows PCs I've got.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.