If skip tries to get the MTU value on initialisation of the machine, the
ndsiwan driver won�t know a bit about the coming MTU Size for the next
WAN Session. It will negotiated during the ppp dial up (In our case 1500
Bytes).
Skip probably has to answer the NDIS_STATUS_WAN_LINE_UP request from the
TCPIP Driver. The ndiswan seems to ignore any static MTU settings in the
registry.
Fo skip to work properly with ndiswan it should follow the Line
Management requests form ndiswan modify them and hand them over to the
IP Stack.
Just a guess
Markus
--------
[EMAIL PROTECTED]
always cc to: [EMAIL PROTECTED]
DeTeSystem
Branch Office Cologne
