| Title: | Kit: Note 4229; Please use NOTED::PWDOSWIN5 for V4.x server |
| Notice: | Kit: Note 4229; Please use NOTED::PWDOSWIN5 for V4.x server |
| Moderator: | CPEEDY::KENNEDY |
| Created: | Fri Dec 18 1992 |
| Last Modified: | Fri Jun 06 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 4319 |
| Total number of notes: | 18478 |
PW vms 5.0e
digital ucx 4.1
I need to known the official answer to this If you have a NT 3.51 sp5
workstation as a client can it use the pathwork alias and under which
protocols.(netbeui,decnet,tcp/ip).
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 4256.1 | Works for me ;o) | VMSNET::P_NUNEZ | Wed Apr 09 1997 18:11 | 22 | |
Well, I don't have service pak 5, but my NT 3.51 client is able to make
a share connection over TCP/IP using the PATHWORKS cluster alias name.
I know the WfW IP stack won't work (a MS issue).
I've seen notes in this conference indicating Win95 and WNT v4.0 IP
won't work if WINS is enabled (again, a MS issue).
Perhaps the IP stack in sp5 is similar to that in nt v4.0???? and
so sp5 suffers the same problems????? My inclination, though, is that
the nt v4.0 ip stack is all new, but I'm not sure...
One thing you might try - from a cluster node running pwrks do:
$ nbshow knbstatus <nt-client-computername>
Do you get a response?
Can the NT client connect if it uses a specific hostname instead of the
alias name? Does $ NBSHOW KNBSTATUS list the alias name?
Paul
| |||||
| 4256.2 | KAOFS::M_VALLEE | csc hull canada | Thu Apr 10 1997 15:39 | 6 | |
the
nbshow knbstatus does not work i tried it in our lab and none of the
working pc respond.ANd yes the client can connect by the node name
only.
| |||||