Progress. I got the ip address of the printer from settings/network in the host, pinged it from the host, then pinged it from win2k. Both were successful. But then I found out that the host could not connect to the router/modem until I shut down win2k in VB! So it appears that either the host is connected to the router/modem or it is connected to the printer. This is not the usual way the host connects to the printer, as I am able to print without losing my internet connection. The address was 192.168.223.100. I need to get rid of this direct connection to the printer. Then how do I get the (proper) ip address for the printer?
On Mon, Oct 9, 2017 at 2:14 PM, Denis Heidtmann <denis.heidtm...@gmail.com> wrote: > I am the one who should apologize--for being in such dire need of help. > Here is the output: > > denis@denis-ThinkPad-L420:~$ ip addr > 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group > default qlen 1 > link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 > inet 127.0.0.1/8 scope host lo > valid_lft forever preferred_lft forever > inet6 ::1/128 scope host > valid_lft forever preferred_lft forever > 2: enp9s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast > state DOWN group default qlen 1000 > link/ether e8:9a:8f:b9:6a:65 brd ff:ff:ff:ff:ff:ff > 3: wlp3s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP > group default qlen 1000 > link/ether 08:11:96:8a:4d:c0 brd ff:ff:ff:ff:ff:ff > inet 10.0.0.118/24 brd 10.0.0.255 scope global dynamic wlp3s0 > valid_lft 603477sec preferred_lft 603477sec > inet6 2601:1c0:6100:ac9::f498/128 scope global dynamic > valid_lft 603479sec preferred_lft 603479sec > inet6 2601:1c0:6100:ac9:c546:3082:760c:6e03/64 scope global temporary > dynamic > valid_lft 199748sec preferred_lft 84479sec > inet6 2601:1c0:6100:ac9:9211:491c:c335:ce74/64 scope global > mngtmpaddr noprefixroute dynamic > valid_lft 199748sec preferred_lft 199748sec > inet6 fe80::bff5:4bac:630:9759/64 scope link > valid_lft forever preferred_lft forever > > I do not know which of the many addresses to pay attention to. I tried to > use the man page to help me answer that question, but it did not. > > So you see that I have not accurately described the depth of my ignorance. > > > -Denis > > > I find this in the printer's properties (in the host): > dnssd://HP%20Officejet%204630%20series%20%5B69E035%5D._ipp._ > tcp.local/?uuid=1c852a4d-b800-1f08-abcd-8cdcd469e035 > > Both you and John have asked what happens if I ping the printer. How do I > do that? I do not see an IP address for the printer. > > I notice that now I see only one printer (-series) not the three I saw > earlier. Bit it still prints. http://localhost:631/printers/ shows only > the one, as idle, waiting for job to complete. But the queue is empty. > > > On Sun, Oct 8, 2017 at 9:51 PM, Tomas Kuchta <tomas.kuchta.li...@gmail.com > > wrote: > >> My apologies for the typos Dennis, >> >> I needed to run and wanted to send some ideas. >> >> I forgot to mention how to find your laptop's IP - run: ip addr >> >> If you see address not starting with the same 10.0.0.x - then your VM is >> not on the same network as your laptop. >> >> When I/we talk about different network, we mean it topologically rather >> than physically. When you look at the ipconfig output, the network is >> determined by IP - 10.0.0.231and netmask - 255.255.255.0 This means the >> network your VM is on can have IP addresses between 10.0.0.1 and >> 10.0.0.255 >> Out of these addresses .1 is taken for default gateway and .255 for >> broadcast to all machines. >> >> The printer can be on a different network, but it would not be discovered >> by windows, and it could be more challenging to configure. >> >> I hope that you find it helpful, >> Tomas >> >> On Oct 9, 2017 11:38 AM, "Tomas Kuchta" <tomas.kuchta.li...@gmail.com> >> wrote: >> >> What is your laptop's IP from Ubuntu? >> Does it start the same 10.0.0.x >> >> The VM is behind virtual network switch if bridged from your laptop's >> network port. >> >> What we are trying to establish is if on the same network. >> >> You forgot to ping the printer from inside the VM. That would have >> answered >> - if you can connect to it over the network. >> >> >> >> On Oct 9, 2017 11:30 AM, "Denis Heidtmann" <denis.heidtm...@gmail.com> >> wrote: >> >> As I mentioned to John, the laptop host Ubuntu 16.04 has successful access >> to the printer when the desktop is suspended or powered off. The laptop's >> access is via wireless. So isn't the printer's USB connection to the >> desktop irrelevant? Perhaps I should not have mentioned it. >> >> The guest Win2k had access to the printer before the desktop/router >> changes. It used the driver recommended by HP, hp deskjet 990c series. >> That driver is still available, ('though I may not know how to inform >> Win2k >> about it.) >> >> You mention "turn off/deny promiscuous mode". Maybe that is the key. I >> will play with that. >> >> I ran ipconfig/all from Win2k. The results are below. There are many >> things in it that are likely not correct, most of which I do not >> understand, nor know how to change. The wrong entries are likely due to >> how I installed VB on the laptop: I copied over the VB file from the >> desktop--it even has the old desktop's name as host. And I do not know >> how >> to get the corresponding information from Ubuntu if we need more than the >> ifconfig reported in my original posting. >> >> Thanks so much for trying to direct a lost soul in over his head. >> >> Now to play with promiscuity. >> >> -Denis >> >> >> >> Windows 2000 IP Configuration >> >> Host Name . . . . . . . . . . . . : winr2d4 [WRONG] >> Primary DNS Suffix . . . . . . . : >> Node Type . . . . . . . . . . . . : Broadcast >> IP Routing Enabled. . . . . . . . : No >> WINS Proxy Enabled. . . . . . . . : No >> DNS Suffix Search List. . . . . . : hsd1.or.comcast.net [?] >> >> Ethernet adapter Local Area Connection: >> >> Connection-specific DNS Suffix . : hsd1.or.comcast.net [?] >> Description . . . . . . . . . . . : AMD PCNET Family PCI Ethernet >> Adapter[WRONG] >> Physical Address. . . . . . . . . : 08-00-27-D6-6D-3F >> DHCP Enabled. . . . . . . . . . . : Yes >> Autoconfiguration Enabled . . . . : Yes >> IP Address. . . . . . . . . . . . : 10.0.0.231 >> Subnet Mask . . . . . . . . . . . : 255.255.255.0 >> Default Gateway . . . . . . . . . : 10.0.0.1 >> DHCP Server . . . . . . . . . . . : 10.0.0.1 >> DNS Servers . . . . . . . . . . . : 75.75.75.75 >> 75.75.76.76 >> Lease Obtained. . . . . . . . . . : Sunday, October 08, 2017 >> 4:16:42 PM >> Lease Expires . . . . . . . . . . : Sunday, October 15, 2017 >> 4:16:42 PM >> >> >> On Sun, Oct 8, 2017 at 3:11 PM, King Beowulf <kingbeow...@gmail.com> >> wrote: >> >> > On 10/08/2017 08:38 AM, Denis Heidtmann wrote: >> > > On my laptop, I have VB in Ubuntu 16.04 running Windows 2000. Before >> I >> > > changed my desktop computer and wireless router I could print from >> 2000. >> > > The printer is connected to the desktop via USB. The printer is also >> > > connected wirelessly to the new wireless Comcast Modem/router. I can >> > print >> > > from Ubuntu on the laptop. >> > > >> > > The long dialogue below is my attempt to show what I have tried to >> > restore >> > > the printing capability to the windows guest. I hope that someone >> here >> > > might be able to direct me along the path to success. >> > > >> > > Thanks, >> > > -Denis >> > > >> > >> > To print via a host printer in VirtualBox you need to: >> > >> > 1. Tell VB to passthrough the host USB port the printer is connected >> > to. Then you can "Add printers" in Windows. Be aware that Windows may >> > 'recognize' the printer as an unknown device until you install the >> > appropriate printer drivers inside the Windows guest. The Windows guest >> > knows absolutely nothing about Linux host and CUPS/HPLIP drivers. >> > >> > 2. Before the Windows guest can see the network printers, you need to >> > have the virtual NIC attached to the same network IP subnet as the host. >> > Normally, Bridged networking will do that but you must check advanced >> > settings to make sure the IP address assignment is correct and that >> > guest NAT and/or DHCP is not enabled. Note: If you are bridging to a >> > host wireless adaptor you will needs to turn off/deny promiscuous mode. >> > >> > If you are trying to get network printing working, and the virtual >> > network bringing is correct, in a Windows command window, type "ipconfig >> > /all" and compare the output to your host. Again, if you are not on the >> > same subnet you the Windows guest won't see any network printers. >> > >> > Anyway, I'm a bit rusty with VB since I moved to qemu. >> > >> > -Ed >> > _______________________________________________ >> > PLUG mailing list >> > PLUG@lists.pdxlinux.org >> > http://lists.pdxlinux.org/mailman/listinfo/plug >> > >> _______________________________________________ >> PLUG mailing list >> PLUG@lists.pdxlinux.org >> http://lists.pdxlinux.org/mailman/listinfo/plug >> _______________________________________________ >> PLUG mailing list >> PLUG@lists.pdxlinux.org >> http://lists.pdxlinux.org/mailman/listinfo/plug >> > > _______________________________________________ PLUG mailing list PLUG@lists.pdxlinux.org http://lists.pdxlinux.org/mailman/listinfo/plug
