Cut the stack to bare minimum killing QOS and Ipv6 along with any other extraneous items.
Be suspect of any feature on 10's stack not on 7's. Always suspect newer Microsoft enhancements like homegroups. On Sep 1, 2017 9:15 PM, "lopaka polena" <lopa...@gmail.com> wrote: I use my extra NICs for virtual box. The network cards that are only being used for virtual machines should only have 2 things checked off in the properties the virtual bridged networking adapter (for virtualbox its "VirtualBox NDIS6 bridged networking driver") and the other is "Link layer topology discovery mapper I/O driver" nothing else should be checked or it will interfere with the primary NIC settings. VMWare should be set similar If both nics have IPV4 or IPV6 boxes checked I can almost guarantee it will cause problems like you describe. Only the primary NIC should have those checked lopaka On Fri, Sep 1, 2017 at 7:00 PM, Winterlight <winterli...@winterlight.org> wrote: > At 06:25 PM 9/1/2017, you wrote: > >> Few things to check. Does this computer have power settings that let it go >> to sleep or power off peripherals? >> > > That was one of the first thing I checked to make sure the computer could > not put the NIC to sleep > > Does it have a wireless nic or onboard chip that is not disabled. >> > > It has two NICS. ASUS P9X79 I haven't disabled one but I will try that. My > goal was to use the second NIC for just for VMware. But I haven't figured > out how to do that yet. > > When the computer won't connect to other devices what does it say if you >> open a CMD prompt and type ipconfig. >> > > right now the computer will connect to other computers but not the > printer. BUT other computers can not connect to it. > Windows IP Configuration > > Ethernet adapter Ethernet 2: > Media State . . . . . . . . . . . : Media disconnected > Connection-specific DNS Suffix . : > > Ethernet adapter Ethernet: > Connection-specific DNS Suffix . : > Link-local IPv6 Address . . . . . : fe80::99a2:69eb:8ef5:f489%9 > IPv4 Address. . . . . . . . . . . : 192.168.10.113 > Subnet Mask . . . . . . . . . . . : 255.255.255.0 > Default Gateway . . . . . . . . . : 192.168.10.1 > > Tunnel adapter Teredo Tunneling Pseudo-Interface: > Connection-specific DNS Suffix . : > IPv6 Address. . . . . . . . . . . : 2001:0:9d38:6ab8:ca6:1cbd:3f57:f58e > Link-local IPv6 Address . . . . . : fe80::ca6:1cbd:3f57:f58e%2 > Default Gateway . . . . . . . > > Does the network address show up properly? yes >> > > Can you ping other devices? >> > > On the other computers I get a I get a Windows cannot access.. check the > spelling otherwise there may be a problem with your network. BUT yes I can > ping the workstation from other computers that can not connect. > > Does the router show the device connected properly in the "Device List"? >> > > I don't see the router at all under Device list... but it seems unlikely > to be the router because all the other computers are working and I don't > see it with my laptop either. I had to print today from the laptop because > I can not print from the workstation to the network laser. > > Once I loose complete connectivity to the LAN I will go through the list > again. > > thanks for the help! > m > > > > > I have virtual machines that do this sometimes and usually have to disable >> then re-enable the network interface to fix things. I've occasionally had >> to do this on windows 10 machines but usually only the boxes that have >> multiple NICs >> >> lopaka >> >> On Fri, Sep 1, 2017 at 4:49 PM, Winterlight <winterli...@winterlight.org> >> wrote: >> >> > I have a personal home workgroup comprising of my primary Windows 10 PRO >> > workstation, some LIVA mini computers I use with TVs and some laptops >> and >> > wireless phones. Wireless is handled by a UniFi AP-AC-Pro. I have single >> > router plugged into a CABLE modem and into Netgear gigabit switch. I >> have a >> > couple of network printers and a HDHomerun TV turner running on the >> > network. This is a new house with a recent ... within the last three >> months >> > ... setup. My primary workstation is a new clean install of Windows 10 >> > PRO. The network works great EXCEPT for my primary workstation. It was >> > working just fine and I do have a Acronis image file from that time = a >> > month ago which I may be forced to restore but I would like to find a >> > lasting fix for this. >> > >> > My workstation keeps losing network conductivity. One hour I think I >> have >> > fixed the problem but 18 hours later I can't connect to other members of >> > the LAN or the printer won't work, or lan members can't connect to the >> > workstation but the workstation can connect to them. The workstation >> always >> > has internet and that tells me that the hardware is working although I >> have >> > swapped out and checked the switches. I have checked every setting on >> the >> > NIC. I ran windows troubleshooter and it came up with a problem with the >> > virtual network. I thought I found it so I completely removed VMware >> > player. And it worked again ...but for a matter of hours. Then I just >> > removed the NICs with their drivers, rebooted it reinstalled and >> everything >> > worked but 17 hours later I can not print to the network printer, and >> while >> > I can access other members of the LAN they can't connect to me. >> > >> > Any ideas? Is there software that can diagnose this? Should I just give >> up >> > and restore my working backup? Thanks! >> > >> > >> > >
