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