But, I cannot get Daniel Krue's TreeHugger to communicate with the same LaserJet networked printer despite my best efforts.
I tried it with both my Direct Connect PostScript driver (patched
LaserWriter driver) as well as with the Harmonie LJIII driver. I get absolutely nothing. No activity at all. But, the GS does not lock and it would appear that the job was 'sent'.
What surprises me is that I assumed I would see some communication
backward from the printer to GSPort, but it all appears to be one-way. Contrast that to printing from Windows applications where clearly
Wireshark shows comm in both directions.
Can any of you network savvy guys offer some insight into why the
emulated Uthernet in GSPort is having issues when using the TreeHugger TCP/IP printer port driver?
Using Kelvin Sherlock's TCP Snooper CDA, it shows that an ipid has been assigned, that the connection has been 'Established' to the proper
addresses and ports, and that the Send Queue has content, but nothing 'happens'.
So, I did a Wireshark dump on the activity between GSPort
(192.168.1.3:1025) and the network printer (192.168.1.170:9100), and it appears that data is actually being sent, but for some reason unknown to
me, it is being re-transmitted as though it's not being acknowledged.
Here's part of the dump:
Source Destination Proto Len Info -------------------------------------------------------------------------- 192.168.1.3 192.168.1.170 TCP 54 1025 → 9100 [SYN] Seq=0 Win=16384 Le 192.168.1.3 192.168.1.170 TCP 54 1025 → 9100 [ACK] Seq=1 Ack=1 Win=16 192.168.1.3 192.168.1.170 IPv4 1514 Fragmented IP protocol (proto=TCP 6, 192.168.1.3 192.168.1.170 IPv4 1514 Fragmented IP protocol (proto=TCP 6, 192.168.1.3 192.168.1.170 IPv4 1514 Fragmented IP protocol (proto=TCP 6, 192.168.1.3 192.168.1.170 TCP 1454 [TCP Window Full] 1025 → 9100 [ACK] 192.168.1.3 192.168.1.170 IPv4 1514 Fragmented IP protocol (proto=TCP 6, 192.168.1.3 192.168.1.170 IPv4 1514 Fragmented IP protocol (proto=TCP 6, 192.168.1.3 192.168.1.170 IPv4 1514 Fragmented IP protocol (proto=TCP 6, 192.168.1.3 192.168.1.170 TCP 1454 [TCP Window Full] [TCP Retransmissio
What surprises me is that I assumed I would see some communication
backward from the printer to GSPort, but it all appears to be one-way. Contrast that to printing from Windows applications where clearly
Wireshark shows comm in both directions.
And, just to make certain that this isn't a firewall problem, I disabled
it completely for testing.
At this point, I'm way beyond my network knowledge skills. Any suggestions?
Thanks.
Hugh Hood
On 7/12/2020 12:02 PM, Hugh Hood wrote:
But, I cannot get Daniel Krue's TreeHugger to communicate with the same LaserJet networked printer despite my best efforts.
I tried it with both my Direct Connect PostScript driver (patched LaserWriter driver) as well as with the Harmonie LJIII driver. I get absolutely nothing. No activity at all. But, the GS does not lock and it would appear that the job was 'sent'.
Hugh Hood <hughhood@earthlink.net> wrote:
What surprises me is that I assumed I would see some communication
backward from the printer to GSPort, but it all appears to be one-way.
Contrast that to printing from Windows applications where clearly
Wireshark shows comm in both directions.
Hi Hugh,
My guess is that the printer is dropping the packets for some reason.
Perhaps it needs a certain option that is not implemented by Marinetti.
Can you capture an exchange that does work and then we can see what it is doing that may be different?
Regards
Andrew
What puzzles me is that FTPing to the same printer (different port) with Ewen's SAFE2 within GSPort works just fine.
I finally got around to using the pre-configured disk image (thanks Ewen
and David) for GSPort that contains Marinetti and the Uthernet LL.
I installed Win10Pcap on my Windows 10 box and configured the TCP/IP
Control Panel.
On 7/12/2020 1:02 PM, Hugh Hood wrote:
I finally got around to using the pre-configured disk image (thanks Ewen
and David) for GSPort that contains Marinetti and the Uthernet LL.
I installed Win10Pcap on my Windows 10 box and configured the TCP/IP
Control Panel.
Win10Pcap and the recommended replacement for it, npcap don't work
correctly with GSport. Spin up a Windows 7 VM, install WinPcap 4.1.3 and
test there. TreeHugger does work with GSport as I have tested it in the
past.
BTW, are you able to test TreeHugger with GSPort currently and let me
know how it goes? Thanks.
On 7/25/2020 11:10 PM, Hugh Hood wrote:
BTW, are you able to test TreeHugger with GSPort currently and let me
know how it goes? Thanks.
I did exactly that today while packet tracing the derpy LaserWriter
driver's AppleTalk comms. I was able to get TreeHugger printing to my HP color LaserJet. No drama whatsoever.
Very interesting. Thanks for going to that trouble for me.
A few more questions, if I may ...
Was this on Windows 10?
Was this GSPort v0.31?
I assume you're using one of the Harmonie drivers?
Is this version 1.0 of TreeHugger?
Is there a wired router between the LaserJet and the machine running
GSPort?
Wireshark (if it can be believed) is showing that the packet size coming
from TreeHugger is 6,000 bytes, which seems like it would be 4X what it should be. I guess I'll keep fiddling, not because it's worth it, but
because it bugs me when things don't work.
...could this happen to others? Is reducing the segment sent by
Marinetti the real root cause? Should the size be set
manually/automagically? Why does it work on all machines but ours?
I’ve asked Ewen to take a look at exposing a configuration setting. I thought there was one already.
Regards
Andrew
On 8/4/2020 8:17 PM, Andrew Roughan wrote:
I’ve asked Ewen to take a look at exposing a configuration setting. I
thought there was one already.
On 8/4/2020 8:17 PM, Andrew Roughan wrote:
I’ve asked Ewen to take a look at exposing a configuration setting. I
thought there was one already.
https://sourceforge.net/p/marinetti/feature-requests/40/
and thank you the three of you!
To recap and relate this back to this particular thread -- I've found it necessary to set the Uthernet link layer MTU to '320' in order to use
Daniel Krue's 'TreeHugger' GS/OS Printer Port driver (AppSocket /
JetDirect / Raw-Port9100 protocol) when running GSPort under Windows 10
using its emulated Uthernet card and printing to a networked HP LaserJet JetDirect 600N/3113A print server.
FWIW, I am running a JetDirect 635N along with Windows 7 and GSport 0.31
with the last revision of WinPCap and AppSocket printing works fine with
the default MTU. Never had a problem with it. It also worked with the JetDirect 615N card until the card failed like the rest of them did
(known hardware flaw).
On 8/12/2020 3:41 PM, Christopher G. Mason wrote:
Whether I ever will find that person remains to be seen. BTW, (I 'new'
to Windows), is Windows 7 still being supported by Microsoft? I ask
because I still run across quite a few people who are using it.
On 8/12/2020 9:29 PM, Hugh Hood wrote:
On 8/12/2020 3:41 PM, Christopher G. Mason wrote:
Whether I ever will find that person remains to be seen. BTW, (I 'new'
to Windows), is Windows 7 still being supported by Microsoft? I ask
because I still run across quite a few people who are using it.
Windows 7 reached EOL in January. GSport needs to be updated for NPCap eventually. GSplus has those changes, but the pre-compiled binaries lack networking support!
On 8/12/20 11:33 PM, Christopher G. Mason wrote:
On 8/12/2020 9:29 PM, Hugh Hood wrote:
On 8/12/2020 3:41 PM, Christopher G. Mason wrote:
Whether I ever will find that person remains to be seen. BTW, (I 'new'
to Windows), is Windows 7 still being supported by Microsoft? I ask
because I still run across quite a few people who are using it.
Windows 7 reached EOL in January. GSport needs to be updated for NPCap
eventually. GSplus has those changes, but the pre-compiled binaries lack
networking support!
I've been meaning to devote some cycles to an updated build of GSport.
Maybe NPCap is a good excuse to get moving. Is there a PR for GSplus
that has NPCap stuff? I'm not sure where those changes are.
https://nmap.org/npcap/guide/npcap-devguide.html#npcap-feature-native-dll
Basically call SetDllDirectory("C:\\Windows\\System32\Npcap\\") so it will use the new wpcap.dll
| Sysop: | Keyop |
|---|---|
| Location: | Huddersfield, West Yorkshire, UK |
| Users: | 293 |
| Nodes: | 16 (2 / 14) |
| Uptime: | 242:15:32 |
| Calls: | 6,624 |
| Files: | 12,175 |
| Messages: | 5,320,202 |