DHCP conflict causes suspend/sleep on A8N-SLI

  • Thread starter Thread starter Ron Joiner
  • Start date Start date
R

Ron Joiner

I have two WinXP pro machines, one as host and the other as client on a
home network. I just set this network up a couple of days ago. The
client computer was the host computer and the new computer became the
host. The host is an Athlon 3500+, A8N-SLI, WinXP Pro, 1 Gig DDR400 ram,
Winfast 6600GT PCIe.

Using Remote disconnection Utility (for ICS - I am on dialup)I attempted
to connect remotely and the host computer shut down as a result of a
DHCP error. Is this possible?

It may or may not be RDU related. Here is the error message from Event
Viewer: "The DHCP allocator has detected a DHCP server with IP address
192.168.0.199 (the IP address of the router) on the same network as the
interface with IP address 192.168.0.1 (the IP address of the host
computer). The allocator has disabled itself on the interface in order
to avoid confusing DHCP clients."

So while the host computer does not shut down completely it goes into
"sleep" mode and cannot be awakened without a restart. I assigned the
router the above IP address so that I can use ICS on the host computer.
The second computer on the LAN was assigned 192.168.0.101.

The problem starts with the fact that I've got two instances of
the DHCP service running on my network, the ICS host PC and
my router. I realize now that I only need one. I turned off DHCP service
on the router, essentially turning it into a switch. I have
now allowed my host computer to provide DHCP
service for my network and I have set up the client
computer to obtain an IP address automatically. I finally managed to
restore my ICS connection.

My last question remains. Did the DHCP error cause my Athlon/A8N-SLI
computer to go into a suspend mode?

Ron
 
Ron said:
I have two WinXP pro machines, one as host and the other as client on a
home network. I just set this network up a couple of days ago. The
client computer was the host computer and the new computer became the
host. The host is an Athlon 3500+, A8N-SLI, WinXP Pro, 1 Gig DDR400 ram,
Winfast 6600GT PCIe.

Using Remote disconnection Utility (for ICS - I am on dialup)I attempted
to connect remotely and the host computer shut down as a result of a
DHCP error. Is this possible?

It may or may not be RDU related. Here is the error message from Event
Viewer: "The DHCP allocator has detected a DHCP server with IP address
192.168.0.199 (the IP address of the router) on the same network as the
interface with IP address 192.168.0.1 (the IP address of the host
computer). The allocator has disabled itself on the interface in order
to avoid confusing DHCP clients."

So while the host computer does not shut down completely it goes into
"sleep" mode and cannot be awakened without a restart. I assigned the
router the above IP address so that I can use ICS on the host computer.
The second computer on the LAN was assigned 192.168.0.101.

The problem starts with the fact that I've got two instances of
the DHCP service running on my network, the ICS host PC and
my router. I realize now that I only need one. I turned off DHCP service
on the router, essentially turning it into a switch. I have
now allowed my host computer to provide DHCP
service for my network and I have set up the client
computer to obtain an IP address automatically. I finally managed to
restore my ICS connection.

My last question remains. Did the DHCP error cause my Athlon/A8N-SLI
computer to go into a suspend mode?

Ron
Should also add. My case is an Antec Sonata TruePower 380 PSU.
 
Ron said:
I have two WinXP pro machines, one as host and the other as client on
a home network. I just set this network up a couple of days ago. The
client computer was the host computer and the new computer became the
host. The host is an Athlon 3500+, A8N-SLI, WinXP Pro, 1 Gig DDR400
ram, Winfast 6600GT PCIe.

Using Remote disconnection Utility (for ICS - I am on dialup)I
attempted to connect remotely and the host computer shut down as a
result of a DHCP error. Is this possible?
No.

It may or may not be RDU related. Here is the error message from Event
Viewer: "The DHCP allocator has detected a DHCP server with IP address
192.168.0.199 (the IP address of the router) on the same network as
the interface with IP address 192.168.0.1 (the IP address of the host
computer). The allocator has disabled itself on the interface in order
to avoid confusing DHCP clients."

You can only have ONE DHCP server per network. You're using Internet
Connection sharing on ONE of your PCs, so that machine is a DHCP server.

On the CLIENT machine(s), you need to DISABLE ICS and/or any DHCP server
that you have running.
Click the "Setup" button at the top of the "Connections" tab within
"Internet Options" - do this on ALL your machines, and follow the
instructions (don't bother with the network disk it asks you to create).

Reboot everything when you've done that.
So while the host computer does not shut down completely it goes into
"sleep" mode and cannot be awakened without a restart. I assigned the
router the above IP address so that I can use ICS on the host
computer. The second computer on the LAN was assigned 192.168.0.101.

There is no need to allocate IP addresses with ICS - just set everything to
automatic. Then the PC that is ICSing it's connection, will automagically
become 192.168.0.1, and the clients will become 192.168.0.*
The problem starts with the fact that I've got two instances of
the DHCP service running on my network, the ICS host PC and
my router.

Er, you don't need a router if you're running ICS. ICS *is* a software
router :)
I realize now that I only need one. I turned off DHCP
service on the router, essentially turning it into a switch.

You need to turn off all it's routing functions too ! All DHCP does is
allocate IP addresses etc.
I have
now allowed my host computer to provide DHCP
service for my network and I have set up the client
computer to obtain an IP address automatically. I finally managed to
restore my ICS connection.

Yep, that's as it should be.
My last question remains. Did the DHCP error cause my Athlon/A8N-SLI
computer to go into a suspend mode?

No.

:)
 
Back
Top