I'm having trouble with a conflict between TCP/IP and IPX. (For part one of this user's Ask the Expert question and answer, go to https://searchwindowsserver.techtarget.com/answers) I can't remove IPX from all IPX from all machines on this campus (and at satellite campuses) so removing IPX is not likely to happen any time soon. Why does IPX cause this problem with TCP/IP? Has anyone done any network monitoring so that they can determine what the cause is?
One possible workaround -- since I don't know what kind of setup is being used with IPX -- is to force the frame type for IPX. IPX can be set to autosense the frame type; you may want to force it to use Ethernet II (or whatever relevant frame type is being used on the network).
IPX and TCP/IP don't play well together, I suspect, simply because Microsoft's IPX stack in Windows is not very well written. If IPX is required, then the best thing to do might be to swap in a Novell-written version of IPX.
Dig Deeper on Windows client management
Related Q&A from Serdar Yegulalp
This week, our expert answers the question of how to get DVD data off a disc, even if the user's PC doesn't have an optical drive. Continue Reading
This week, our expert answers a question on how to connect a phone or tablet to a USB drive with a micro-USB connector. Continue Reading
Open source and free suites such as LibreOffice and OpenOffice could save organizations money, but not effort in comparison with Microsoft Office. Continue Reading