Скачать в pdf «Network+»

IPX RIP is very similar to the RIP protocol in TCP/IP in that RIP for IPX is the distance vector routing protocol for IPX. Similarly, NLSP is the link state routing protocol for IPX/SPX. Both work similarly to their TCP/IP counterparts. RIP uses broadcasts of the entire IPX routing tables to keep all IPX routers updated. And, just like OSPF, NLSP sends out only the changes to the routing tables and then only to a select group of network addresses.


IPX/SPX isn’t as ubiquitous as TCP/IP (which can even be found running on Coke machines), but it holds its own when it comes to allowing many

different platforms to talk. Windows 9x, NT, Me, 2000, NetWare, OS/2, and a few versions of Linux come “out of the box” with support for communicating with other entities via the IPX/SPX protocol stack. Before the popularity explosion of the Internet in the mid-1990s, the IPX/SPX protocol stack was the only protocol stack many companies would run.

The only downside to interoperability using IPX/SPX is that many versions of Unix, or other high-end operating systems like OS/400, don’t come with built-in support for the IPX/SPX protocol stack or even with an option for support.


Really, the only items that have names are the NetWare servers. Generally speaking, you can name a NetWare server anything you want, as long as you follow these rules:

■    The name must not include any of the “illegal” characters, including a period (.), a comma (,), a plus sign (+), an equals sign (=), and a backslash ().

Скачать в pdf «Network+»