On 10/09/2017 02:14 PM, Denis Heidtmann 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
This is the laptop's loopback or "localhost" - can ignore > 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 This looks like the laptops > 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 This looks like the laptop wireless, ipv4 address of 10.0.0.118/24 or ip 10.0.0.118 subnet mask 255.255.255.0 > > 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. As we used to back in the day, ignorance is curable, stupidity permanent. No shame in not knowing, heck, there are big holes in my knowledge for sure. >---more snip---- >> >> >> 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 >> >--snip--- VB uses an emulated network interface card (NIC), it won't see the host per se. Thus, "AMD PCNET Family PCI Ethernet Adapter" is the card for the Win2k "hardware" (can be changed in VB setings). By bridging, you are just connecting the 2 NICs to *behave* as one NIC. Remember, as far as Win2k knows, it is running on REAL hardware. You could do a "PCI passthrough" of the ACTUAL wifi hardware, but, if you do, the laptop host operating system looses control of and can't use that hardware. So, this looks ok, the win2k "box" is seeing you router ( Gateway 10.0.0.1) DHCP server (also 10.0.0.1) and getting IP 10.0.0.231 subnet Mask 255.255.255.0 which means your Win2k "box" is on the same network as the laptop and router. [Aside: the DNS servers look like Comcast. I recommend telling your router to override with OpenDNS or Google - much faster.] So far so good. In the top post, you said that you have: HP Officejet 4630 (10.0.0.244) port 9100 1. ping from the laptop linux ( ping 10.0.0.244) to make sure the printer is "alive" 2. ping from within the Win2K "box" (ping 10.0.0.244 ). You should be able to the printer IP from both the host and the guest unless something is screwy with your printer or a firewall somewhere. Now comes the tricky part (humor intended). In the Win2k add printer wizard you DO NOT scan for a network printer. This is for windows networks (SMB/SAMBA, Active Directory servers). Instead, you tell it to attach to a LOCAL printer and a specific TCP IP port. Here is a good tutorial from U of Penn: https://www.sas.upenn.edu/computing/natsci/tutorials/printing/xp (WinXP is basically Win2K with prettier GUI and more bugs). Hope this helps. -Ed _______________________________________________ PLUG mailing list PLUG@lists.pdxlinux.org http://lists.pdxlinux.org/mailman/listinfo/plug
