Dear gentlemen,
on and off, with Bryan we've been playing with Ubuntu, Samba, CUPS
and the MS Network Client running in FreeDOS. And we're facing a dead
end - same symptoms observed by me and by Bryan:
We can load the MS stack, to the point that we can "net use" network
disk volumes = map a local drive letter to an ARC path from the
server. And the disk is perfectly accessible.
But, printing is giving us an interesting misbehavior.
We can ask for
net use LPT2: \\server\printqueue
That does succeed. But, whatever we copy to the redirected LPT2
(we've also tried LPT1 for that matter), we only get a couple lines
printed. Like 4 to 6 lines, if we try to print plain text.
I've observed the problem with Wireshark. The MS client connects a
TCP session to Samba, they negotiate the protocol version, the client
starts a print request, sends the first packet with an actual
payload, gets a TCP ACK, and the very next TCP packet from the client
to the server has a FIN flag - and the TCP session get gracefully
ended. Interestingly, the client produces one extra packet with an
ACK for the session, after the FIN / FIN+ACK coordinated handshake
has closed the session. Wireshark's TCP tracing marks that extra ACK
packet as a duplicate...
I have no clue why this is happening. I've tried loading all the
drivers "low" (instead of "high" or UMB). No joy.
I'm wondering, which of the bunch of drivers and executables (about 8
of them) is specifically responsible for the printer port redirection
function. And, what could make it close the TCP session prematurely.
Does it perhaps expect a different "pattern of data writes" on the
hooked LPT port service? Which a plain "copy" command does not
satisfy?
Any ideas are welcome :-)
Frank
_______________________________________________
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user
