Quoting Alan Altmark <[EMAIL PROTECTED]>: > Do you have all 3 of the 2.2 IUCV patches applied?
Yup, I tried 2 kernels: One's a kernel I compiled with the 3 patches, and the other is the kernel provided from SuSE (both 2.2.16 of course). > MTU size has nothing to do with connection errors (CTC or IUCV). The > timeout error is what VM TCP/IP displays when the other side doesn't > respond to an IUCV connect within 20 (?) seconds or so, indicating that > the Linux side isn't quite right. You didn't post of VM TCP/IP IUCV > configuration nor the options used on the netiucv module. I only use 'iucv=TCPIP' in the kernel command line. That's it. The weird thing is, that when I open a 3270 session to a machine/user that is stuck, and I press a couple of enters, then "b" in the CP Read, the connection returns to its original state (starts working again). Here's the tcpip configuration (I hope I didn't leave important stuff out :-) : DEVICE VMJGIG OSD F000 PORTNAME GIGPF0 PRIROUTER AUTORESTART LINK VMJGIG QDIOETHERNET VMJGIG DEVICE LNXJMST1 IUCV 0 0 LNXJMST1 A LINK LNXJMST1 IUCV 0 LNXJMST1 192.168.48.20 = LNXJMST1 16384 HOST Thanks a lot for you help! Yuval. ------------------------------------------------- This mail sent through IMP: http://horde.org/imp/
