![]() ![]() I have a similar setup with WinVista, and IPv6 works fine for that system. But if I try to ping the loopback IP, I get PING: transmit failed. I can ping other PCs on my network or on the internet without issue. A while back I wrote about implementing some registry entries as a workaround for this issue on Windows 10. It could not retrieve any DHCP information, could not ping anything on the network when configured with a static ip even pinging 127.0.0. I just upgraded from Win 7 to Win 8.1, and I'm having a really peculiar issue with my Ethernet NIC. Win8 is running from VirtualBox with Bridged networking set receives RADVD broadcasts and get's its address from a DHCPv6 server. There is a known issue with Windows 10 and Windows Server 2016 DNS client that prevents manage out using ISATAP on these operating systems from working correctly. If they are set to auto detect or something related, force them to a value just to be sure they are locked on the same parameters. ![]() A combination of half-duplex and full-duplex usually cause that behavior. When I try to ping anything, including 172.0.0. Right now, I am not getting any ip addresses on any adapters, not even a 169.x.x.x address. However, I do believe that Microsoft recently changed their licensing strategy for 8 Enterprise to make it more easily available without having an Enterprise Agreement. I am having some problems with connecting and pinging. ![]() Is anyone else having difficulties with this or having success with Win8 and IPv6? Check speed and duplex of the server interface, its values must be the same of the switch port it is connected. Windows 7 Ultimate Windows 7 Enterprise Windows 8/8.1 Enterprise. I've just started playing with the Windows 8 Consumer Preview release and found that, although Win8 gets a DHCPv6 issued address, it can't even Ping over IPv6 let alone connect anywhere. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |