|
Home > Archive > CNE > May 2001 > Have a Quick ? for u novell gurus
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Have a Quick ? for u novell gurus
|
|
| entrerixxx 2001-05-01, 9:57 am |
| I use a win 95 workstation @ work. I often need to use NwAdmin to manage object within the companys' tree. When I connect to a 4.11 server and run the NwAdmin executable from the server it either takes forever or crashes my machine. I only know a little bit about novell but, I am fairly good at picking stuff up. I placed a shortcut on my desktop that points to the NwAdmin95.exe file located on one of the servers I have rights to. Finally my question is :
Is it possible to have the NwAdmin utility loaded locally on my workstation instead of having to go out onto the network and run it? I know I will probably still have to go out onto the network to retrieve tree info to administer but, I was just wondering if this would be a better way of using NwAdmin95 instead of running it directly from a highly utilized server. Help is greatly appreciated.
Thanks... | |
| chunder 2001-05-01, 10:23 am |
| your computer itself could be the problem... low memory can be a big issue with NWadmn. however, a congested network or overburdened server can also cause your issues.
i haven't done it but have heard of people copying the Win32 directory to the local workstation.
search support.novell.com for more info. | |
| cybatek 2001-05-01, 1:38 pm |
| Windows 95, now thats funny. Next you'll tell me it only has 64 meg RAM 
Yes, your workstation is the problem. But that aside . . .
You need to copy the WIN95 directory (if 4.11, otherwise WIN32 for NW5+) from the server to the PC. You will then be able to run NWAdmin fine and you do off load some of the resource effort of doing admin across the wire.
A word of caution. Be aware that when installing new Novell services (Bordermanger etc.), it is a common for the new app to want to copy Snap-in files to the directory where NWAdmin is.
If this helps, great. But it is probably a symptom of a more complex performance / design problem | |
| chunder 2001-05-01, 1:53 pm |
| hey cyba.. didn't a service pack of some sort move everything to a win32 dir in 4.1x? or was that the zen stuff? cuz i remember at my old gig that was the case... and actually, here, before we upg'd to 5.1, i remembered telling the other admins here to start using the nwadmin in the win32 dir and not the win95 dir... but i can't remember what it was that made it so that was the case... hmmm.
ok. bye. | |
| cybatek 2001-05-01, 2:20 pm |
| Could be. Haven't actually been to any 4x sites in a while.
Caveat Emptor | |
|
| Win95 already a problem by itself.
I agreed that you shall look into the ZEN. It can get you a big headache! | |
| dheinsdorf 2001-05-01, 9:35 pm |
| First things first, and taking into account what the other members have said:
- Dont use NwAdmin95. It was replaced in late 1998 by NwAdmin32. See this originating TID (also has an old rev of NwAdmin32):
http://developer.novell.com/support...min/NWADMIN.HTM
If your 4.11 box is up to the latest support pack (and it should be) then you should have \win32\nwadmin32.exe.
I think we got it prior to the inclusive support pack by installing Zen 1.0 or 1.1 starter pack(s).
We still have 4.10 and up to 5.1 servers, and the ONLY time I use admin95 is because some old GroupWise 5.2 snapins dont work in admin32, so only for that.
You didnt get into details about your workstation crashs but slow Admin startup ranks from normal but bothersome to random client hangs for a zillion possible reasons.
Right off the bat, 95/98/me have only 64 TLS "Thread Local Handles" which NWAdmin will suck up. NT4/2000/XP have 64 of these process threads per application/process. Moral is no matter how buffed your client box is, if its 95a,b,c/98,se,ME it WILL at some point experience an NWAdminXX based problem at some point. Period.
Irregardless of your hardware, switch to NWAdmin32, and if on 95/98 have as little as possible else going on on the client while using admin, close systray, antiviral, anything you can. And make sure your up to Client32 v3.21 SP5. Dont use Client 3.3!
By the way, Win95 AINT your problem if your at OSR2.x with patches. I ran NWAdmin32 for several years on a well tuned P55C200 with 32/48/64 meg. I have been to some NAEC Netware classes where they still use 95.
Also you can go local with NWAdmin, but its really only necessary if you have loads of snapins. I never ran it local with my old workstation on a 10meg shared link.
Finally, please dont take this the wrong way, but if you've been given administrative duties to perform on your tree at work, versus browse only "just looking around" stuff, then you could spend days and days reading the support.novell.com TIDS on NWAdmin alone, not to mention lurking and posting to the www.novell.com/coolsolutions communities forums. You can read all the Novell books in the world and pass any test, but making those sites part of your daily routine is an absolute necessity to working on Novell products. Also \developer.novell.com (all the killer app notes) and www.novell.com\documentation are must have desktop shortcuts.
Regards,
Doug |
|
|
|
|