Error message

[DerbyBorn]

What does this mean:

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


Could it be this that causes me some start-up problems - what can I do
about it?

 

[John Williamson]

What does this mean:

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


Could it be this that causes me some start-up problems - what can I do
about it?

If your startup is taking a long time to get to this point, it may be
waiting for the DHCP server in your router to allocate an address, which
could mean there's a problem with the router. Try rebooting the router,
and if that doesn't work, try following the procedures on this page:-

http://forums.techguy.org/networking/963475-solved-ip-address-not-assigned.html

 

[Char Jackson]

What does this mean:

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

When your computer starts up, it requests an IP address from a DHCP server.
If you have a router, that's typically where the DHCP server is. If you
don't have a router, the DHCP server is in your ISP's network.

Some possible causes of this error:
-bad Ethernet cable (if wired)
-PC out of range of the router (if wireless)
-failing or misconfigured router
-failing Ethernet port on your PC
-network stack corruption on your PC
-...

Could it be this that causes me some start-up problems - what can I do
about it?

I wouldn't expect any of those things to directly cause a BSOD, except
perhaps if there's file corruption that goes well beyond the network stack.

 

[DerbyBorn]

When your computer starts up, it requests an IP address from a DHCP
server. If you have a router, that's typically where the DHCP server
is. If you don't have a router, the DHCP server is in your ISP's
network.

Some possible causes of this error:
-bad Ethernet cable (if wired)
-PC out of range of the router (if wireless)
-failing or misconfigured router
-failing Ethernet port on your PC
-network stack corruption on your PC
-...


I wouldn't expect any of those things to directly cause a BSOD, except
perhaps if there's file corruption that goes well beyond the network
stack.

It is wireless - and the BSOD comes up before the wireless would
normally have connected. It usually takes about 15 - 30 secs after
Windows has started for the icon in the system tray to show a
connection.

 

[Char Jackson]

It is wireless - and the BSOD comes up before the wireless would
normally have connected. It usually takes about 15 - 30 secs after
Windows has started for the icon in the system tray to show a
connection.

BSODs usually give you enough information to be able to track down the cause
and find a solution. Have you tried that? I think someone already suggested
BlueScreenView from Nirsoft.net, which is a great tool to have around.

Without knowing the details of the BSOD, I'd be reluctant to group the two
issues together. Is everything hunky dory if you do a static IP assignment,
essentially bypassing the DHCP server?

 

[Gene E. Bloch]

BSODs usually give you enough information to be able to track down the cause
and find a solution. Have you tried that? I think someone already suggested
BlueScreenView from Nirsoft.net, which is a great tool to have around.
+1

Without knowing the details of the BSOD, I'd be reluctant to group the two
issues together. Is everything hunky dory if you do a static IP assignment,
essentially bypassing the DHCP server?

+1