| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 264.1 | | VMSNET::mickey.alf.dec.com::s_vore | Smile, Mickey's watching! [email protected] | Fri May 02 1997 08:17 | 25 |
| > PATHWORKS v4.1B on NTv3.51 for their clients. However, connection denied
> errors were found after the above changes; whereas originally using Win95
> clients cause no problem.
after what above changes?
In any case, PW32 really isn't the issue here as it's just providing
the DECnet transport. The question is NT's modern redirector vs. the
ancient PCSA server. Connections can be made with a set of limitations
which are, I believe, documented in a couple of DSNlink/TIMA/STARS
articles. In short, either use all PUBLIC access services, or...
Set your NT Workstation Name (COMPUTERNAME) to an OpenVMS username.
Grant that OpenVMS user access to the share (possibly using groups).
Make the connection to that share before any PUBLIC-Accessable
shares, providing the OpenVMS password.
You can't have these auto-connect.
Note that a PATHWORKS V4 server is not a full LAN Manager server,
but it understands the older MS-Net dialect - with Digital
enhancements - of the SMB (Server Message Block) protocol. In
practice this means that user level security does not exist, no
domains.
|
| 264.2 | PW32 can use PWRK/PCSA server ? | NNTPD::"[email protected]" | HKTS | Thu May 08 1997 03:24 | 14 |
|
What changes ??
I mean Win95 connects to PCSA server without any problem but access denied if
using Winnt351/40 as a client connects to PCSA server.
Besides, should PW32 connects to PCSA (PATHWORKS v4.x) server ? Or PWRK
(v5.x)?
Any limitation between these two servers using PW32 as a client??
:>
[Posted by WWW Notes gateway]
|
| 264.3 | | VMSNET::mickey.alf.dec.com::s_vore | Smile, Mickey's watching! [email protected] | Thu May 08 1997 08:10 | 22 |
| > Any limitation between these two servers using PW32 as a client??
Please re-read my .1 PW32 is ONLY providing the transport - unless
you've got node-based restrictions defined somewhere in NCP, DECnet
can't be causing your problems.
Yes, Win95 clients can use both the old unsupported PCSA v4.x server
and the current 5.0x server.
Yes, NT 3.x clients can use both the old unsupported PCSA v4.x server
and the current 5.0x server.
Yes, NT 4.x clients can use both the old unsupported PCSA v4.x server
and the current 5.0x server.
And yes, as mentioned in .1, there are restrictions. If you want the
best connectivity possible, upgrade your server to the current
version (5.0E eco1 right now) but expect that there will _still_ be
some restrictions because that's a LAN Manager 2.2 server and NT's
effectively LAN Manager 3.x
|
| 264.4 | What about the other way round ? | WOTVAX::oloras12.olo.dec.com::Colin Clowes | Confusion Reigns | Fri May 09 1997 13:10 | 19 |
| Hi,
To finish this topic off:
What about support for using old PCSA clients using DECnet to access File
and Print services on a NT V4 server using Pathworks 32
Specifically
is there any restriction on PCSA V4.1 clients accessing Pathworks 32 NT 4.0
using DECnet ?
Does it work ?
Is it supprted ?
will the DECnet stack cope with 100's users ?
Thanks
Colin
|
| 264.5 | | SPELNK::curless | | Fri May 09 1997 13:48 | 7 |
|
Yes there are restrictions... NOT RELATED to DECnet, just to the differing
versions of the redirector, and what the client and server will negotiate
when connecting. The limitations are VERY SIMILAR to the limitations
between NT and the PATHWORKS v4.x server.
Jeff
|