2.2.1.2.94 IPX_STATIC_SERVICE_INFO

The IPX_STATIC_SERVICE_INFO structure MAY<85> be used to carry the IPX server information. When this structure is encapsulated in RTR_TOC_ENTRY (section 2.2.1.2.4), the InfoType value used MUST be 0x00000003.

 typedef IPX_SERVER_ENTRY IPX_STATIC_SERVICE_INFO, *PIPX_STATIC_SERVICE_INFO;
  
 typedef struct _IPX_SERVER_ENTRY {
   USHORT Type;
   UCHAR Name[48];
   UCHAR Network[4];
   UCHAR Node[6];
   UCHAR Socket[2];
   USHORT HopCount;
 } IPX_SERVER_ENTRY,
  *PIPX_SERVER_ENTRY;

Type: Indicates the contents of the payload portion of the IPX packet. It allows a number of client protocols to use the IPX and be identified by the IPX router.

Routers can filter the IPX traffic based on the Packet Type field. For example, some routers by default do not propagate NetBIOS over IPX broadcast traffic and MUST be manually configured to enable packets with a packet type value of 20. The following table lists some common defined values of the IPX packet type.

Value	Meaning
0x0000	Unspecified
0x0001	RIP
0x0004	SAP/Normal IPX
0x0005	SPX
0x0014	IPX WAN broadcast (used for NetBIOS over IPX broadcasts)

Name: A null-terminated Unicode string giving the name of the interface.

Network: This MUST be the 4-byte IPX network number in hexadecimal (8 hexadecimal digits).

Node: Identifies a node on an IPX network. The 6-byte fields can be used to store physical addresses, also known as media access control (MAC) addresses.

Socket: Identifies the software process addresses of the destination and source applications. With multiple processes communicating between the same two computers, the IPX network and node numbers are the same. The IPX socket number is a software process identifier that is used to forward the IPX payload to the proper process.

HopCount: This MUST be the number of routers to be traversed to get to the network number.