Pursuant to this thread I just made, when the NW5.1 Java installer feels like being my friend, and I can get to the point where I can setup networking, I try to do IPX only at first. My thinking is, I want to get it installed into the same tree as my NW4.2 VM image, and get everything installed/upgraded to SP8. Then, I'll install the TCPIP stack and configure that as appropriate.
Problem: the NW5.1 installer apparently doesn't know how to find trees using IPX, from what I can tell. I've got live packet capture using VBox's --nictrace and --nictracefile options, and while I can see all of the NLSP, SAP, IPX RIP, etc, broadcasts coming from my NW4.2 server, I see very little traffic coming out of the NW5.1 server when it does any kind of querying to trees and what not. I am using 802.2 framing (802.3 + LLC DSAP/SSAP = 0xe0), IPX network number 0x00000001, the MAC addresses are 08:00:27:FF:FF:42 for the NW4.2 server (NIMLOTH, ServerID C0A8013E) and 08:00:27:FF:FF:51 for the NW5.1 server (CELEBORN, ServerID C0A8013D), and the tree is called ARDA. In WireShark, I can see, when the NW5.1 installer searches for duplicate server ID's, the following exchange:
So I am reasonably certain that they can see each other. However, after that little exchange, the two won't talk to each other again. The NW5.1 server will send out an IPX RIP occasionally, but when I try searching for the NDS Tree, I get this error back:
"Because of network problems, no NDS tree information is currently available using the browse button. You must type the name of the tree."
Yet even if I type the name of the tree and then attempt to browse by context, I get nothing back either. The only odd thing is the extraneous characters on the Tree name, but that is possibly a WireShark display bug related to parsing IPX SAP. I get similar from IPX SAP packets culled from my old NW6.5 VM Image that died many months ago.
Even if I directly specify the 4.2 server's ServerID, I *never* see ANY IPX queries go out on the wire for that specific ID when probing for the NDS tree. However, if I fire up another NW4.2 install, when I get to the point where I pick an NDS tree, it finds the other 4.2 server's tree without me even asking. So I know I am not doing this completely backwards.
Tips, ideas? Am I doing something wrong w/ IPX? Or do I need to give up on NW5.1 and try NW5.0, NW6.0, or rebuild my NW6.5 server?
Problem: the NW5.1 installer apparently doesn't know how to find trees using IPX, from what I can tell. I've got live packet capture using VBox's --nictrace and --nictracefile options, and while I can see all of the NLSP, SAP, IPX RIP, etc, broadcasts coming from my NW4.2 server, I see very little traffic coming out of the NW5.1 server when it does any kind of querying to trees and what not. I am using 802.2 framing (802.3 + LLC DSAP/SSAP = 0xe0), IPX network number 0x00000001, the MAC addresses are 08:00:27:FF:FF:42 for the NW4.2 server (NIMLOTH, ServerID C0A8013E) and 08:00:27:FF:FF:51 for the NW5.1 server (CELEBORN, ServerID C0A8013D), and the tree is called ARDA. In WireShark, I can see, when the NW5.1 installer searches for duplicate server ID's, the following exchange:
Code:
00000001.080027FFFF51 -> 00000001.FFFFFFFFFFFF IPX SAP
General Query
Server Type: Any Service or Wildcard (0xFFFF)
00000001.080027FFFF42 -> 00000001.080027FFFF51 IPX RIP
RIP packet type: Response
Route Vector: c0 a8 01 3e, 1 hop, 2 ticks (111 ms)
00000001.080027FFFF42 -> 00000001.080027FFFF51 IPX SAP
General Response
Server Name: NIMLOTH
Server Type: Unknown (0x021D)
Network: c0 a8 01 3e
Node: 00:00:00:00:00:01
Socket: Unknown (0x9088)
Intermediate Networks: 1
Server Name: NIMLOTH
Server Type: File Server (SLIST source) (0x0004)
Network: c0 a8 01 3e
Node: 00:00:00:00:00:01
Socket: NCP (0x0451)
Intermediate Networks: 1
Server Name: ARDA____________________________\245\314F\353C@@@@@D\205PJ
Server Type: Time Synchronization Server (NetWare 4.x) (0x026B)
Network: c0 a8 01 3e
Node: 00:00:00:00:00:01
Socket: Unknown (0x0005)
Intermediate Networks: 1
Server Name: ARDA____________________________\245\314F\353C@@@@@D\205PJ
Server Type: Directory Server (NetWare 4.x) (0x0278)
Network: c0 a8 01 3e
Node: 00:00:00:00:00:01
Socket: NetWare Directory Server (0x4006)
Intermediate Networks: 1So I am reasonably certain that they can see each other. However, after that little exchange, the two won't talk to each other again. The NW5.1 server will send out an IPX RIP occasionally, but when I try searching for the NDS Tree, I get this error back:
Quote:
"Because of network problems, no NDS tree information is currently available using the browse button. You must type the name of the tree."
Even if I directly specify the 4.2 server's ServerID, I *never* see ANY IPX queries go out on the wire for that specific ID when probing for the NDS tree. However, if I fire up another NW4.2 install, when I get to the point where I pick an NDS tree, it finds the other 4.2 server's tree without me even asking. So I know I am not doing this completely backwards.
Tips, ideas? Am I doing something wrong w/ IPX? Or do I need to give up on NW5.1 and try NW5.0, NW6.0, or rebuild my NW6.5 server?