I have always, for security reasons avoided binding File and Print Sharing for Microsoft Clients to TCP/IP in my small office network. With Windows 2000 I used instead NetBEUI and now with Windows XP I am using the NWLink IPX/SPX NetBIOS Compatible protocol for File and Print Sharing. Recently I have been trying to implement the Norton Ghost Recovery CD, which enables one to boot the computer with a Windows PE based bootable CD, and access a drive image stored on another machine on the network and restore that image to the machine with a damaged Windows installation. Symantec has made a custom Recovery CD for me which included the Network adapter drivers which were not included in the shipping product for my Intel and 3Com Ethernet adapters.
Since they are in the mood to make custom CD's for me, I would like them to also include the IPX/SPX protocol since their boot CD currently requires File and Printer Sharing for Microsoft Networks to be bound to TCP/IP on the machine containing the image files in order to connet to it from the machine you are booting from the Windows PE based Recovery CD.
So my main question is what files would they have to add to the CD in order to enable IXP/SPX to work also, and in order for me to understand what is involved to explain it to them I need to know some more about IPX/SPX. There seems to be very sparse documentation about this in the Microsoft Technet or on Novell's site.
One question I would like to know is how IPX/SPX routing is implemented. Since it doesn't use IP address based routing what does it use?
I have four machines connected to a LinkSys BEFSR81 Cable DSL Router, using the router as a DHCP server which dynamically assigns private IP addresses to the machines in the range 192.168.1.10X.
I have discovered that supposedly you can see the configuration of your IPX/SPX routing by typing "ipxroute /config" at a command prompt. When I do that, I get a table like this:
Num Name Network Node Frame
0. Internal 79f52926 000000000001 [None ]
1. IpxLoopbackAdapter 79f52926 000000000002 [802.2]
2. Local Area Connection 00000000 000fd61b7fa9 [802.2]
3. NDISWANIPX 00000000 e4d020524153 [EthII] -
- down wan line
That table is garbled by line wrap, but those of you with expertise in this area will understand it I think.
I had installed and activated the RIP Listening service... you have to install RIP Listener from Windows Components additional networking features. and also in Windows Firewall (if you use that) Microsoft says in their Help that you have to go to the Windows Firewall
Exceptions Tab to open UDP Port 520 with the Name "520 port opening for RIP Listener" and then [My improvement] click the "Change Scope" button and set it for "My Network (subnet only)".
Discovering this made me wonder... where *does* the routing information come from when I am using an IPX/SPX protocol?
If I enable the connection log in my LinkSys router and examine the outgoing connections log, I see something like this:
LAN IP Address Destination URL/IP Port
192.168.1.101 22.214.171.124 520
192.168.1.102 126.96.36.199 520
192.168.1.103 188.8.131.52 520
192.168.1.104 184.108.40.206 520
What would this Destination URL/IP of "220.127.116.11" be? It is not pingable....
When I read all the documentation I can find on IPX/SPX routing, it appears that there must is some sort of addressing aside from name resolution, but what that is or how to use it I can find no information about.
I also appear to be seeing contradictory information about whether I need to be using the SAP (Service Advertising Protocol) under Windows or not.... some places seem to indicate I need it for IPX/SPX and other places seem to say that I only need to use that if I am actually connecting to a Novell network.
I have looked for books on this subject I could buy, but have found none that seem to go into this topic in the depth or detail I need on the inner workings of this protocol to be able to really understand it, so I hope someone with experience in this area can explain it to me or point me to a publication that I can obtain. Aside from wanting/needing to understand the operation for my own network stability, if I hope to be able to get Symantec to implement IPX/SPX on their recovery CD I need to know exactly what to tell them to do, as in put File X here and File Y there, etc.
I would be very appreciative of any help this group can provide me!
Free Guide: Managing storage for virtual environments
Complete a brief survey to get a complimentary 70-page whitepaper featuring the best methods and solutions for your virtual environment, as well as hypervisor-specific management advice from TechTarget experts. Don’t miss out on this exclusive content!