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 |
T.R | Title | User | Personal Name | Date | Lines |
---|---|---|---|---|---|
4024.1 | UTRTSC::SWEEP | I want a lolly... | Tue Nov 12 1996 03:27 | 6 | |
4024.2 | Additional Info Please | GRANPA::BARABIA | Tue Nov 12 1996 10:25 | 9 | |
4024.3 | UTRTSC::SWEEP | I want a lolly... | Tue Nov 12 1996 10:50 | 22 | |
4024.4 | Still a Little Fuzzy | GRANPA::BARABIA | Wed Nov 13 1996 10:45 | 23 | |
4024.5 | UTRTSC::EISINK | Writting unsaved data to floppy disk. | Wed Nov 13 1996 13:38 | 19 | |
4024.6 | He's what we got | GRANPA::BARABIA | Wed Nov 13 1996 15:16 | 44 | |
4024.7 | UTRTSC::EISINK | Writting unsaved data to floppy disk. | Thu Nov 14 1996 01:23 | 29 | |
4024.8 | New Error Messages | GRANPA::BARABIA | Thu Nov 14 1996 11:55 | 26 | |
4024.9 | NETRIX::"[email protected]" | Paul Smith | Tue Feb 25 1997 04:04 | 8 | |
Has this issue bee resolved ? I have a customer who is experiencing the same problems. Regards, Paul S. [Posted by WWW Notes gateway] | |||||
4024.10 | Netbios bug when FDDI | UTRTSC::EISINK | No Kipling apes today | Tue Feb 25 1997 08:01 | 33 |
Paul, yes this has been resolved. The problem was that part of the netlogon the PATHWORKS cluster alias name , which is a NETBIOS group name', has to be resolved. The find name request is sent out and the logon server sents the response. However when the netlogon is served by a backup domain controller or primary domain controller which has a FDDI controller the source address in the data link header is not AA-00-04-00 but the physical hardaware address. This is a netbios bug when the device is a FDDI device. When the local server sees this it tries to connect to object 64 (LMMCP) and the node name the NETBIOS name which is incorrect, SO, when the logon server is a cluster it can fail when : - The PATHWORKS cluster alias is _NOT_ the same as the DECnet cluster alias. Which is what we recommend. - The PATHWORKS cluster alias is the same as the DECnet cluster alias and the DECnet cluster alias is _not_ defined in the local decnet database. - The machine name of the logon server is _NOT_ the same as the DECnet nodename. So to get this properly fixed open an IPMT and refer to cfs.46593. We've a netbios fix on the shelf. Rob. |