DHCP error causing shutdown?

[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.

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?

I can provide more details.

Ron

 

[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.

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?

I can provide more details.

Ron

It may or may not be RDU related. Here is the error message: "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 is assigned 192.168.0.101.

I am a little stumped.

Ron

 

[Nepatsfan]

The problem starts with the fact that you've got two instances of
the DHCP service running on your network, the ICS host PC and
your router. You only need one. Try turning off the DHCP service
on the router, essentially turning it into a switch. If you've
set up ICS correctly , your host computer will provide DHCP
service for your network. You should also set up the client
computer to obtain an IP address automatically. You may find that
you're going to have to start from scratch setting up your ICS
connection.

Nepatsfan

 

[Ron Joiner]

The problem starts with the fact that you've got two instances of
the DHCP service running on your network, the ICS host PC and
your router. You only need one. Try turning off the DHCP service
on the router, essentially turning it into a switch. If you've
set up ICS correctly , your host computer will provide DHCP
service for your network. You should also set up the client
computer to obtain an IP address automatically. You may find that
you're going to have to start from scratch setting up your ICS
connection.

Nepatsfan

Would this cause the host computer to go into suspend/sleep?

Ron

 

[Nepatsfan]

Would this cause the host computer to go into suspend/sleep?

Ron

Because I've never set up ICS the way you're doing I can't say
for certain whether that's what is causing your host computer to
go into a "suspend state". Whenever I've set up ICS using dialup
, I've either used a crossover cable (LAN has only 2 computers)
or a hub (at least three machines).

What I do know is that every resource I've ever seen relating to
ICS using dialup never has a router in the mix. It's always a hub
or a switch. A router is used with cable or DSL becuase you're
not using ICS in that environment. The bottom line to this setup
is that ICS handles DHCP services for your network. You don't
need a router performing the same function. See "Warning #2" in
this article for details:

http://www.practicallynetworked.com/sharing/xp_ics/index.htm

Why not try the following and see what happens:

Turn off the DHCP service on your router.
Make sure your internet connection is working on the host
computer.
Set up ICS on the host PC. You should end up with your dialup
connection being assinged an IP address from your ISP and your
host computer having an IP for the LAN (ethernet connection) of
192.168.0.1 .
Set up your client computer to obtain an address automatically.
It should end up with an IP in the 192.168.0.X range. You may
have to run an ipconfig /renew to get the proper settings
(Start -> Run -> ipconfig /renew).
See if the client can connect to the internet.

Here's another web site that might come in handy:

http://www.pcstats.com/articleview.cfm?articleid=1429&page=8

Nepatsfan

 

[Ron Joiner]

Because I've never set up ICS the way you're doing I can't say
for certain whether that's what is causing your host computer to
go into a "suspend state". Whenever I've set up ICS using dialup
, I've either used a crossover cable (LAN has only 2 computers)
or a hub (at least three machines).

What I do know is that every resource I've ever seen relating to
ICS using dialup never has a router in the mix. It's always a hub
or a switch. A router is used with cable or DSL becuase you're
not using ICS in that environment. The bottom line to this setup
is that ICS handles DHCP services for your network. You don't
need a router performing the same function. See "Warning #2" in
this article for details:

http://www.practicallynetworked.com/sharing/xp_ics/index.htm

Why not try the following and see what happens:

Turn off the DHCP service on your router.
Make sure your internet connection is working on the host
computer.
Set up ICS on the host PC. You should end up with your dialup
connection being assinged an IP address from your ISP and your
host computer having an IP for the LAN (ethernet connection) of
192.168.0.1 .
Set up your client computer to obtain an address automatically.
It should end up with an IP in the 192.168.0.X range. You may
have to run an ipconfig /renew to get the proper settings
(Start -> Run -> ipconfig /renew).
See if the client can connect to the internet.

Here's another web site that might come in handy:

http://www.pcstats.com/articleview.cfm?articleid=1429&page=8

Nepatsfan

I reconfigured the router to a switch and disengaged DHCP while at the
same time assigned it an IP adress other than the host computer which is
assigned 192.168.0.1. I have set the other computers on the LAN to
obtain an address automatically. I will look at your other suggestions
in the next day or so. All is well so far.

I have gone to the sites you suggested and especially noted #2 on
practicallynetworked and now see the logic in the whole thing. I am now
in the process of restoring ICS.

Thanks for your kind assistance.

Ron