On Wed, Jul 27, 2016 at 7:10 PM, Jose Maria Terry Jimenez <jtj(a)tssystems.net
wrote:
> El 27/07/16 a las 15:22, Manish Kathuria escribió:
>
>
>
> On Wed, Jul 27, 2016 at 9:00 AM, Tim <ignored_mailbox(a)yahoo.com.au
wrote:
>
>> Allegedly, on or about 26 July 2016, Manish Kathuria sent:
>> > The D-Link documentation suggests specifying
>> >
http://172.16.100.1:631/printers/HP as the Printer URI. This
>> > configuration works very well over the network while using a Windows
>> > system but it does not print at all from the Fedora machine even after
>> > trying various permutations and combinations.
>>
>> I'm going to ask the obvious question: Is your Linux computer in the
>> same subnet as the printer? (i.e. 172.16..)
>>
>>
> Yes
>
>
>> Is that the IP of the printer?
>>
>>
>
>
>
>> For what it's worth, even if it is, browsing to that IP may not do you
>> any good. They may simply have the printer listening, without providing
>> any interface. That's what my HP LaserJet 4M does (it's there on the
>> network, listening and printing, but doesn't provide any kind of
>> interface to the outside world).
>>
>
> Exactly. It does not let me browse.
>
>>
>> Is that the IP of the router?
>>
>
> The printer's IP is the same as the wireless router (i.e. 172.16.100.1 and
> the Linux system is 172.16.100.x)
>
>>
>> In that case, I'd expect that the router is acting as an internet
>> printing server, and ought to have some kind of interface. But you may
>> have more luck going to the root of the server (instead of directly to
>> the printer address), <
http://172.16.100.1:631/>, to see if that gives
>> you an interface.
>>
>> Tried that also, and it did not show anything on the browser. The process
> list on the DLink Router shows a program named ippd running which provides
> the interface to the printer.
>
>
>
> Can you access the router's print server port via telnet?
>
> telnet 172.16.100.1 631
>
> Yes, it works.
If not try disabling the Fedora's firewall.
Also, last week i had a problem with a customer, and it was he configured
a wrong net mask in the Linux box.
I suppose that ping and traceroute to the printserver's IP give the
expected results, did you tried it?
Network connectivity is fine. Probably its just compatibility. I felt that
it
should work since the print server itself (and the router device) is
Linux based.