| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 4076.1 | | UTRTSC::SWEEP | I want a lolly... | Mon Dec 16 1996 03:43 | 8 |
| 4076.2 | | UTRTSC::SWEEP | I want a lolly... | Mon Dec 16 1996 03:46 | 4 |
| 4076.3 | | COPHK::copvm5.dmo.dec.com::Jesper | The Viking | Tue Dec 17 1996 03:10 | 16 |
| 4076.4 | It's a MS problem | COPHK::copvm5.dmo.dec.com::cop01::jesper | | Tue Jan 28 1997 05:57 | 11 |
|
The problem is now acknowledged and identified by Microsoft.
The problem also exists in NT. The problem is again that MS TCP
dont like GROUP names, but only if using WINS. Their netbios
over TCP is a two legged 'monster', that goes left if using
WINS and right when not using WINS. Thats why it works in one
config and not in the other.
Jesper
|
| 4076.5 | | VMSNET::P_NUNEZ | | Wed Mar 12 1997 16:17 | 12 |
|
Can someone confirm that this WINS/PATHWORKS cluster alias problem will
also prevent an Win95 or WinNT client from validating their domain
logon request if the server responding to the netlogon request is a
PATHWORKS cluster?
From my understanding, during the netlogon request the client does a
FindName to resolve the cluster alias name (it gets back in a response
to it's multicast). Does the client respond to this findname response
and succeed in being validated by the cluster?
Paul
|
| 4076.6 | | UTRTSC::SWEEP | I want a lolly... | Thu Mar 13 1997 04:01 | 9 |
| From my perception WINS will only cache unique names.
The PW cluster alias is therefore not cached and not
translated by WINS. This means that the client will do
a findname request to locate the PW cluster alias.
Now I must tell you that until now I only read about it
and not work with it yet.
Adrie
|
| 4076.7 | 2nd try | VMSNET::P_NUNEZ | | Thu Mar 13 1997 09:35 | 7 |
|
And my question was:
When the client does the findname request during the net logon process,
will this WINS/NETBIOS group name issue cause it to fail?
Paul
|
| 4076.8 | | UTRTSC::SWEEP | I want a lolly... | Fri Mar 14 1997 10:47 | 4 |
| net logon doesn't do a findname....
adrie
its mailslot broadcast
|
| 4076.9 | | VMSNET::P_NUNEZ | | Fri Mar 14 1997 12:47 | 16 |
| Anyone ever traced a Win95 domain logon?
I'm still at a loss as to why:
1. A cluster member that is NOT the active NETLOGON server, but on
which PW was obviously NOT responding, is hanging clients during domain
logon validation.
2. When they force the PW cluster alias name over to a member that IS
responding, the clients have no problem logging on to the domain.
I'll do my testing and be back with results...
Paul
|
| 4076.10 | | CPEEDY::wells.lkg.dec.com::wells | Phil Wells | Fri Mar 14 1997 13:42 | 2 |
| This sounds very much like an old IP cluster alias problem. Are you
using TCP and what version of PW?
|