I need to try to make an embedded scanner AirScan/eSCL compatible. This is a tiny sheetfeed scanner. I have most of the work done, but I am havng issues with the final message exchanges just before the client GETs the scanned image.I can easily enough initiate the scan up to the point of sending 201 Created location URI from there it gets foggy as I have seen AirScan/eSCL Clients that all seem to behave differently. I can make it work in Vuescan but Vuescan does not come back to check ScannerStatus again , it just initiates the download based on header information froj 201 Created and Location: URI.It is specifically this point after sending 201 Created and location URI headers where things are falling apart for me on OSX Mojave.I have seen that OSX mojave requests ScannerStatus again before download but have no idea whet it is looking forI have identified several status messages but not sure even which one applies when the scan is actually ready for download or already downloaded.No matter what I can not seem to make OSX Mojave happy. I figure if I can make it work on Mojave it will probably work on iOS .If anyone has any wireshark traces from a successful scan that may be helpful too. I have a scanner in another city that I was remotely working with but problems with WiFi card not allowing me to see all the traffic on the network so I can see messages to/from real AirScan compatible HP multi function device.Also looking for info on how to identify correctly a SINGLE sheet feeder scanner to OSX, not a flatbed with ADF option .ThanksMark

I have been using Windows 10 with some PHP that I wrote and Bonjour to share a non-AirScan (non eSCL) scanner by way of the eSCL protocol. This has worked fine consistently across many Windows 10 home, and pro (64 bit only) systems that I have tested on. Recently however my primary Windows 10 development machine died (may it rest in pieces). This was always my only dedicated windows machine for testing so I converted a Linux box to Windows 10 Home x86_64. As I previously had tested on Windows 10 Home I saw no potential for issues. I install Bonjour Print services for Windows, and use the following command... dns-sd -R "Samsung SCX-5935NX@eSCL" _uscan._tcp local 8000 "note=Twain2AirScan Version 2.09" "duplex=T" "is=platen,adf" "cs=color,grayscale,binary" "pdl=application/pdf,image/jpeg" "uuid=3508b420-00a0-004e-00b5-002507510abf" "rs=eSCL" "representation=http://10.0.0.149:8000/scannericons/Samsung-SCX-5935NX.png" "vers=2.2" "usb_MDL=Samsung SCX-5935NX@eSCL" "usb_MFG=Samsung" "mdl=SCX-5935NX" "mfg=Samsung" "ty=Samsung SCX-5935NX@eSCL" "adminurl=http://10.0.0.149:8000/index.php" "txtvers=1" This has worked fine till I built this new machine. Now what I see is that it works for up to several minutes then it stops. On my Mac I run... dns-sd -B _uscan._tcp and see... 16:00:52.405 Add    2  7 local.        _uscan._tcp.     Samsung SCX-5935NX@eSCL That is fine usually for several munures then I see... 16:07:22.300 Rmv    0  7 local.        _uscan._tcp.     Samsung __SCX-5935NX@eSCL I see no reason why it should suddenly fail and have not seen this previously after multiple installs. I have disabled Windows Firewall and put UAC control to minimum . This entire project relies on this one small piece of code that now suddenly is failing on one system. This same system BTW was completely rebuilt twice with fresh software downloads of Bonjour Print services for Windows , and I have tested the Bonjour SDK for Windows as well. Normally I would launch this from a VBS script that launches a BAT file , this is to suppress the window. It does not matter how I run it , I have even tried running it from Task manager and it simply fails after several minutes. Originally I would have though there was a way to make a more permanent. configuration rather than a long winded command but I think this is the only way, correct? Anyone know what else I can try? Thanks Mark