I was wondering the same thing. This server has 256meg of memory. I
have set the GWIA link to the POA back to the way it was and will see
if it continues. I have other servers in the county and they are all
the same. None of the others have starting getting the IPXF error.
This is what makes me think it might be a hardware issue.
However; you answered my question....! What is IPXF. This is what I
could not find on Novell's sight. Now that I know it is fragmentation,
I have more to go on.
Thank you.
* Sent from Novell Discussion Forums http://novell.remarq.com The Internet's Discussion Network *
The fastest and easiest way to search and participate in Usenet - Free!
Hi Russell,
> However; you answered my question....! What is IPXF. This is what I
> could not find on Novell's sight. Now that I know it is fragmentation,
> I have more to go on.
It is even more than that. I couldn't find a list of things IPXF takes care of, but it is essentially
the most important module for the IPX communication...
Sorry for not being more helpful. I would seriously investigate an hardware issue...
--
Cat
Novell Support Connection Volunteer
thanks for the feedback. I was aware of compatibility issues between BM
2.1 and client versions higher than 2.2, but I have never seen them
crashing the server!
I guess it depends a lot on the environment. I will keep that in mind!
Thanks!
yes, I know that TID quite well, but it doesn't say that using the wrong
client will cause an abend of the server.
Even before the patch, you could only use client 2.2 and 2.5 with BM2.1.
I have seen problems with the wrong client versions a number of times,
but they never caused the server abend. It is good to know that probably
the abend is the ultimate result of this incompatiblity!
Thanks for your feedback.