Client not acquiring IP address from ICS server

[Conan Kelly]

Hello all,

My Win XP Pro laptop is normally the one that dials-up, so I've run the
Network Setup Wizard so that the laptop has ICS enabled with a static IP
address of 192.168.0.1/24. Our Win XP MCE 2005 machine is set up for
dynamic IP address. We don't leave the computers physically connected all
the time because our house isn't wired for networking (I'm just running a
cable behind the couch and across the floor when we want the 2 machines
connected). The first day I ran the wizard (maybe 3 months ago), both
machines worked beautifully. But that was for the one day only. Pretty
much every time I've tried connecting the 2 'puters since then, the MCE
system could not acquire an address from the laptop (it would end up with an
address of 169.254.x.x/16).

2 nights ago, I decided to connect them together, not expecting it to work,
expecting to have to statically set the IP address. Low and behold, the
damn thing was working. Tried a registry hack, quit working. Tonight I
reverted my system back to before the registry hack (good thing I saved a
System Restore Point), It was working again. After that, I downloaded the
Security Update for Windows XP (KB912919), and once again it has quit
working. I have yet to uninstall this update to see if it will fix it.

I guess mainly what I'm interested in is if other people are having the same
issue with updates affecting their ICS capabilities. I'm pretty diligent on
keeping the computer updated and I'm wondering if these updates are somehow
affecting the DHCP functions of ICS.

Any ideas or thoughts on what to check or settings to change (other than
uninstalling the last update--I'll try that a little later to see if it
works) will be greatly appreciated. Also, if anyone else is having similar
problems, let me know.

Thanks for any help anyone can provide,

Conan Kelly

 

[Tony]

Hello all,

My Win XP Pro laptop is normally the one that dials-up, so I've run the
Network Setup Wizard so that the laptop has ICS enabled with a static IP
address of 192.168.0.1/24. Our Win XP MCE 2005 machine is set up for
dynamic IP address. We don't leave the computers physically connected all
the time because our house isn't wired for networking (I'm just running a
cable behind the couch and across the floor when we want the 2 machines
connected). The first day I ran the wizard (maybe 3 months ago), both
machines worked beautifully. But that was for the one day only. Pretty
much every time I've tried connecting the 2 'puters since then, the MCE
system could not acquire an address from the laptop (it would end up with
an address of 169.254.x.x/16).

2 nights ago, I decided to connect them together, not expecting it to
work, expecting to have to statically set the IP address. Low and behold,
the damn thing was working. Tried a registry hack, quit working. Tonight
I reverted my system back to before the registry hack (good thing I saved
a System Restore Point), It was working again. After that, I downloaded
the Security Update for Windows XP (KB912919), and once again it has quit
working. I have yet to uninstall this update to see if it will fix it.

I guess mainly what I'm interested in is if other people are having the
same issue with updates affecting their ICS capabilities. I'm pretty
diligent on keeping the computer updated and I'm wondering if these
updates are somehow affecting the DHCP functions of ICS.

Any ideas or thoughts on what to check or settings to change (other than
uninstalling the last update--I'll try that a little later to see if it
works) will be greatly appreciated. Also, if anyone else is having
similar problems, let me know.

Thanks for any help anyone can provide,

Conan Kelly

Yes I have had problems with MS updates stopping network connections from
working. I have usually got round it by deleting the network adaptor in
system devices and letting it reinstall.

 

[Glen]

I use ICS and found quite often if i get a 169.254 limited error you should
be able to just manually assign the address. Anything in the range
192.168.0.1 for the gateway ip and 255.255.255.0 for the subnet and
192.168.0.2 to 254 for the connecting puter and 255.255.255.0 for the
subnet. You dont need dhcp for your lan and it does cause problems
sometimes. I've never had an update stop mine working but I have had other
ongoing problems.

Glen P

 

[Conan Kelly]

Yes I have had problems with MS updates stopping network connections from
working. I have usually got round it by deleting the network adaptor in
system devices and letting it reinstall.

Tony,

Thanks for the info. I tried your suggestion, but it did not work. THIS IS
DRIVING ME CRAZY!!!!

I tried Glen's suggestions as well with no luck. Also when I tried to run
the Network Setup Wizard, it locked the whole system up tight. After 15
mins., the only way to reboot the system was to hold the power button down
for 5 secs. (ouch!). I couldn't even [Ctrl] + [Alt] + [Del] my way to the
Task Manager. That has happened to me before though. And I tried
uninstalling my most recent update, that didn't work either.

If you have any other ideas, they will be much appreciated,

Conan

 

[Conan Kelly]

Glen,

Thank you for your suggestions. Please read my response to Tony's post for
more info. I tried your suggestion: statically setting the IP address to
192.168.0.2-254 and gateway IP to 192.168.0.1, but I couldn't get out onto
the Internet. I could only get to the other computer's shared resources, as
usual.

Looking back on it now, though, I did not disable ICS. Could this interfer
with the other machines ability to get to the internet?

Any other ideas will be greatly appreciated,

Thanks again,

Conan Kelly