| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 435.1 | | DECWET::ONO | Software doesn't break-it comes broken | Fri Feb 21 1997 12:10 | 7 |
| Pierpa,
Try this - when you create the client, put the string Windows NT
in the architecture field. I think this will workaround the
problem with a V3.2 server on Digital UNIX.
Wes
|
| 435.2 | | DECWET::RANDALL | | Fri Feb 21 1997 12:28 | 3 |
| Also patch 2 for Networker NT V4.3 should help this problem.
-- Rich Randall
|
| 435.3 | Wich patch for INTEL ????? | TRN02::FRASSINO | | Tue Feb 25 1997 02:05 | 15 |
| Rich,
I've found patches related to Alpha and Intel.
The Alpha patches kit contains an entry ( patch 2 ) that can be useful.
Tha Intel Patches kit contains a README that mention 3 files, but
patches 3 doesn't existon the filesystem. Patches 2, in my opinion,
doesn't match my problem. Does patches #3 exist really and can be
useful ??
I point out that my Alpha/Intel are NSR CLIENTS, and I use a
Digital Unix NSR SERVER v3.2 + patches.
Any help will be well accepted !
*8( Pierpa
|
| 435.4 | | DECWET::RANDALL | | Tue Feb 25 1997 12:23 | 13 |
| Pierpa,
Whoops, I made the erroneous assumption that your NT clients were Alpha NT
clients. The problem that you are experiencing is a know bug. There is a
patch for the NT Alpha client and there will be a patch out by tomorrow or
so, that should fix Digital Networker V4.2A-B servers. A patch for the
the V3.2 server will take more time, however. As far as I know there is no
patch for this problem on the NT Intel client. If possible I would suggest
upgrading the server to 4.2B and installing the patch that should be available
in a day or two. If that is not possible then I can back port the patch to
V3.2 but that will take signifigantly more time.
-- Rich Randall
|
| 435.5 | Additional infos. | TRN02::FRASSINO | | Tue Feb 25 1997 22:39 | 12 |
| Rich,
thanks for your reply.Now we have the correct scenario to work on.
You correctly suggest to migrate to a newer version of Unix NSR server,
but in my case the situation is a little bit more complicated.
Infact, I'm also working on a Field test for NSR-HSM, and I'll have to
upgrade to v4.0x (Digital Unix OS) and new NSR-HSM (v4.2C) in the
future; inaddition I've ~150 workstations as clients (100 Alpha, 20 Sun
and 30 HP).As you can see an additional upgrade now to guarantee PCs
backup is really a risk.
Let me know how we can go ahead, anyway.
Thanks a lot for your help!
*8) Pierpa
|
| 435.6 | | DECWET::FARLEE | Insufficient Virtual um...er.... | Wed Feb 26 1997 10:06 | 13 |
| Pierpa,
What Rich is telling you is that there is a patch avilable for the V4.2B
version of NetWorker (which will function either on 3.2x or on 4.0[a|b]).
If you for some reason cannot upgrade your NetWorker server past 3.2, then
you'll just have to wait. It really is a substantially larger job
to port the fix to the 3.2 code.
As far as the number of clients, I must be missing something: We do not
require that you upgrade all of your clients in order to upgrade your server.
Kevin
|
| 435.7 | | DECWET::RANDALL | | Wed Feb 26 1997 17:54 | 4 |
| RE .-1
>(which will function either on [Digital UNIX] 3.2x or on 4.0[a|b]).
|
| 435.8 | NSR HSM Field Test | DECWET::SDY | I'm late, I'm late... | Wed Feb 26 1997 18:12 | 16 |
| re: .5
Pierpa,
Just noticed your note about NSR HSM Field Test, we haven't heard
from you in quite a while and figured you had opted out. The Field Test is
now closed, and you should be aware that the license paks will expire in
April. You are welcome to try the kit until expiration, but please be aware
that we will have very few resources devoted to answering any FT kit
questions. (we're in the midst of our SSB submittal)
If you have any other questions about NSR HSM, feel free to send me email at
[email protected] or DECWET::sdy
Steven D. Yee
NSR HSM Project Lead
|