Does AREV require SPX protocol to run. I have customer who's trying to tunnel IPX thru IP to office in Cal. AREV doesn't work with this configuration and the network person involved seems to think it's maybe because SPX is NOT running.

IP and IPX are quite different.

SPX is a serial version of IPX where the sequence of packets is presumed/required. (I base my assertion re SPX on details from the Novell Netware API, so it may be glib, but you get the idea).

I don't see how there can be two transport layers working seamlessly. Either your application "boards the train" in the red IPX carriages or the blue IP carriages (metaphorically). These carriages are different lengths.

You give no details of the AREV network driver you are using, or the platforms of the host and workstation. This will aid a response. Usually AREV's Netware LH NLM is used as an IPX conduit, or AREV's NT service using named pipes is used over IP connections.

steve@state-of-the-art.com.au

How does your customer perform the tunneling? Did s/he write a protocol layer to do it on the sending side and receiving side to create a real tunnel? Or is it something s/he purchased? This protocol layer would have to take the place of the IP interface on both sides, to encode the IPX transmissions into IP for sending, and from IP to IPX when received. Probably not much of a change in what's being transmitted, but a very serious chunk of coding/testing.

It seems much easier to use the more typical network interfaces. They are probably re-inventing the wheel, and adding much unwanted complexity.

View this thread on the forum...