As a network engineer, here's how I'd approach this problem. Maybe it's helpful to you.
1. Run the command "arp -a" from the pc. This will give me a list of mac addrs to ip addrs mappings for all the network interfaces that are on the subnet from which I'm running the command. e.g. mannix@mc-mint ~ $ arp -a ? (192.168.0.10) at 00:18:4d:ff:ff:07 [ether] on wlan0 ? (192.168.0.1) at 50:6a:03:94:82:da [ether] on wlan0 2. Copy and paste the command results into a text file. 2. Disconnect the printer from the network. 3. Run the arp -a command from the pc again and compare the list of entries to the first results list. 4. If nothing changes, then the pc and the printer are on different subnets. 5. At which point, you can either put them on the same subnet if the hp printer has wireless or you statically assign an ip address to it on the same subnet or you connect the two devices & subnets via a router. Nowadays, most ISPs provide a wireless router that has some ethernet ports. If you connect the printer to the wifi router via an ethernet cable into one of the eth ports on the wifi router, you should then be able to see it from your pc over the WLAN. Cheers!, Mike On 11/06/2015 03:47 PM, [email protected] wrote: > Send PLUG mailing list submissions to > [email protected] > > To subscribe or unsubscribe via the World Wide Web, visit > http://lists.pdxlinux.org/mailman/listinfo/plug > or, via email, send a message with subject or body 'help' to > [email protected] > > You can reach the person managing the list at > [email protected] > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of PLUG digest..." > > > Today's Topics: > > 1. Re3: Networking & HP-Printer Probs ... (Re2: ... Remote > Desktop & Virtual Network Connections ... ) (Charles) > 2. Re: Re3: Networking & HP-Printer Probs ... (Re2: ... Remote > Desktop & Virtual Network Connections ... ) (wes) > 3. Re: Re3: Networking & HP-Printer Probs ... (Re2: ... Remote > Desktop & Virtual Network Connections ... ) (Russell Senior) > 4. Re4: ... Networking & HP-Printer Probs ... (Charles) > 5. Re: Re3: Networking & HP-Printer Probs ... (Re2: ... Remote > Desktop & Virtual Network Connections ... ) (Charles) > 6. Re: Re3: Networking & HP-Printer Probs ... (Re2: ... Remote > Desktop & Virtual Network Connections ... ) (Russell Senior) > 7. Re: Networking & HP-Printer Probs ... (Re3: ... Building > Community; Tekies & End-Users) (Russell Senior) > 8. Re: Re3: Networking & HP-Printer Probs ... (Re2: ... Remote > Desktop & Virtual Network Connections ... ) (wes) > 9. Re: Re4: ... Networking & HP-Printer Probs ... (Rich Shepard) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Fri, 6 Nov 2015 13:35:41 -0800 > From: Charles <[email protected]> > Subject: [PLUG] Re3: Networking & HP-Printer Probs ... (Re2: ... > Remote Desktop & Virtual Network Connections ... ) > To: [email protected], Portland Linux/Unix Group > <[email protected]> > Cc: [email protected], [email protected] > Message-ID: <[email protected]> > Content-Type: text/plain; charset=utf-8; format=flowed > > Wes; > > Thanks much for the valuable insight. > > As you suggested, i ran the "ifconfig" command. > These are the results i received: > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~ > ifconfig > > eth0 Link encap:Ethernet HWaddr 00:27:13:b1:ff:c5 > UP BROADCAST MULTICAST MTU:1500 Metric:1 > RX packets:0 errors:0 dropped:0 overruns:0 frame:0 > TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:1000 > RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) > Interrupt:20 Memory:fc200000-fc220000 > > lo Link encap:Local Loopback > inet addr:127.0.0.1 Mask:255.0.0.0 > inet6 addr: ::1/128 Scope:Host > UP LOOPBACK RUNNING MTU:65536 Metric:1 > RX packets:31993 errors:0 dropped:0 overruns:0 frame:0 > TX packets:31993 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:0 > RX bytes:3689652 (3.6 MB) TX bytes:3689652 (3.6 MB) > > wlan0 Link encap:Ethernet HWaddr 00:21:6a:b2:d5:f2 > inet addr:192.168.0.106 Bcast:192.168.0.255 Mask:255.255.255.0 > inet6 addr: fe80::221:6aff:feb2:d5f2/64 Scope:Link > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:71328 errors:0 dropped:0 overruns:0 frame:0 > TX packets:43190 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:1000 > RX bytes:54549381 (54.5 MB) TX bytes:7211431 (7.2 MB) > ~~~~~~~~~~~~~~~~~~~~~ > > Here-under, you said: > > > note the line stating "inet addr:" > > - this is the IP you should emulate. > > In the above data out-put which i received, > i see two references to "inet addr". > > I tried pinging them both, & they both ping ok. > > I am presuming that the latter-one for wlan0 > is the one that is for the router which controls my network; > & which reads as: "inet addr:192.168.0.106" ; > is the one which we should focus on; Correct? > > And your video is excellent; > & i will try to get the ip set-up on the printer asap. > > Need to reply to Rich here also. > > Thanks much; > > Cz ... > > > > > > > ------------------------------ > > Message: 2 > Date: Fri, 6 Nov 2015 13:55:42 -0800 > From: wes <[email protected]> > Subject: Re: [PLUG] Re3: Networking & HP-Printer Probs ... (Re2: ... > Remote Desktop & Virtual Network Connections ... ) > To: Charles <[email protected]> > Cc: Rich Shepard <[email protected]>, Portland Linux/Unix Group > <[email protected]>, john <[email protected]> > Message-ID: > <caa1wlokdsnajrsu5vmuvwxnpumfnjtt6ubtnrah_xj+vpae...@mail.gmail.com> > Content-Type: text/plain; charset=UTF-8 > > On Fri, Nov 6, 2015 at 1:35 PM, Charles <[email protected]> wrote: > >> wlan0 Link encap:Ethernet HWaddr 00:21:6a:b2:d5:f2 >> inet addr:192.168.0.106 Bcast:192.168.0.255 Mask:255.255.255.0 >> inet6 addr: fe80::221:6aff:feb2:d5f2/64 Scope:Link >> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 >> RX packets:71328 errors:0 dropped:0 overruns:0 frame:0 >> TX packets:43190 errors:0 dropped:0 overruns:0 carrier:0 >> collisions:0 txqueuelen:1000 >> RX bytes:54549381 (54.5 MB) TX bytes:7211431 (7.2 MB) >> ~~~~~~~~~~~~~~~~~~~~~ >> >> Here-under, you said: >> >>> note the line stating "inet addr:" >>> - this is the IP you should emulate. >> In the above data out-put which i received, >> i see two references to "inet addr". >> >> I tried pinging them both, & they both ping ok. >> >> I am presuming that the latter-one for wlan0 >> is the one that is for the router which controls my network; >> & which reads as: "inet addr:192.168.0.106" ; >> is the one which we should focus on; Correct? >> > This is the IP address for the computer system where you ran the ifconfig > command. This would make your router's IP address 192.168.0.1. The fact > that this computer's IP is 106 suggests (by implication) that the router > begin handing out IPs at 100, this is a common default setup. So, the > safest course is to set your printer's IP to something below 100 (but above > 1). If there is any possibility you may begin to have more devices in the > future which you may need to set IPs manually on, it will become critically > important that you don't use the same address for multiple devices. Today > it's not a problem, but something to keep in mind. > > >> And your video is excellent; >> & i will try to get the ip set-up on the printer asap. >> > I suggest using 192.168.0.2. > > good luck. > > -wes > > > ------------------------------ > > Message: 3 > Date: Fri, 06 Nov 2015 14:54:47 -0800 > From: Russell Senior <[email protected]> > Subject: Re: [PLUG] Re3: Networking & HP-Printer Probs ... (Re2: ... > Remote Desktop & Virtual Network Connections ... ) > To: Portland Linux/Unix Group <[email protected]> > Message-ID: <[email protected]> > Content-Type: text/plain; charset=us-ascii > >>>>>> "wes" == wes <[email protected]> writes: > wes> This is the IP address for the computer system where you ran the > wes> ifconfig command. This would make your router's IP address > wes> 192.168.0.1. The fact that this computer's IP is 106 suggests (by > wes> implication) that the router begin handing out IPs at 100, this is > wes> a common default setup. So, the safest course is to set your > wes> printer's IP to something below 100 (but above 1). If there is any > wes> possibility you may begin to have more devices in the future which > wes> you may need to set IPs manually on, it will become critically > wes> important that you don't use the same address for multiple > wes> devices. Today it's not a problem, but something to keep in mind. > > Most network printers advertise service via zeroconf. You should try: > > avahi-browse -a > > _______________________________________________ PLUG mailing list [email protected] http://lists.pdxlinux.org/mailman/listinfo/plug
