Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #159178 > unrolled thread
| Started by | rlharris@oplink.net |
|---|---|
| First post | 2015-10-15 08:10 +0200 |
| Last post | 2015-10-15 15:40 +0200 |
| Articles | 20 on this page of 75 — 13 participants |
Back to article view | Back to linux.debian.user
direct ethernet connection between computer and printer rlharris@oplink.net - 2015-10-15 08:10 +0200
Re: direct ethernet connection between computer and printer Reco <recoverym4n@gmail.com> - 2015-10-15 08:40 +0200
Re: direct ethernet connection between computer and printer rlharris@oplink.net - 2015-10-15 10:00 +0200
Re: direct ethernet connection between computer and printer Reco <recoverym4n@gmail.com> - 2015-10-15 14:00 +0200
Re: direct ethernet connection between computer and printer Brian <ad44@cityscape.co.uk> - 2015-10-15 15:20 +0200
Re: direct ethernet connection between computer and printer David Wright <deblis@lionunicorn.co.uk> - 2015-10-15 16:50 +0200
Re: direct ethernet connection between computer and printer Doug <dmcgarrett@optonline.net> - 2015-10-15 21:50 +0200
Re: direct ethernet connection between computer and printer rlharris@oplink.net - 2015-10-15 22:20 +0200
Re: direct ethernet connection between computer and printer rlharris@oplink.net - 2015-10-15 22:10 +0200
Re: direct ethernet connection between computer and printer Brian <ad44@cityscape.co.uk> - 2015-10-15 22:40 +0200
Re: direct ethernet connection between computer and printer Lisi Reisz <lisi.reisz@gmail.com> - 2015-10-15 22:50 +0200
Re: direct ethernet connection between computer and printer Brian <ad44@cityscape.co.uk> - 2015-10-15 23:00 +0200
Re: direct ethernet connection between computer and printer Joe <joe@jretrading.com> - 2015-10-15 23:20 +0200
Re: direct ethernet connection between computer and printer Brian <ad44@cityscape.co.uk> - 2015-10-15 23:50 +0200
Re: direct ethernet connection between computer and printer Brian <ad44@cityscape.co.uk> - 2015-10-16 00:20 +0200
Re: direct ethernet connection between computer and printer rlharris@oplink.net - 2015-10-16 01:00 +0200
Re: direct ethernet connection between computer and printer Brian <ad44@cityscape.co.uk> - 2015-10-16 10:30 +0200
Re: direct ethernet connection between computer and printer Joe <joe@jretrading.com> - 2015-10-16 09:50 +0200
Re: direct ethernet connection between computer and printer Lisi Reisz <lisi.reisz@gmail.com> - 2015-10-15 23:40 +0200
Re: direct ethernet connection between computer and printer rlharris@oplink.net - 2015-10-15 22:40 +0200
Re: direct ethernet connection between computer and printer David Wright <deblis@lionunicorn.co.uk> - 2015-10-15 23:00 +0200
Re: direct ethernet connection between computer and printer rlharris@oplink.net - 2015-10-16 00:20 +0200
Re: direct ethernet connection between computer and printer David Wright <deblis@lionunicorn.co.uk> - 2015-10-16 06:10 +0200
Re: direct ethernet connection between computer and printer Reco <recoverym4n@gmail.com> - 2015-10-15 23:00 +0200
Re: direct ethernet connection between computer and printer Joe <joe@jretrading.com> - 2015-10-15 23:20 +0200
Re: direct ethernet connection between computer and printer Reco <recoverym4n@gmail.com> - 2015-10-15 23:30 +0200
Re: direct ethernet connection between computer and printer rlharris@oplink.net - 2015-10-16 00:10 +0200
Re: direct ethernet connection between computer and printer Felix Miata <mrmazda@earthlink.net> - 2015-10-16 00:30 +0200
Re: direct ethernet connection between computer and printer rlharris@oplink.net - 2015-10-16 01:00 +0200
Re: direct ethernet connection between computer and printer Joe <joe@jretrading.com> - 2015-10-16 09:40 +0200
Re: direct ethernet connection between computer and printer rlharris@oplink.net - 2015-10-16 10:20 +0200
Re: direct ethernet connection between computer and printer Joe <joe@jretrading.com> - 2015-10-16 11:40 +0200
Re: direct ethernet connection between computer and printer David Wright <deblis@lionunicorn.co.uk> - 2015-10-16 16:30 +0200
Re: direct ethernet connection between computer and printer Joe <joe@jretrading.com> - 2015-10-15 23:10 +0200
Re: direct ethernet connection between computer and printer rlharris@oplink.net - 2015-10-16 00:20 +0200
Re: direct ethernet connection between computer and printer Pascal Hambourg <pascal@plouf.fr.eu.org> - 2015-10-15 22:10 +0200
Re: direct ethernet connection between computer and printer Reco <recoverym4n@gmail.com> - 2015-10-15 22:40 +0200
Re: direct ethernet connection between computer and printer Reco <recoverym4n@gmail.com> - 2015-10-17 18:00 +0200
Re: direct ethernet connection between computer and printer <tomas@tuxteam.de> - 2015-10-17 21:20 +0200
Re: direct ethernet connection between computer and printer Reco <recoverym4n@gmail.com> - 2015-10-17 23:00 +0200
Mailing lists, CC, followup-to, netiquette and all the rest [was: direct ethernet connection between computer and printer] <tomas@tuxteam.de> - 2015-10-18 09:10 +0200
Re: Mailing lists, CC, followup-to, netiquette and all the rest [was: direct ethernet connection between computer and printer] Reco <recoverym4n@gmail.com> - 2015-10-18 12:10 +0200
Re: Mailing lists, CC, followup-to, netiquette and all the rest [was: direct ethernet connection between computer and printer] <tomas@tuxteam.de> - 2015-10-18 17:40 +0200
Re: Mailing lists, CC, followup-to, netiquette and all the rest [was: direct ethernet connection between computer and printer] Lisi Reisz <lisi.reisz@gmail.com> - 2015-10-18 18:00 +0200
Re: Mailing lists, CC, followup-to, netiquette and all the rest [was: direct ethernet connection between computer and printer] <tomas@tuxteam.de> - 2015-10-18 18:30 +0200
Re: Mailing lists, CC, followup-to, netiquette and all the rest [was: direct ethernet connection between computer and printer] Brian <ad44@cityscape.co.uk> - 2015-10-18 21:00 +0200
Re: Mailing lists, CC, followup-to, netiquette and all the rest [was: direct ethernet connection between computer and printer] Lisi Reisz <lisi.reisz@gmail.com> - 2015-10-18 21:20 +0200
Re: Mailing lists, CC, followup-to, netiquette and all the rest [was: direct ethernet connection between computer and printer] <tomas@tuxteam.de> - 2015-10-18 22:00 +0200
Re: Mailing lists, CC, followup-to, netiquette and all the rest [was: direct ethernet connection between computer and printer] Chris Bannister <cbannister@slingshot.co.nz> - 2015-10-19 05:50 +0200
Re: Mailing lists, CC, followup-to, netiquette and all the rest [was: direct ethernet connection between computer and printer] Joe <joe@jretrading.com> - 2015-10-19 09:30 +0200
Re: Mailing lists, CC, followup-to, netiquette and all the rest [was: direct ethernet connection between computer and printer] Lisi Reisz <lisi.reisz@gmail.com> - 2015-10-19 09:40 +0200
Re: Mailing lists, CC, followup-to, netiquette and all the rest [was: direct ethernet connection between computer and printer] <tomas@tuxteam.de> - 2015-10-19 09:30 +0200
Re: Mailing lists, CC, followup-to, netiquette and all the rest [was: direct ethernet connection between computer and printer] Lisi Reisz <lisi.reisz@gmail.com> - 2015-10-19 09:40 +0200
Re: Mailing lists, CC, followup-to, netiquette and all the rest [was: direct ethernet connection between computer and printer] Lisi Reisz <lisi.reisz@gmail.com> - 2015-10-19 09:30 +0200
Re: Mailing lists, CC, followup-to, netiquette and all the rest [was: direct ethernet connection between computer and printer] <tomas@tuxteam.de> - 2015-10-18 22:00 +0200
Re: Mailing lists, CC, followup-to, netiquette and all the rest [was: direct ethernet connection between computer and printer] Brian <ad44@cityscape.co.uk> - 2015-10-18 23:50 +0200
Re: Mailing lists, CC, followup-to, netiquette and all the rest [was: direct ethernet connection between computer and printer] <tomas@tuxteam.de> - 2015-10-19 09:40 +0200
Re: Mailing lists, CC, followup-to, netiquette and all the rest [was: direct ethernet connection between computer and printer] Lisi Reisz <lisi.reisz@gmail.com> - 2015-10-19 09:40 +0200
Re: Mailing lists, CC, followup-to, netiquette and all the rest [was: direct ethernet connection between computer and printer] <tomas@tuxteam.de> - 2015-10-19 18:20 +0200
Re: Mailing lists, CC, followup-to, netiquette and all the rest [was: direct ethernet connection between computer and printer] Lisi Reisz <lisi.reisz@gmail.com> - 2015-10-19 23:40 +0200
Re: Mailing lists, CC, followup-to, netiquette and all the rest [was: direct ethernet connection between computer and printer] <tomas@tuxteam.de> - 2015-10-20 09:30 +0200
Re: Mailing lists, CC, followup-to, netiquette and all the rest [was: direct ethernet connection between computer and printer] Joel Rees <joel.rees@gmail.com> - 2015-10-22 02:10 +0200
Re: Mailing lists, CC, followup-to, netiquette and all the rest [was: direct ethernet connection between computer and printer] Chris Bannister <cbannister@slingshot.co.nz> - 2015-10-19 10:50 +0200
Re: Mailing lists, CC, followup-to, netiquette and all the rest [was: direct ethernet connection between computer and printer] Lisi Reisz <lisi.reisz@gmail.com> - 2015-10-19 12:10 +0200
Re: direct ethernet connection between computer and printer Lisi Reisz <lisi.reisz@gmail.com> - 2015-10-18 00:00 +0200
Re: direct ethernet connection between computer and printer rlharris@oplink.net - 2015-10-18 01:20 +0200
Re: direct ethernet connection between computer and printer <tomas@tuxteam.de> - 2015-10-18 09:20 +0200
Re: direct ethernet connection between computer and printer <tomas@tuxteam.de> - 2015-10-18 09:20 +0200
Re: direct ethernet connection between computer and printer Chris Bannister <cbannister@slingshot.co.nz> - 2015-10-18 10:40 +0200
Re: direct ethernet connection between computer and printer Brian <ad44@cityscape.co.uk> - 2015-10-17 21:40 +0200
Re: direct ethernet connection between computer and printer Martin Smith <lists@rakupottery.org.uk> - 2015-10-15 09:50 +0200
Re: direct ethernet connection between computer and printer rlharris@oplink.net - 2015-10-15 10:10 +0200
Re: direct ethernet connection between computer and printer Joe <joe@jretrading.com> - 2015-10-15 10:20 +0200
Re: direct ethernet connection between computer and printer rlharris@oplink.net - 2015-10-15 10:50 +0200
Re: direct ethernet connection between computer and printer Brian <ad44@cityscape.co.uk> - 2015-10-15 15:40 +0200
Page 1 of 4 [1] 2 3 4 Next page →
| From | rlharris@oplink.net |
|---|---|
| Date | 2015-10-15 08:10 +0200 |
| Subject | direct ethernet connection between computer and printer |
| Message-ID | <qjJTK-67x-31@gated-at.bofh.it> |
Yesterday in the office of my associate, I tried without success to install a HP LaserJet 2100TN in a wired local area network (LAN) consisting of nothing but a i386 running Windows 8, a modem (which I think also is router) and an ethernet switch. Through Control Panel, I learned that the computer had ip address 192.168.100.3. The HP2100 printed a configuration report which indicated an ip address of 192.168.1.201. It occurred to me to use telnet to access the printer and reconfigure the ip address. But the Windows command prompt did not understand "telnet". Thereupon I connected directly to the printer a laptop running Jessie (with Xfce desktop), using an ethernet cable. NetworkManager Applet (0.9.10.0) did not make a connection. I though that perhaps a "cross-over" ethernet cable might be required, so I placed an ethernet switch and two "straight" cables between the laptop and the printer; but again NetworkManager Applet (0.9.10.0) failed to make a connection. So first of all I would like to know whether it is possible to connect a computer directly to a printer without a router to manage the connection. And then I would like to know the proper way to reconfigure this printer. If the "modem" indeed has an internal router with DHCP server, then I think that the printer should utilize DHCP. At the moment I am ignorant concerning the modem and/or router, because they are hidden behind desks and boxes, so that visual inspection is going to necessitate moving things in the office, which my associate is not going to enjoy. Russ
[toc] | [next] | [standalone]
| From | Reco <recoverym4n@gmail.com> |
|---|---|
| Date | 2015-10-15 08:40 +0200 |
| Message-ID | <qjKmJ-6HK-3@gated-at.bofh.it> |
| In reply to | #159178 |
Hi. On Thu, 15 Oct 2015 00:34:14 -0500 rlharris@oplink.net wrote: > Yesterday in the office of my associate, I tried without success to > install a HP LaserJet 2100TN in a wired local area network (LAN) > consisting of nothing but a i386 running Windows 8, a modem (which I think > also is router) and an ethernet switch. > > Through Control Panel, I learned that the computer had ip address > 192.168.100.3. The HP2100 printed a configuration report which indicated > an ip address of 192.168.1.201. Did this 'configuration report' mention the netmask used by printer? What about printer's MAC? > It occurred to me to use telnet to access the printer and reconfigure the > ip address. But the Windows command prompt did not understand "telnet". > > Thereupon I connected directly to the printer a laptop running Jessie > (with Xfce desktop), using an ethernet cable. NetworkManager Applet > (0.9.10.0) did not make a connection. NetworkManager is unnecessary complex tool for such simple task. A simple sequence of 'ip link set' and 'ip address add' is sufficient for such things. > And then I would like to know the proper way to reconfigure this printer. > If the "modem" indeed has an internal router with DHCP server, then I > think that the printer should utilize DHCP. You do not need to guess here. Run tcpdump at your laptop, power cycle the printer. As long as you see requests to 0.0.0.0 udp port 67 - the printer uses DHCP for configuration. Reco
[toc] | [prev] | [next] | [standalone]
| From | rlharris@oplink.net |
|---|---|
| Date | 2015-10-15 10:00 +0200 |
| Message-ID | <qjLCa-8ty-7@gated-at.bofh.it> |
| In reply to | #159180 |
On Thu, October 15, 2015 1:30 am, Reco wrote: > Did this 'configuration report' mention the netmask used by printer? > What about printer's MAC? Yes; the title is "JetDirect Configuration Page", which provides the following: IP ADDRESS: 192.168.1.210 SUBNET MASK: 255.255.255.0 DEF. GATEWAY: 192.168.1.1 LAN HW ADDRESS: 0010835D432B I presume that the "LAN HW ADDRESS:" is the mac address. > NetworkManager is unnecessary complex tool for such simple task. > A simple sequence of 'ip link set' and 'ip address add' is sufficient > for such things. Understood; but NetWorkManager is installed by default by the Debian installer when Xfce is specified in Jessie. Can I make use of NetworkManager, or ignore it? > You do not need to guess here. Run tcpdump at your laptop, power cycle > the printer. As long as you see requests to 0.0.0.0 udp port 67 - the > printer uses DHCP for configuration. I brought the printer (and the laptop) back here. I installed tcpdump. I see no requests to 0.0.0.0 udp port 67. Russ
[toc] | [prev] | [next] | [standalone]
| From | Reco <recoverym4n@gmail.com> |
|---|---|
| Date | 2015-10-15 14:00 +0200 |
| Message-ID | <qjPmr-5vG-11@gated-at.bofh.it> |
| In reply to | #159182 |
On Thu, Oct 15, 2015 at 02:54:31AM -0500, rlharris@oplink.net wrote: > On Thu, October 15, 2015 1:30 am, Reco wrote: > > Did this 'configuration report' mention the netmask used by printer? > > What about printer's MAC? > > Yes; the title is "JetDirect Configuration Page", which provides the > following: > > IP ADDRESS: 192.168.1.210 > SUBNET MASK: 255.255.255.0 > DEF. GATEWAY: 192.168.1.1 > LAN HW ADDRESS: 0010835D432B > > I presume that the "LAN HW ADDRESS:" is the mac address. So do I. > > NetworkManager is unnecessary complex tool for such simple task. > > A simple sequence of 'ip link set' and 'ip address add' is sufficient > > for such things. > > Understood; but NetWorkManager is installed by default by the Debian > installer when Xfce is specified in Jessie. Can I make use of > NetworkManager, or ignore it? Attach Ethernet cable to your laptop and printer via switch. Ensure that NetworkManager ignores your laptop's Ethernet interface (eth0 for simplicity). Run (as root): ip l s dev eth0 up ip a a dev eth0 192.168.1.200/24 "ping 192.168.1.210" should succeed. "arping -I eth0 192.168.1.210" should show MAC 00:10:83:5D:43:2B. If you see all this - you're good and can proceed with: telnet 192.168.1.210 > > You do not need to guess here. Run tcpdump at your laptop, power cycle > > the printer. As long as you see requests to 0.0.0.0 udp port 67 - the > > printer uses DHCP for configuration. > > I brought the printer (and the laptop) back here. I installed tcpdump. I > see no requests to 0.0.0.0 udp port 67. So the printer uses statically assinged IP. This simplifies things :) Reco
[toc] | [prev] | [next] | [standalone]
| From | Brian <ad44@cityscape.co.uk> |
|---|---|
| Date | 2015-10-15 15:20 +0200 |
| Message-ID | <qjQBR-7uU-25@gated-at.bofh.it> |
| In reply to | #159192 |
On Thu 15 Oct 2015 at 14:53:16 +0300, Reco wrote: > On Thu, Oct 15, 2015 at 02:54:31AM -0500, rlharris@oplink.net wrote: > > > > I brought the printer (and the laptop) back here. I installed tcpdump. I > > see no requests to 0.0.0.0 udp port 67. > > So the printer uses statically assinged IP. This simplifies things :) Revert the printer to its factory defaults, which will use DHCP. [1] At the office it will pick up an address from the network it is on. [1] HP have instructions on how to do this.
[toc] | [prev] | [next] | [standalone]
| From | David Wright <deblis@lionunicorn.co.uk> |
|---|---|
| Date | 2015-10-15 16:50 +0200 |
| Message-ID | <qjS0V-Yf-3@gated-at.bofh.it> |
| In reply to | #159198 |
Quoting Brian (ad44@cityscape.co.uk): > On Thu 15 Oct 2015 at 14:53:16 +0300, Reco wrote: > > > On Thu, Oct 15, 2015 at 02:54:31AM -0500, rlharris@oplink.net wrote: > > > > > > I brought the printer (and the laptop) back here. I installed tcpdump. I > > > see no requests to 0.0.0.0 udp port 67. > > > > So the printer uses statically assinged IP. This simplifies things :) > > Revert the printer to its factory defaults, which will use DHCP. [1] At > the office it will pick up an address from the network it is on. > > [1] HP have instructions on how to do this. If you don't have a manual, download one from https://archive.org/details/printermanual-hp-laserjet-2100-service-manual and read chapters 3 (printer) and 6 (comms troubleshooting). The other page that's useful is http://h20564.www2.hp.com/hpsc/doc/public/display?docId=emr_na-bpj05678 Before you reset anything, get it to print the current configuration that your colleagues may be relying on. Make sure you've got the page- count: were you to hold the Job Cancel button *too* long when you do your factory reset, you would clear this number. There's also a separate network configuration page. The reason I mentioned printing is that the web page above mentions holding a button (Test in this instance) for anything up to 30 seconds. On your printer, that *would* clear your page count. Then do your reset and see whether, when you switch it on and connect it to the router, it automatically finds out what network it's on and what it's address is. Assuming the network card has reset, it *could* come up as 192.0.0.192 (but it shouldn't: DHCP should work). Cheers, David.
[toc] | [prev] | [next] | [standalone]
| From | Doug <dmcgarrett@optonline.net> |
|---|---|
| Date | 2015-10-15 21:50 +0200 |
| Message-ID | <qjWHg-7WB-33@gated-at.bofh.it> |
| In reply to | #159192 |
On 10/15/2015 07:53 AM, Reco wrote: > On Thu, Oct 15, 2015 at 02:54:31AM -0500, rlharris@oplink.net wrote: >> On Thu, October 15, 2015 1:30 am, Reco wrote: >>> Did this 'configuration report' mention the netmask used by printer? >>> What about printer's MAC? >> >> Yes; the title is "JetDirect Configuration Page", which provides the >> following: >> >> IP ADDRESS: 192.168.1.210 >> SUBNET MASK: 255.255.255.0 >> DEF. GATEWAY: 192.168.1.1 >> LAN HW ADDRESS: 0010835D432B >> >> I presume that the "LAN HW ADDRESS:" is the mac address. > > So do I. > /snip/ > So the printer uses statically assinged IP. This simplifies things :) > > Reco > > I have experience with two HP LaserJets and one Epson All-in-One inkjet, and all came with fixed IP addresses from the factory, in the range above 192.168.1.100. One came with .130, one with .147. one with .120. In your case, the fixed IP is .210. It should be easy to change, following instructions that came with the printer. Set the new IP address somewhere betwween .5 and .29 and all will be well. (Then you need to set the computer to look for that address when asked to print.) --dm
[toc] | [prev] | [next] | [standalone]
| From | rlharris@oplink.net |
|---|---|
| Date | 2015-10-15 22:20 +0200 |
| Message-ID | <qjXah-pN-1@gated-at.bofh.it> |
| In reply to | #159203 |
On Thu, October 15, 2015 2:42 pm, Doug wrote: > It should be easy to change, following instructions that came > with the printer. But that is the essence of the problem! The instructions which came with the printer (which are buried in a HP2100TN user manual which I found on line) end with the instruction to insert the HP administration utility CD, which CD I do not have and have not yet found. But even if I had the CD, it almost surely is for an early version of Windows. However, the good news is that when I access the hp2100tn with telnet, the printer advertises several commands, including a listing of current parameter settings and instructions on how to change individual parameters. Russ
[toc] | [prev] | [next] | [standalone]
| From | rlharris@oplink.net |
|---|---|
| Date | 2015-10-15 22:10 +0200 |
| Message-ID | <qjX0B-8R-19@gated-at.bofh.it> |
| In reply to | #159192 |
On Thu, October 15, 2015 6:53 am, Reco wrote: > Attach Ethernet cable to your laptop and printer via switch. > > Ensure that NetworkManager ignores your laptop's Ethernet interface > (eth0 for simplicity). > > Run (as root): > > ip l s dev eth0 up ip a a dev eth0 192.168.1.200/24 > > "ping 192.168.1.210" should succeed. > "arping -I eth0 192.168.1.210" should show MAC 00:10:83:5D:43:2B. > > telnet 192.168.1.210 Reco, this works perfectly. Many thanks for including all the details. And it turns out (according to the ISP out there) that my associate is receiving via a radio link a single address (192.168.100.3) from the DHCP server of the ISP. So in order to accommodate an ethernet printer, I need to install and configure a router. My only experience with routers has been with a PC running IPCop, but I understand that there are small firmware-based routers, which I suppose include a firewall and DHCP server. Have you any recommendations as to brand and model? Russ
[toc] | [prev] | [next] | [standalone]
| From | Brian <ad44@cityscape.co.uk> |
|---|---|
| Date | 2015-10-15 22:40 +0200 |
| Message-ID | <qjXtE-Qa-19@gated-at.bofh.it> |
| In reply to | #159204 |
On Thu 15 Oct 2015 at 15:01:01 -0500, rlharris@oplink.net wrote: > On Thu, October 15, 2015 6:53 am, Reco wrote: > > Attach Ethernet cable to your laptop and printer via switch. > > > > Ensure that NetworkManager ignores your laptop's Ethernet interface > > (eth0 for simplicity). > > > > Run (as root): > > > > ip l s dev eth0 up ip a a dev eth0 192.168.1.200/24 > > > > "ping 192.168.1.210" should succeed. > > "arping -I eth0 192.168.1.210" should show MAC 00:10:83:5D:43:2B. > > > > telnet 192.168.1.210 > > Reco, this works perfectly. Many thanks for including all the details. > > And it turns out (according to the ISP out there) that my associate is > receiving via a radio link a single address (192.168.100.3) from the DHCP > server of the ISP. > > So in order to accommodate an ethernet printer, I need to install and > configure a router. No you don't. You only have change the printers's setup to match the network it is on. You know how to do that with telnet. (Martin Smith has already alluded to the same principle).
[toc] | [prev] | [next] | [standalone]
| From | Lisi Reisz <lisi.reisz@gmail.com> |
|---|---|
| Date | 2015-10-15 22:50 +0200 |
| Message-ID | <qjXDk-11G-13@gated-at.bofh.it> |
| In reply to | #159207 |
On Thursday 15 October 2015 21:38:16 Brian wrote: > No you don't. You only have change the printers's setup to match the > network it is on. You know how to do that with telnet. Brian - Could you give some hints as to how two separate devices can share one IP without some sort of routing? Lisi
[toc] | [prev] | [next] | [standalone]
| From | Brian <ad44@cityscape.co.uk> |
|---|---|
| Date | 2015-10-15 23:00 +0200 |
| Message-ID | <qjXN1-1dR-25@gated-at.bofh.it> |
| In reply to | #159210 |
On Thu 15 Oct 2015 at 21:44:56 +0100, Lisi Reisz wrote: > On Thursday 15 October 2015 21:38:16 Brian wrote: > > No you don't. You only have change the printers's setup to match the > > network it is on. You know how to do that with telnet. > > Brian - > > Could you give some hints as to how two separate devices can share one IP > without some sort of routing? It isn't a matter of sharing one IP but of being on the same network in order to communicate. From an earlier post we have Through Control Panel, I learned that the computer had ip address 192.168.100.3. The HP2100 printed a configuration report which indicated an ip address of 192.168.1.201 It seems that the consensus is that 192.168.1.201 is a fixed IP for the printer. We will go with that. If the printer is to communicate with the computer it needs to have an IP like 192.168.100.3.201. Change its IP with telnet. A moment's job.
[toc] | [prev] | [next] | [standalone]
| From | Joe <joe@jretrading.com> |
|---|---|
| Date | 2015-10-15 23:20 +0200 |
| Message-ID | <qjY6m-1PP-19@gated-at.bofh.it> |
| In reply to | #159212 |
On Thu, 15 Oct 2015 21:58:21 +0100 Brian <ad44@cityscape.co.uk> wrote: > On Thu 15 Oct 2015 at 21:44:56 +0100, Lisi Reisz wrote: > > > On Thursday 15 October 2015 21:38:16 Brian wrote: > > > No you don't. You only have change the printers's setup to match > > > the network it is on. You know how to do that with telnet. > > > > Brian - > > > > Could you give some hints as to how two separate devices can share > > one IP without some sort of routing? > > It isn't a matter of sharing one IP but of being on the same network > in order to communicate. From an earlier post we have > > Through Control Panel, I learned that the computer had ip address > 192.168.100.3. The HP2100 printed a configuration report which > indicated an ip address of 192.168.1.201 > > It seems that the consensus is that 192.168.1.201 is a fixed IP for > the printer. We will go with that. > > If the printer is to communicate with the computer it needs to have an > IP like 192.168.100.3.201. Change its IP with telnet. A moment's job. > I assume that was a typo. I believe Windows does allow multiple IP addresses on one adaptor, but I haven't tried it, and I suspect MS would describe it as 'unsupported'. If you move the printer into the 192.168.3. network there must be a risk than another customer of the same ISP will be given whatever address you choose. -- Joe
[toc] | [prev] | [next] | [standalone]
| From | Brian <ad44@cityscape.co.uk> |
|---|---|
| Date | 2015-10-15 23:50 +0200 |
| Message-ID | <qjYzn-2nB-21@gated-at.bofh.it> |
| In reply to | #159215 |
On Thu 15 Oct 2015 at 22:10:43 +0100, Joe wrote: > On Thu, 15 Oct 2015 21:58:21 +0100 > Brian <ad44@cityscape.co.uk> wrote: > > > On Thu 15 Oct 2015 at 21:44:56 +0100, Lisi Reisz wrote: > > > > > On Thursday 15 October 2015 21:38:16 Brian wrote: > > > > No you don't. You only have change the printers's setup to match > > > > the network it is on. You know how to do that with telnet. > > > > > > Brian - > > > > > > Could you give some hints as to how two separate devices can share > > > one IP without some sort of routing? > > > > It isn't a matter of sharing one IP but of being on the same network > > in order to communicate. From an earlier post we have > > > > Through Control Panel, I learned that the computer had ip address > > 192.168.100.3. The HP2100 printed a configuration report which > > indicated an ip address of 192.168.1.201 > > > > It seems that the consensus is that 192.168.1.201 is a fixed IP for > > the printer. We will go with that. > > > > If the printer is to communicate with the computer it needs to have an > > IP like 192.168.100.3.201. Change its IP with telnet. A moment's job. > > > > I assume that was a typo. I believe Windows does allow multiple IP > addresses on one adaptor, but I haven't tried it, and I suspect MS > would describe it as 'unsupported'. If you move the printer into the > 192.168.3. network there must be a risk than another customer of the > same ISP will be given whatever address you choose. Yes. 192.168.100.201
[toc] | [prev] | [next] | [standalone]
| From | Brian <ad44@cityscape.co.uk> |
|---|---|
| Date | 2015-10-16 00:20 +0200 |
| Message-ID | <qjZ2q-3bG-21@gated-at.bofh.it> |
| In reply to | #159215 |
On Thu 15 Oct 2015 at 22:10:43 +0100, Joe wrote: > On Thu, 15 Oct 2015 21:58:21 +0100 > Brian <ad44@cityscape.co.uk> wrote: > > > > If the printer is to communicate with the computer it needs to have an > > IP like 192.168.100.3.201. Change its IP with telnet. A moment's job. > > > > I assume that was a typo. I believe Windows does allow multiple IP > addresses on one adaptor, but I haven't tried it, and I suspect MS > would describe it as 'unsupported'. If you move the printer into the > 192.168.3. network there must be a risk than another customer of the > same ISP will be given whatever address you choose. It is related in https://lists.debian.org/debian-user/2015/10/msg00722.html that ... it turns out (according to the ISP out there) that my associate is receiving via a radio link a single address (192.168.100.3) from the DHCP server of the ISP. An ISP hands out an address in a private range and it is assigned to the external interface of a router? I do not understand this but know I have much to learn about networking. Any enlightenment in the offing?
[toc] | [prev] | [next] | [standalone]
| From | rlharris@oplink.net |
|---|---|
| Date | 2015-10-16 01:00 +0200 |
| Message-ID | <qjZF9-3XH-17@gated-at.bofh.it> |
| In reply to | #159225 |
On Thu, October 15, 2015 5:11 pm, Brian wrote: > An ISP hands out an address in a private range and it is assigned to the > external interface of a router? I do not understand this but know I have > much to learn about networking. Any enlightenment in the offing? No; in the present (original) installation, the address (192.168.100.3) is assigned to the (Windows desktop) computer, and there is no router. But, conceptually, is there anything wrong with assigning a private IP address to the WAN port of a router? Russ
[toc] | [prev] | [next] | [standalone]
| From | Brian <ad44@cityscape.co.uk> |
|---|---|
| Date | 2015-10-16 10:30 +0200 |
| Message-ID | <qk8yL-FP-13@gated-at.bofh.it> |
| In reply to | #159228 |
On Thu 15 Oct 2015 at 17:40:57 -0500, rlharris@oplink.net wrote: > On Thu, October 15, 2015 5:11 pm, Brian wrote: > > An ISP hands out an address in a private range and it is assigned to the > > external interface of a router? I do not understand this but know I have > > much to learn about networking. Any enlightenment in the offing? > > No; in the present (original) installation, the address (192.168.100.3) is > assigned to the (Windows desktop) computer, and there is no router. > > But, conceptually, is there anything wrong with assigning a private IP > address to the WAN port of a router? I don't get out much :). Thanks to David Wright for introducing me to WISP and Joe for the clear explanation.
[toc] | [prev] | [next] | [standalone]
| From | Joe <joe@jretrading.com> |
|---|---|
| Date | 2015-10-16 09:50 +0200 |
| Message-ID | <qk7W1-872-17@gated-at.bofh.it> |
| In reply to | #159225 |
On Thu, 15 Oct 2015 23:11:45 +0100 Brian <ad44@cityscape.co.uk> wrote: > > An ISP hands out an address in a private range and it is assigned to > the external interface of a router? I do not understand this but know > I have much to learn about networking. Any enlightenment in the > offing? > That's an easy one. An ISP unwilling or unable to lease public addresses for all his customers. In the old days, there was just a modem pool, much smaller than the number of customers, but now everyone is online all the time. It's not unusual with the really big domestic ISPs who came to the game too late (or were in the wrong country) to get enough addresses. It also ensures that nobody runs any kind of service, and the other side of that coin is that nobody can try to break in apart from other customers on the same broadcast domain. Less helpdesk hassle. The moral is that if you're changing ISP and you want a public address, make sure first that you'll be getting one. -- Joe
[toc] | [prev] | [next] | [standalone]
| From | Lisi Reisz <lisi.reisz@gmail.com> |
|---|---|
| Date | 2015-10-15 23:40 +0200 |
| Message-ID | <qjYpI-2ci-11@gated-at.bofh.it> |
| In reply to | #159212 |
On Thursday 15 October 2015 21:58:21 Brian wrote: > On Thu 15 Oct 2015 at 21:44:56 +0100, Lisi Reisz wrote: > > On Thursday 15 October 2015 21:38:16 Brian wrote: > > > No you don't. You only have change the printers's setup to match the > > > network it is on. You know how to do that with telnet. > > > > Brian - > > > > Could you give some hints as to how two separate devices can share one IP > > without some sort of routing? > > It isn't a matter of sharing one IP but of being on the same network in > order to communicate. From an earlier post we have > > Through Control Panel, I learned that the computer had ip address > 192.168.100.3. The HP2100 printed a configuration report which indicated > an ip address of 192.168.1.201 > > It seems that the consensus is that 192.168.1.201 is a fixed IP for the > printer. We will go with that. > > If the printer is to communicate with the computer it needs to have an > IP like 192.168.100.3.201. Change its IP with telnet. A moment's job. Thanks. Lisi
[toc] | [prev] | [next] | [standalone]
| From | rlharris@oplink.net |
|---|---|
| Date | 2015-10-15 22:40 +0200 |
| Message-ID | <qjXtE-Qa-7@gated-at.bofh.it> |
| In reply to | #159204 |
On Thu, October 15, 2015 3:01 pm, rlharris@oplink.net wrote: > My only experience with routers has been with a PC running IPCop, but I > understand that there are small firmware-based routers, which I suppose > include a firewall and DHCP server. Have you any recommendations as to > brand and model? Is there anything wrong with using an old Wi-Fi router and turning off the radio? (My associate does not care for Wi-Fi.) In my junkbox is a Cisco Linksys WRT110 which can serve four ethernet devices. Russ
[toc] | [prev] | [next] | [standalone]
Page 1 of 4 [1] 2 3 4 Next page →
Back to top | Article view | linux.debian.user
csiph-web