novell problem

[layne151]

The server keeps messing up the time (will not advance past 1998 and stay there) I could not find a y2k patch for it and was wondering if there was a way to disable the time sync to the clients accessing it, i think i have done it on an older version but unable to do it on this version (4.1)


Please and input appreciated!

 

[CTR]

There is a setting on the Novell client for getting time from the server. But a Novell 4.x server that is not keeping timesync is a recipe for disaster. Directory Services is VERY time sensitive. You should fix the problem instead of masking the symptoms. Get the last service pack for 4.10, and if that doesn't fix it start looking for hardware problems. Maybe something like a dead CMOS battery on the mainboard.

 

[PrinceofWands]

I've also noticed this tendancy for time errors with Novell. When I took my first Neovell class even the instructor never managed to correct the servers broadcast time. The same problem was also noted at two of my jobs...the server would broadcast an incorrect time forcing all clients onto the same time. It was a real pain in the butt.

 

[CTR]

I was pm'ing with layne151 about this a few minutes ago. It looks like the CMOS reports the time with no problems. New battery and everything. But when server.exe takes over it looks like it is picking up 1998 for some reason. I asked him about the service pack again, and asked him to down and exit if possible and check the time from DOS. Weird.

Princeofwands: There are some good docs on Novell about timesync. I always used timesync.cfg files, which aren't complicated once you read up on how to use them. Never had a problem once I started doing that.

 

[Shadow07]

CTR - Why should you use timesync.cfg files? Isn't NDS good enough? Why can't NDS use NTP like Windows 2000 does? <-- Shadow givin CTR crap again about NDS and Novell.

 

[spidey07]

shadow,

there are plenty of NTP nlms out there for free!

 

[CTR]

Watch out spidey -- don't get caught in the crossfire of the extensive PM smackdown Shadow and I had on NDS and AD.

Fact is, of course, that Spidey is right and even Novell provides NTP. But when you really want to do it right, like with smart companies who use the tried-and-true NDS, NTP for your primary servers to sync their clocks and all secondaries need to be getting their time specifically from the primaries. C'mon Shadow...I know you like to serve 'em up to me but at least put some spin on it!

 

[Shadow07]

Oh no! It's coming back to me! What ever guys.

I'm just shooting the crap at ya. I know that there are NLM's for NDS. I was just giving CTR crap because he said that he had to write cfg files to get timesync to work. With Windows 2000 and Active Directory, just run NET TIME /SETSNTP:ipaddress_ordnsname and that will set NTP and the correct time. But you all know that AD doesn't use Time for AD sync, right? The only thing used for time is Kerberos (not NTLM anymore).

Come on. And you call yourselves IT Professionals. Man, pathetic; just pathetic.

(Shadow is now ducking for all of the flack and flames that are about to shoot his way!)

 

[layne151]

Whoa you guys lost me there! Here is an update i hooked up the old server ( p75, see why i updated it) and the server and bios both reported correct time. I am using the same software VER 4.1 on a p2 300 and am now getting thre problem were my server date is 1988, everything else time/month day is fine. annot get the correct year.