Search results for query: *

Randy, Thanks for the follow up, hope you are still checking this thread. I'm still getting this problem, it seems to be something to do with the netware client getting in a knot and not looking to its NWHOST file to find its nearest server. I am pretty sure its not a network card issue and...

The configuration mentioned by TheLad is probably the one, if the server is in this state you will probably see utilization never drops below 40% (usually it should occasionally drop down to single figures). We had a similar problem caused by a different issue, if you have a large number of...

Thanks for the tip randy but the I can simulate this issue by deliberately powering off a machine rather than logging off windows which simulates a crash situation. It is something to do with the netare client not doing any name resoulution to find the tree, i'm still working on it!

Can a DOS client use a NWHOST file? That usually fixes most cannot find server type problems.

I'm not sure about files reappearing after logout/login, does not happen on my W2k clients. Files that have been deleted should only come back after a salvage. On the autopurge, I use a combination of two utilities, cron.nlm (which is standard with Netware 5.1 I think, you just have to load it)...

We are: Netware 5.1 SP 3 Clients Win95/NWCLient 3.30 IP Only There is a entry for our tree in each clients NWHOST file Situation: Sometimes when a client machine crashes or is turned off withough logging off then on an immediate reboot there is no Login GUI. Once in windows if I bring up a...

Thanks for the help, I used the toolkit.nlm and cron.nlm to shchedule weekly purges. (I do not want to set the attibutes to purge as we do salvage files occasionally, I just want to stop a massive amount of deleted files building up which can stop the volumes mounting on startup)

One issue is the %LOGIN_NAME script variable truncates to 8 characters so if you use something like this: Map root H:=SHSYD01\VOL1:\STAFF\HOME\%LOGIN_NAME to map users home drives it will not work with users login names more than 8 characters.

I had the same problem after installing PCanywhere 9, had to go into safe mode and then apply the latest pcanywhere patch. If you cannot even get into safe mode then it looks like a rebuild.

I'm trying to schedule regular purges of my netware server using scheduled tasks in windows 2000 (we create a lot of temp files and if I do not purge regularly the volumes will not mount without a Vrepair with purge deleted files set to yes). The problem I'm having is that in 2000 when I do...

You need to put a line like this: DOS SET WHO="%LOGIN_NAME" in the loging script before you call the batch file. This will set a dos variable WHO which you can then refer to in the batch file e.g if exist c:\autoexec.bat echo "its there">f:\logs\%who%