Yes, your problem and mine seemed very similar and I had similar troubleshooting experiences, including the results of releasing and renewing -or attempting (it too failed) - the ipconfig. I have pasted below my latest ipconfig /all which now includes both the wireless and the wired network adaptors as a compaeison, though obviously either can be disconnected at will and most of the trouleshooting was with just the LAN.
pinging a known site achieves 100% loss once the connection changes from its approx 60 secs of identified private to unidentified public network.
It looks like for are back up and working, adequately at least, so that is good.
Interested in Trouble's steps for you, I opened my NIC's properties, but did not find an advanced tab or anywhere to see or control the connection speed or whether duplex and so on. There is an advanced tab for the w/l adaptor but again I found no view or control of connection speed or mode or whther duplex. I suppose these were specific steps for you which I cannot try.
Sorry, I do not know how to insert my code neatly in a compact form.
Code:
Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Rick>ipconfig /all
Windows IP Configuration
Host Name . . . . . . . . . . . . : PCS-Lenovo-PC
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : lan
Wireless LAN adapter Wireless Network Connection 3:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft Virtual WiFi Miniport Adapter #
2
Physical Address. . . . . . . . . : 00-1B-11-21-18-4D
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Wireless LAN adapter Wireless Network Connection:
Connection-specific DNS Suffix . : lan
Description . . . . . . . . . . . : D-Link DWA-140 RangeBooster N USB Adapter
Physical Address. . . . . . . . . : 00-1B-11-21-18-4C
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::3d99:c376:9583:52f2%19(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.1.94(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : 24 February 2011 11:16:57
Lease Expires . . . . . . . . . . : 25 February 2011 23:16:56
Default Gateway . . . . . . . . . :
DHCP Server . . . . . . . . . . . : 192.168.1.254
DHCPv6 IAID . . . . . . . . . . . : 402660113
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-10-6A-1B-F6-00-21-86-1A-00-B0
DNS Servers . . . . . . . . . . . : 192.168.1.254
NetBIOS over Tcpip. . . . . . . . : Enabled
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . : lan
Description . . . . . . . . . . . : Intel(R) 82566DM-2 Gigabit Network Connec
tion
Physical Address. . . . . . . . . : 00-21-86-1A-00-B0
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IPv4 Address. . . . . . . . . . . : 192.168.1.83(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : 24 February 2011 11:13:45
Lease Expires . . . . . . . . . . : 25 February 2011 23:13:44
Default Gateway . . . . . . . . . :
DHCP Server . . . . . . . . . . . : 192.168.1.254
DNS Servers . . . . . . . . . . . : 192.168.1.254
NetBIOS over Tcpip. . . . . . . . : Enabled
Tunnel adapter Teredo Tunneling Pseudo-Interface:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Tunnel adapter isatap.{9F03E329-F0CB-4776-864B-D9C8F5B3A49E}:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft ISATAP Adapter #2
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Tunnel adapter isatap.lan:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . : lan
Description . . . . . . . . . . . : Microsoft ISATAP Adapter #3
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
C:\Users\Rick>
RickyQ:
As you can see by looking at the IP addressing information that you have posted above, neither of your two Network Adapters is receiving complete DHCP addressing information from your router. Both are missing the Default Gateway Address and without that any communication outside your local network will be impossible since sent packets don't know where to go to leave the local network. Additionally your D-Link wireless adapter is also missing DNS Servers addressing and without that, that adapter will be unable to resolve FQDNs (Fully Qualified Domain Names like
www.microsoft.com) So....
First try to manually assign static values for IP addressing information for both devices use the following information;
D-Link DWA-140 (wireless adapter)
IP Address 192.168.1.221
SubNet Mask 255.255.255.0
Default Gateway 192.168.1.254
DNS Server Preferred 192.168.1.254
Intel 82566DM-2 (wired Gigabit Adapter)
IP Address 192.168.1.222
SubNet Mask 255.255.255.0
Default Gateway 192.168.1.254
DNS Server Preferred 192.168.1.254
OK your way back out of there in both case and reboot the machine, go back and make sure the static assignments have been preserved through the reboot.
If that still doesn't seem to help then go back and adjust the DNS address information to a public DNS server solution like Google's which are
Preferred = 8.8.8.8
Alternate = 8.8.4.4
Or even better determine the DNS server addresses from you ISP provider. They should be present if you look at the Router's WAN page.
OK your way back out of there and see if that helps.
As a last resort try contacting your ISP it may be an issue that they may be familiar with and may be able to resolve with either a firmware update for their device or a particular configuration setting that we may not know about. Minimally they should at least be able to tell you their DNS server addresses which may help if you can't determine them through other means.