Tom's Guide | Tom's Hardware | Tom's Games
 |
 |
 |
We have a new Compaq rackmount server thats running netware 5. It keeps losing about 30 mins everyday in the system clock. Any ideas why?
I assume this is the only server on the network; then I would look at the RTC battery or BIOS upgrade. If it is not the only server then it should be getting its time from the network.
0 
I seem to be having the same problem. I have a dual pentium III 850 with 512MB RAM. I replaced the motherboard and both CPUs - problem's still there. I have a one server system with a DiskZerver CD stack (pretends to be a server). If you get a fix, please let me know.
0
I am having the same problem, on 5.1 running on an IBM Netfinity. It seems all answers point to a newer timesync.nlm and a problem with ide drivers ...IDEATA.HAM. a lot of comments I've found say to update these to a newer version.
0
I had the same problem. Fixed it by syncing with the US Navel Observerty's atomic clock. All better now. My time problems started when I applied the latest support Pack from Novell to my netware 5.0 server. I also installed NovaNet backup software on the same day, so I am not sure which caused the problem. I was told that it was probably the daily backup that was causing the problem, but I'm not sure. Anyways, it's fixed now.
WC
0
I've encountered this on several 5.x Compaq servers. The best work around I've found is outlined in TID 10023130. You can find this document at support.novell.com.
0
Try using an Atomic Clock as an accurate time source, you can find Novell software drivers and Atomic clock time receivers on www.galleon.eu.com.
Atomic clocks are accurate to 1 second in a million years.
0
I am not familiar with Netware. At least not enough to solve this time problem it would seem. I have recently taken over the admin of three different Novell servers running 4.1, 5 and 5.1 at three different locations. They are stand alone servers and don't have connections to the Internet so I don't know what it would take to reference them with an outside atomic server. I am not attempting to 'bash' Novell but doesn't it seem silly that a Netware server can't keep time as well as a $ 5 watch? I know that NT has it's bugs but they are at least complicated things, not things that a watch from a gumball machine could do. I am quite frustrated. One of the servers is a fairly new (less than a year) 5.1 server that has never been able to keep time. It loses days of time over the course of a month. Another server, the Netware 5 one, just recently started losing time at the rate of a few minutes a day. The 4.1 server had a hard drive go out and when I replaced it the time went back 3 years! I tried to set the time through the bios, DOS, and the console and just to upset me it went back another ten years! Right now the clock says 1988 and I cannot set it forward. Strange, huh? On that one there is no timesync.cfg file on the server, should I write one myself?
The Novell knowledgebase is less than helpful to someone who doesn't already know what they are doing.
0
When I unload ideata.ham, I did not lose any time after that and this was on a compaq server. When ideata.ham is load it keeps polling for somethind in the cd rom. If there is nothing in the cdrom it will lose time. Either unload ideata.ham or keep a cd in it or get a new driver.
0
Windows 9x and ME users: Adjusting time / date or month causes lost time.
Third party utility or screen saver causing incorrect time.
Issue with APM. Automated Power Management (Control Panel)
Bad Battery / Replacing the CMOS battery.
0  |
 |
 |
This post is quite old and has been locked from receiving new replies. Please create a new posting instead.
| Ads by Google |
