My Novell 5.0 Server has correct time but all my clents won't update!

[1085]

I ran ran Dstshift.nlm like Novell said to.
But it tells me I don't need the update.
Also I used the set time command to set the correct time on the server and when I did, and type in the command time at the console the time at the server is correct. But all my flamin win98,me and xp clients! keep getting put 5 hours hours behind when they are rebooted. I also patched all workstations with appropriate MS updates and patches, they all still won't freakin take the correct time from the server! What in the world can I do to fix this other than upgrade to Novell 6? I have two sites with Novell six and those particular sites have no time problems.

Help!

Thanks for your Help,
Bill

 

[marvhuffaker]

There are lots of ways to stop the beeping, some are better options than others..

- Turn server off and submit your resignation
- Put the server somewhere you can't hear it
- Unplug the PC speaker
- Fix the problem, like as terry said, declare a new epoch.
- Wait for the problem to fix itself, probably within a few hours. (Guessing 5)



Marvin Huffaker, MCNE

http://www.redjuju.com

 

[1085]

The first two suggestions are not an option.
I also remember loading dstshift.nlm before the beeping started. I might try the command unload dstshift. But I am not 100% sure that is causing the beeping. I just know that I didn't need that patch because the server told me it wasn't necessary as soon as I loaded it. But I do know not long after loading it, being unable to set the time that is when the beeping started. declare a new epoch? What does that mean? How do I do that? is that some kind of Novell language I still don't yet understand? What is the syntax and command I need to use to do that? Should I also put the command in Autoexec.ncf? or another file? You see I got into IT around the year 2000 and my first couple of jobs had me working with Novell 5. But then in 2001 a lot of companies started migrating to NT4. I think by the year Win2k Server was released with AD Novell was almost buried. That is why am am MCSE certified and not CNA or CNE certified. so it has been 8 years before my current job, I touched a Novell server. I bought an out of print novell 5 book and read it cover to cover to refresh my memory before accepting this job a month ago. Creating users groups and ous in nds with nwadmin has been a snap so far. Yesterday I installed the latest version of Macafee Netshield on one of my sites Novell servers. I also know how to Administer Linux web servers cause two jobs ago I worked for a web host.I didn't even know Novell 6 existed till one day I accidentally clicked a link and it brought me to Novells website. I will run NWdeploy.exe fom the route of the Novell 6.5 cd and plan to upgrade my novell 5.0 server soon. Out of curiosity I also found and purchased the last copy of the Novell administrators Handbook from Novell press for novell 6 from a local Barnes and Noble. I read that I need to have a 200 meg Dos partition to do an in place upgrade. Since I previously didn't use Dos or Novell for a while. I was wondering how do I check the dos partition size? fdisk then an option in fdisk? or is there a way to run a command when novell is loaded to check my Dos partition size. Thanks again for your help,
Bill

 

[1085]

I am also thinking of switching gears to study for Novell suse certification thinking that netware might eventually disappear. Now that Novell and microsoft are working together suse might be a better option than RHCE. Which I read a book on but stopped and started reading the last two netware books before starting this job. The new network war is Linux vs. Windows. Netware isn't even a player. If you go to any Barnes and Noble you see one big Linux section and one big windows section. In computer books section. Some nonprofits lawoffices and government agencies however continue to maintain their Novell and Groupwise servers.
I may upgrade a few servers to Novell 6 but my main focus will probably be on maintainance. Do you think we will ever see a Novell Netware 7? Or is this the end of the line for Netware and the Bigger and better platform becoming Suse Linux?

 

[LawnBoy]

Have you even read the docs that came with dstshift.nlm?

 

[1085]

Yes I actually skimmed over it. when i tried to load it it was useless the server coplained it didn't need it but I believe after that using load dstshift.nlm the beeping started or it could be after loading timesync.nlm. But I know using unload timesync doesn't stop it. So my next guess is to try unload dstshift to see if it is still loaded. all it does every 15 minutes is display Synthetic time is being issued on partition "t=new_start group" and then beep. 15 minutes later Synthetic time is being issued on partition "t=new_start group"
then beep again. There are no other error messages.
Also just to clarify I already set the time with the set time zone command and that fixed the time issue. And I put it in the autoexec.ncf at the bottom of the file. I really don't think where it is in the file matters Just like a command in autoexec.bat as long as it is there. And yes autoexec.bat on the dos partition does need a cd nwserver
server.exe command to start. That is one thing I don't forget about novell cause I installed a 5.0 box before.
Just curious why Novell is dependant upon dos at least for the initial install still in version 6. When Microsoft and Linux servers are not. Or I think it said with an eltorito bootable cd rom it might be able to be installed without a dos partition?

Thanks again for your help,
Bill

 

[TheLad]

It does matter where the timesync statements go, they need to go at the top of the AUTOEXEC.NCF

Have you restarted timesync (or the server) since this all started?

--------------------------------------
"Insert funny comment in here!"
--------------------------------------

 

[jees5]

Are you using Client 32? If so go to client property and change it to stop getting the time from the server.

 

[1085]

yes several times but it still wouldn't stop beeping.
but something weird if i set my server an hour back all my clients except one xp pro pick up correct time. But if i set correct time on server that one pc gets correct time and all others are off.

 

[marvhuffaker]

Jees5 - that's a terrible idea. Getting time from the server is the best way to keep consistent time throughout an organization. Just make sure the server time is right and everything else just works. Why would you want your workstations to be managed individually.

<quote>1085: But it tells me I don't need the update.</quote>
It told you it didn't need it because you didn't have your time zone setup correctly. If you would have had it setup correctly, it would have worked just fine. Now that you have it set correctly (assuming you made that happen), you could run it again and it would actually do something. I brought this up the first time I replied to your post -- go back and look (don't just skim it).

I was thinking about having you do a DSREPAIR -XK2 --> Repair, but that would be cruel.. I wouldn't recommend running that. Repeat, do not run DSREPAIR -XK2.

You need to read through this link:

http://www.novell.com/coolsolutions/feature/17227.html

Don't just skim it. it has the answer you are looking for. Something about an epoch that has been mentioned a couple times here.






Marvin Huffaker, MCNE

http://www.redjuju.com

 

[TheLad]

Are you using Client 32? If so go to client property and change it to stop getting the time from the server.

And how exactly would this resolve the time synchronisation issues on the server?

The link that Marv has posted above should get you sorted. Like he said, read through it but digest it first then perform the required actions. By the way, do you have a time source setup for yourt organisation? How many servers do you have in your DS?

--------------------------------------
"Insert funny comment in here!"
--------------------------------------

 

[1085]

You don't listen I really don't care if the server is an hour behind because this is the first time since dst, all clients have correct time. the beeping is being caused by

DS-7.51-27
Synthetic time is being issued on partition "t=new_start group" synthetic time error if I could get rid of the beeping right now it is working just fine.

 

[1085]

I also already mentioned that the dstshift.nlm was rejected by a message saying it was not needed by the server.

 

[TheLad]

So how did you get on following the information in Marv's link?

--------------------------------------
"Insert funny comment in here!"
--------------------------------------

 

[1085]

I already tried dsrepair -a and when I set a new epoch, it gives me a 601 error. then the command says copleted successfully. Back to square one server is still issuing synthetic time and beeping after it issues the message.
Is there any other way to stop the server from issuing synthetic time? It is definitely causing the beeping.
Thanks,
Bill

 

[marvhuffaker]

Dude you have to troubleshoot the issues. Declaring a new epoch is nothing, but a 601 error means an NDS object is not found. Probably a server object. You got bigger problems than you think. You need to go through that entire document - STEP BY STEP. If you get errors in the first step, troubleshoot and resolve before moving to the next one. And so on.

I also have a 30 thread rule. After 30 threads, it's time to call Novell, my office, or some other qualified consultant to help. You're running in circles on some issues that could most likely be fixed in under an hour. But you are ignoring or skimming many suggestions that have been made, so it's pointless to continue here.


Marvin Huffaker, MCNE

http://www.redjuju.com

 

[terry712]

as marv says you need to go through step by step

declaring an epoch is not something you do on a whim or you will be using an xk2 (an again - DONT RUN THIS - it bleach and will not fix this)

you need to find the future date stamp - if it aint too far then nothing critical but not good, too far and major problem

how many server's in tree?
mixed ds?
how's your sync?

go through the basic before you start using command that you dont understand