Windows 7: Potential Network Adaptor Problem

Hi,

I read Event Viewer stating: ERROR

"Your computer was not assigned an address from the network (by the DHCP Server) for the Network Card with network address 0x00025B66A83D. The following error occurred: 0x79. Your computer will continue to try and obtain an address on its own from the network address"

I do not understand it, i have set my network to static IP, not receive from DHCP server from my router. I have confirmed that by "ipconfig /all"

I have "ping localhost" with no 4 replies and have "ping 192.168.0.11" which is my computer. I did not received all 4 replies either.

I have ping to my router (DHCP Server) and it works OK.

Is it possible something wrong with my Ethernet hardware or just Ethernet driver problem?

Possible cause: TCP/IP Stack or my Ethernet is corrupt. What I can do about it?

Thanks in advance and happy new year to everyone

M

Try setting it to a dynamic IP and tell us what happens.

Also, what is the internel network IP of your router? 192.168.0.??

Thank you for reply.

My System is now reinstalled. Windows kernal was so bad which not just corrupted my tcp/ip stack but also caused BSOD several times.

M

check this:

Solution
It seems that some DHCP servers are having problems with IPv6 implementation on Windows 7 so the solution is to disable it.
1. Press Windows Key + R, type control and press enter.
2. Click on Network and Internet.
3. Click on Network and Sharing Center
4. Change Adapter Settings.
5. Right mouse click on the network adapter and select properties.
6. Uncheck 'Internet Protocol Version 6 (TCP/IPv6)' and press Ok.
Restart your computer if you don’t want to use ipconfig on a command window. Once you get the IP you can enable the IPv6 protocol but if you are not going to use it, what is the usual leave it this way.

That is no solution it's a work around at best and only tries to compenstate for an out of date driver or an out of date firmware on the router. Just about every router made in the last 15 years can handle the IPv6 protocol.

The Argument against Disabling IPv6
It is unfortunate that some organizations disable IPv6 on their computers running Windows Vista or Windows Server 2008, where it is installed and enabled by default. Many disable IPv6-based on the assumption that they are not running any applications or services that use it. Others might disable it because of a misperception that having both IPv4 and IPv6 enabled effectively doubles their DNS and Web traffic. This is not true.
From Microsoft's perspective, IPv6 is a mandatory part of the Windows operating system and it is enabled and included in standard Windows service and application testing during the operating system development process. Because Windows was designed specifically with IPv6 present, Microsoft does not perform any testing to determine the effects of disabling IPv6. If IPv6 is disabled on Windows Vista, Windows Server 2008, or later versions, some components will not function. Moreover, applications that you might not think are using IPv6—such as Remote Assistance, HomeGroup, DirectAccess, and Windows Mail—could be.
Therefore, Microsoft recommends that you leave IPv6 enabled, even if you do not have an IPv6-enabled network, either native or tunneled. By leaving IPv6 enabled, you do not disable IPv6-only applications and services (for example, HomeGroup in Windows 7 and DirectAccess in Windows 7 and Windows Server 2008 R2 are IPv6-only) and your hosts can take advantage of IPv6-enhanced connectivity.

Read more. http://technet.microsoft.com/en-us/m....cableguy.aspx

Fixing the 4 layer TCP/IP stack or winsock is easy by using the command prompt and the two commands in bold.

netsh winsock reset catalog (reset winsock entries)

netsh int ip reset reset.log hit (reset TCP/IP stack)

Read more: http://windows7themes.net/repair-reset-winsock-windows-7.html#ixzz14nqZhG9I

I agree completely with you that the suggestion (I pasted from another site) is only a work around. I have tried the 2 commands you suggest, and others, to no avail. It's been terribly frustrating. Until a more reliable solution comes up, I will have to make do. Thanks for your response.