Path: csiph.com!usenet.pasdenom.info!weretis.net!feeder4.news.weretis.net!eternal-september.org!feeder.eternal-september.org!mx02.eternal-september.org!.POSTED!not-for-mail From: Unknown Newsgroups: comp.sys.raspberry-pi,comp.os.linux.misc,alt.os.linux.debian Subject: Re: HOW2 mobile, headless-rPi connect to LAN-printer? Date: Sun, 29 Mar 2015 22:04:49 +0000 (UTC) Organization: A noiseless patient Spider Lines: 38 Message-ID: References: <20150325180540.5fe7b534@jresid.jretrading.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Injection-Date: Sun, 29 Mar 2015 22:04:49 +0000 (UTC) Injection-Info: mx02.eternal-september.org; posting-host="204d9520eb12dc84eb173fb37efabc04"; logging-data="2538"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX18/lVFDMIa9g72UplO9+Tcw/nFRl2SaRvU=" User-Agent: Pan/0.133 (House of Butterflies) Cancel-Lock: sha1:q4Nl19s2zBlHLIIIqjlRgz3aCg8= Xref: csiph.com comp.os.linux.misc:14269 On Wed, 25 Mar 2015 21:04:14 +0000, Jerry Peters wrote: > In comp.os.linux.misc Joe wrote: >> On Wed, 25 Mar 2015 09:34:41 -0400 >> Dennis Lee Bieber wrote: >> >>> On Wed, 25 Mar 2015 03:13:20 +0000 (UTC), noSpam@gmail.com declaimed >>> the following: >>> >>> >>> >Perhaps if I phone a Win-user, he can tell me if/where his system >>> >shows the printer's IP, and how to ask the office-girl to 'get it' - >>> >from her PC. -- snip -- >> The last one I was involved with was a Ricoh device, that used TCP/9100 >> for 'raw' data, whatever that was. But it could be configured for >> several ports and protocols, including lpr and IPX. >> >> > I have a Brother printer and it does the same, tcp/9100 needs to be > configured for whatever protocol you're using. This seems to be getting close to a solution. Perhaps I can try `ping 192.168.0.9100` But it will be from a headerless rPi, with only an on/off switch. == Let's test the idea from the x86 to the rPi. ~:ping 192.168.0.2 >> /pingTrace ^C~:less /pingTrace PING 192.168.0.2 (192.168.0.2) 56(84) bytes of data. 64 bytes from 192.168.0.2: icmp_seq=1 ttl=64 time=1.18 ms 64 bytes from 192.168.0.2: icmp_seq=2 ttl=64 time=0.433 ms 64 bytes from 192.168.0.2: icmp_seq=3 ttl=64 time=0.481 ms That's a start.