Windows 10: IPv4 IP address conflict since upgrade to Win10

Upgraded an old win7 32-bit Dell Dimension 9200 to Win10 Pro on Friday 31st July. I intended to donate it to a school library in Kenya but shipping / customs costs high so now hoping to sell it to raise funds for the same charity.

On Friday 7th August I started to get Network Error "Windows has detected an IP address conflict" which seems to correspond to event ID 4199 from Tcpip. This was the first reboot following KB3074686 but that may be a coincidence?



This is the ipconfig (ipv6 continues to work enabling RDP from my laptop but there is no internet access from win10):
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IPv6 Address. . . . . . . . . . . : fd60:e701:51c6:c400:9c06:6a1e:78ae:ec51(Preferred)
Temporary IPv6 Address. . . . . . : fd60:e701:51c6:c400:bc75:b302:453f:e3ec(Preferred)
Link-local IPv6 Address . . . . . : fe80::9c06:6a1e:78ae:ec51%9(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.1.3(Duplicate)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : Sunday, August 9, 2015 3:54:44 PM
Lease Expires . . . . . . . . . . : Monday, August 10, 2015 3:54:42 PM
Default Gateway . . . . . . . . . : 192.168.1.1
DHCP Server . . . . . . . . . . . : 192.168.1.1
DHCPv6 IAID . . . . . . . . . . . : 167778769
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-13-73-A1-D3-00-19-D1-2A-97-3A
DNS Servers . . . . . . . . . . . : fe80::1%9
192.168.1.1
192.168.1.1
NetBIOS over Tcpip. . . . . . . . : Enabled

There are also NetBT error 4307 errors, I assume they are another symptom and not a cause:

C:\WINDOWS\system32>nbtstat -n


Local Area Connection:
Node IpAddress: [192.168.1.3] Scope Id: []


NetBIOS Local Name Table


Name Type Status
---------------------------------------------
ANTHONY-PC <20> UNIQUE Registered
ANTHONY-PC <00> UNIQUE Registered
WORKGROUP <00> GROUP Registered
WORKGROUP <1E> GROUP Registered




Unfortunately the original graphics card (ATI X1300) was unsupported so I was using it headless through Remote Desktop Protocol which complicated resolving networking issues!
UPDATE: Having received delivery of a cheap AMD R7 240 the graphics card issue was resolved.

UPDATE: I have worked around the networking IP address conflict by disabling DHCP and manually assigning an IPv4 IP address outside of the router's DHCP server IP range. NetBT/WINS enabled and name resolution now working correctly with Ubuntu and win8.1 boxes on the same network.

Should I now attempt a clean install to win10 64-bit (and enable access to full 5Gb memory)?
According to Belarc Advisor there are some Office 2010 applications licensed on the machine. Should I try to preserve them for charity use or do they need to be replaced?

:)

 

Ethernet connected but no internet

you mean you got ttl for you puing successfully (Reply from 8.8.8.8: bytes=32 time=47ms TTL=47) only when connected to wifi ?

So i think you have a problem with this in your wired connection.. For some reason your pc cant get ip address from your router/gateway. it shows autoconfig ipv4 address.. normally this happens when your gateway/router can't issue dhcp ip address or even
if there is a ip conflict.. very rarely this could be due to obsolete ethernet network drivers . I suggest you to check gateway/router .. restart router etc and check dhcp pool afterwords in the router. and if router dhcp setting for lan is ok, update ethernet
drivers to latest.. check cable connectivity to router.. etc

 

Since I upgraded to Windows 10 I cant connect to Internet

tell me if you get a ipv4 ip address