Win XP ICS - DHCP just quits working?

Hello. Please allow me to ask a question. I am very puzzled. Perhaps
some of you could shed some light on my current situation.

Scenario: Windows XP Pro with Netgear WG111 USB 2.0 wireless(wifi)
adapter. Drivers and applications installed from latest zip file from
netgear (wg111_2_1.zip). Native netgear apps not running at all,
instead I am using Windows XP's capabilities to manage my wifi network
which consist of an ad hoc network with desktop as host and a laptop
as the client. I am using Win XP's Internet Connection Sharing (and
its DHCP capabilities).

The ad hoc network runs at 11 mpbs (802.11b) and has a wep key.

For 2 weeks everything works fine. Win XP assigns an IP address to the
laptop everytime it connects to the ad hoc network, and I can use my
broadband internet connection from my laptop. All is good. Getting
great range and data transfer rate is great when streaming music from
the host desktop.

Then for what seems like totally out of the blue, Win XP does NOT
assign an IP address to my laptop anymore. The laptop connects to the
ad hoc network, but hangs on 'acquiring IP address' or something like
that, and finally times out and gets a default IP address. If I run
ipconfig /renew in a command window on the laptop, I get the message
that the DHCP server cannot be reached.

Any ideas? Why would Win XP DHCP suddenly stop working after 2 weeks
or so?

Please note that if I manually assign an IP address to the laptop,
then all is good again. I can see the host and transfer files etc.
Since I have other wifi networks at work, I would like to use Win XP's
DHCP again at home because I do not want to have to assign and
unassign IP addresses all the time (DHCP at work, then manually at
home etc.).

Thank you in advance. CHEERS!

(E-Mail Removed) (Bendit) wrote in
news:(E-Mail Removed) om:

> Hello. Please allow me to ask a question. I am very puzzled. Perhaps
> some of you could shed some light on my current situation.
>
> Scenario: Windows XP Pro with Netgear WG111 USB 2.0 wireless(wifi)
> adapter. Drivers and applications installed from latest zip file from
> netgear (wg111_2_1.zip). Native netgear apps not running at all,
> instead I am using Windows XP's capabilities to manage my wifi network
> which consist of an ad hoc network with desktop as host and a laptop
> as the client. I am using Win XP's Internet Connection Sharing (and
> its DHCP capabilities).
>
> The ad hoc network runs at 11 mpbs (802.11b) and has a wep key.
>
> For 2 weeks everything works fine. Win XP assigns an IP address to the
> laptop everytime it connects to the ad hoc network, and I can use my
> broadband internet connection from my laptop. All is good. Getting
> great range and data transfer rate is great when streaming music from
> the host desktop.
>
> Then for what seems like totally out of the blue, Win XP does NOT
> assign an IP address to my laptop anymore. The laptop connects to the
> ad hoc network, but hangs on 'acquiring IP address' or something like
> that, and finally times out and gets a default IP address. If I run
> ipconfig /renew in a command window on the laptop, I get the message
> that the DHCP server cannot be reached.
>
> Any ideas? Why would Win XP DHCP suddenly stop working after 2 weeks
> or so?
>
> Please note that if I manually assign an IP address to the laptop,
> then all is good again. I can see the host and transfer files etc.
> Since I have other wifi networks at work, I would like to use Win XP's
> DHCP again at home because I do not want to have to assign and
> unassign IP addresses all the time (DHCP at work, then manually at
> home etc.).

I would simply get a wired/wireless NAT router and let it be the gateway
device and the DHCP server for the network and be done with it and forget
about AD-Hoc anything with ICS Windows anything. You'll have less gray
hairs that way. ;-)

It's just a lille advice.


http://www.homenethelp.com/web/explain/about-NAT.asp

Duane

"Duane Arnold" <(E-Mail Removed)> wrote in message
news:Xns95B067EDBDAF8notmenotmecom@63.240.76.16...
> (E-Mail Removed) (Bendit) wrote in
> news:(E-Mail Removed) om:
>
>> Hello. Please allow me to ask a question. I am very puzzled. Perhaps
>> some of you could shed some light on my current situation.
>>
>> Scenario: Windows XP Pro with Netgear WG111 USB 2.0 wireless(wifi)
>> adapter. Drivers and applications installed from latest zip file from
>> netgear (wg111_2_1.zip). Native netgear apps not running at all,
>> instead I am using Windows XP's capabilities to manage my wifi network
>> which consist of an ad hoc network with desktop as host and a laptop
>> as the client. I am using Win XP's Internet Connection Sharing (and
>> its DHCP capabilities).
>>
>> The ad hoc network runs at 11 mpbs (802.11b) and has a wep key.
>>
>> For 2 weeks everything works fine. Win XP assigns an IP address to the
>> laptop everytime it connects to the ad hoc network, and I can use my
>> broadband internet connection from my laptop. All is good. Getting
>> great range and data transfer rate is great when streaming music from
>> the host desktop.
>>
>> Then for what seems like totally out of the blue, Win XP does NOT
>> assign an IP address to my laptop anymore. The laptop connects to the
>> ad hoc network, but hangs on 'acquiring IP address' or something like
>> that, and finally times out and gets a default IP address. If I run
>> ipconfig /renew in a command window on the laptop, I get the message
>> that the DHCP server cannot be reached.
>>
>> Any ideas? Why would Win XP DHCP suddenly stop working after 2 weeks
>> or so?
>>
>> Please note that if I manually assign an IP address to the laptop,
>> then all is good again. I can see the host and transfer files etc.
>> Since I have other wifi networks at work, I would like to use Win XP's
>> DHCP again at home because I do not want to have to assign and
>> unassign IP addresses all the time (DHCP at work, then manually at
>> home etc.).
>
> I would simply get a wired/wireless NAT router and let it be the gateway
> device and the DHCP server for the network and be done with it and forget
> about AD-Hoc anything with ICS Windows anything. You'll have less gray
> hairs that way. ;-)
>
> It's just a lille advice.
>
>
> http://www.homenethelp.com/web/explain/about-NAT.asp
>
> Duane
>

Thank you for your advice. I am aware of the different hardware components I
could purchase to make my situation better. I would like to stick with ICS
and my USB radio though, as it is cost effective (when it works!) and
reusable (you can just carry the usb thingy everywhere, it's really small
and light). Plus, it is now personal, I must conquer that problem or I will
lose sleep over it!

Thanks again for any input!

Have you tried reconfiguring ICS......start from scratch?

Have you had any virus, spyware or trojans?

"Duane Arnold" <(E-Mail Removed)> wrote in message
news:Xns95B067EDBDAF8notmenotmecom@63.240.76.16...
> (E-Mail Removed) (Bendit) wrote in
> news:(E-Mail Removed) om:
>
> > Hello. Please allow me to ask a question. I am very puzzled.
Perhaps
> > some of you could shed some light on my current situation.
> >
> > Scenario: Windows XP Pro with Netgear WG111 USB 2.0 wireless(wifi)
> > adapter. Drivers and applications installed from latest zip file
from
> > netgear (wg111_2_1.zip). Native netgear apps not running at all,
> > instead I am using Windows XP's capabilities to manage my wifi
network
> > which consist of an ad hoc network with desktop as host and a
laptop
> > as the client. I am using Win XP's Internet Connection Sharing
(and
> > its DHCP capabilities).
> >
> > The ad hoc network runs at 11 mpbs (802.11b) and has a wep key.
> >
> > For 2 weeks everything works fine. Win XP assigns an IP address to
the
> > laptop everytime it connects to the ad hoc network, and I can use
my
> > broadband internet connection from my laptop. All is good. Getting
> > great range and data transfer rate is great when streaming music
from
> > the host desktop.
> >
> > Then for what seems like totally out of the blue, Win XP does NOT
> > assign an IP address to my laptop anymore. The laptop connects to
the
> > ad hoc network, but hangs on 'acquiring IP address' or something
like
> > that, and finally times out and gets a default IP address. If I
run
> > ipconfig /renew in a command window on the laptop, I get the
message
> > that the DHCP server cannot be reached.
> >
> > Any ideas? Why would Win XP DHCP suddenly stop working after 2
weeks
> > or so?
> >
> > Please note that if I manually assign an IP address to the laptop,
> > then all is good again. I can see the host and transfer files etc.
> > Since I have other wifi networks at work, I would like to use Win
XP's
> > DHCP again at home because I do not want to have to assign and
> > unassign IP addresses all the time (DHCP at work, then manually at
> > home etc.).
>
> I would simply get a wired/wireless NAT router and let it be the
gateway
> device and the DHCP server for the network and be done with it and
forget
> about AD-Hoc anything with ICS Windows anything. You'll have less
gray
> hairs that way. ;-)
>
> It's just a lille advice.
>
>
> http://www.homenethelp.com/web/explain/about-NAT.asp
>
> Duane
>
>
>

Have you recently updated zone alarm past the 4.59 version? If so
reverting back to the 4.59 or before version should let your ics work
again. Chuck

On 29 Nov 2004 07:52:20 -0800, (E-Mail Removed) (Bendit) wrote:

>Hello. Please allow me to ask a question. I am very puzzled. Perhaps
>some of you could shed some light on my current situation.
>
>Scenario: Windows XP Pro with Netgear WG111 USB 2.0 wireless(wifi)
>adapter. Drivers and applications installed from latest zip file from
>netgear (wg111_2_1.zip). Native netgear apps not running at all,
>instead I am using Windows XP's capabilities to manage my wifi network
>which consist of an ad hoc network with desktop as host and a laptop
>as the client. I am using Win XP's Internet Connection Sharing (and
>its DHCP capabilities).
>
>The ad hoc network runs at 11 mpbs (802.11b) and has a wep key.
>
>For 2 weeks everything works fine. Win XP assigns an IP address to the
>laptop everytime it connects to the ad hoc network, and I can use my
>broadband internet connection from my laptop. All is good. Getting
>great range and data transfer rate is great when streaming music from
>the host desktop.
>
>Then for what seems like totally out of the blue, Win XP does NOT
>assign an IP address to my laptop anymore. The laptop connects to the
>ad hoc network, but hangs on 'acquiring IP address' or something like
>that, and finally times out and gets a default IP address. If I run
>ipconfig /renew in a command window on the laptop, I get the message
>that the DHCP server cannot be reached.
>
>Any ideas? Why would Win XP DHCP suddenly stop working after 2 weeks
>or so?
>
>Please note that if I manually assign an IP address to the laptop,
>then all is good again. I can see the host and transfer files etc.
>Since I have other wifi networks at work, I would like to use Win XP's
>DHCP again at home because I do not want to have to assign and
>unassign IP addresses all the time (DHCP at work, then manually at
>home etc.).
>
>Thank you in advance. CHEERS!

(E-Mail Removed) (Bendit) wrote in message news:<(E-Mail Removed). com>...
> Hello. Please allow me to ask a question. I am very puzzled. Perhaps
> some of you could shed some light on my current situation.
>
> Scenario: Windows XP Pro with Netgear WG111 USB 2.0 wireless(wifi)
> adapter. Drivers and applications installed from latest zip file from
> netgear (wg111_2_1.zip). Native netgear apps not running at all,
> instead I am using Windows XP's capabilities to manage my wifi network
> which consist of an ad hoc network with desktop as host and a laptop
> as the client. I am using Win XP's Internet Connection Sharing (and
> its DHCP capabilities).
>
> The ad hoc network runs at 11 mpbs (802.11b) and has a wep key.
>
> For 2 weeks everything works fine. Win XP assigns an IP address to the
> laptop everytime it connects to the ad hoc network, and I can use my
> broadband internet connection from my laptop. All is good. Getting
> great range and data transfer rate is great when streaming music from
> the host desktop.
>
> Then for what seems like totally out of the blue, Win XP does NOT
> assign an IP address to my laptop anymore. The laptop connects to the
> ad hoc network, but hangs on 'acquiring IP address' or something like
> that, and finally times out and gets a default IP address. If I run
> ipconfig /renew in a command window on the laptop, I get the message
> that the DHCP server cannot be reached.
>
> Any ideas? Why would Win XP DHCP suddenly stop working after 2 weeks
> or so?
>
> Please note that if I manually assign an IP address to the laptop,
> then all is good again. I can see the host and transfer files etc.
> Since I have other wifi networks at work, I would like to use Win XP's
> DHCP again at home because I do not want to have to assign and
> unassign IP addresses all the time (DHCP at work, then manually at
> home etc.).
>
> Thank you in advance. CHEERS!


New outcome: I had reinstalled all the netgear software and
reconfigured 'internet connection sharing' under windows XP pro and
all was good again. The desktop was giving an IP to the laptop, I
could access the web from the laptop, life was good.

Then again, while surfing the web from the laptop, all stopped working
again. I couldn't surf to anything anymore, URLs couldn't get resolved
anymore, I couldn't even PING the host desktop (192.168.0.1)! A
'repair' on the network adapter would once again fail on 'acquiring
network address'. The host computer was hosed again.

I am now forced to use hard coded IP addresses, and I am writing this
message through a remote desktop connection from the laptop to the
desktop (which I guess is way more secured in a way since I have to
authenticate).

(note that the wireless service on that laptop runs fine all day long
at work, without any drops at all)

So that is my story. I am mystified at the ability of my host computer
to work for a while (ICS) and then stop and stay broken for what seems
like no good reason at all.

Again, if you have any insights, I am all ears.

cheers!

Bendit wrote:
> (E-Mail Removed) (Bendit) wrote in message
news:<(E-Mail Removed). com>...
> > Hello. Please allow me to ask a question. I am very puzzled.
Perhaps
> > some of you could shed some light on my current situation.
> >
> > Scenario: Windows XP Pro with Netgear WG111 USB 2.0 wireless(wifi)
> > adapter. Drivers and applications installed from latest zip file
from
> > netgear (wg111_2_1.zip). Native netgear apps not running at all,
> > instead I am using Windows XP's capabilities to manage my wifi
network
> > which consist of an ad hoc network with desktop as host and a
laptop
> > as the client. I am using Win XP's Internet Connection Sharing (and
> > its DHCP capabilities).
> >
> > The ad hoc network runs at 11 mpbs (802.11b) and has a wep key.
> >
> > For 2 weeks everything works fine. Win XP assigns an IP address to
the
> > laptop everytime it connects to the ad hoc network, and I can use
my
> > broadband internet connection from my laptop. All is good. Getting
> > great range and data transfer rate is great when streaming music
from
> > the host desktop.
> >
> > Then for what seems like totally out of the blue, Win XP does NOT
> > assign an IP address to my laptop anymore. The laptop connects to
the
> > ad hoc network, but hangs on 'acquiring IP address' or something
like
> > that, and finally times out and gets a default IP address. If I run
> > ipconfig /renew in a command window on the laptop, I get the
message
> > that the DHCP server cannot be reached.
> >
> > Any ideas? Why would Win XP DHCP suddenly stop working after 2
weeks
> > or so?
> >
> > Please note that if I manually assign an IP address to the laptop,
> > then all is good again. I can see the host and transfer files etc.
> > Since I have other wifi networks at work, I would like to use Win
XP's
> > DHCP again at home because I do not want to have to assign and
> > unassign IP addresses all the time (DHCP at work, then manually at
> > home etc.).
> >
> > Thank you in advance. CHEERS!
>
>
> New outcome: I had reinstalled all the netgear software and
> reconfigured 'internet connection sharing' under windows XP pro and
> all was good again. The desktop was giving an IP to the laptop, I
> could access the web from the laptop, life was good.
>
> Then again, while surfing the web from the laptop, all stopped
working
> again. I couldn't surf to anything anymore, URLs couldn't get
resolved
> anymore, I couldn't even PING the host desktop (192.168.0.1)! A
> 'repair' on the network adapter would once again fail on 'acquiring
> network address'. The host computer was hosed again.
>
> I am now forced to use hard coded IP addresses, and I am writing this
> message through a remote desktop connection from the laptop to the
> desktop (which I guess is way more secured in a way since I have to
> authenticate).
>
> (note that the wireless service on that laptop runs fine all day long
> at work, without any drops at all)
>
> So that is my story. I am mystified at the ability of my host
computer
> to work for a while (ICS) and then stop and stay broken for what
seems
> like no good reason at all.
>
> Again, if you have any insights, I am all ears.
>
> cheers!

Progress: ICS worked for a couple of days again. This time it had
functionned properly without re-installing the netgear software. Beats
me. I had placed a support call at netgear just for the heck of it.
They have free 90 day support with a new product. Because both
computers can ping each other if IP addresses are manually configured,
they basically told me to go suck a lemon and call Microsoft (regarding
ICS).

On 11 Dec 2004 13:10:10 -0800, in alt.internet.wireless , "Bendit"
<(E-Mail Removed)> wrote:

>they basically told me to go suck a lemon and call Microsoft (regarding
>ICS).

Probably fair enough - its hardly someone else's problem if MS's DHCP
implementation is one lemon short of a G&T. The best solution is to buy a
router or invest in cheap proxying s/w.


--
Mark McIntyre
CLC FAQ <http://www.eskimo.com/~scs/C-faq/top.html>
CLC readme: <http://www.ungerhu.com/jxh/clc.welcome.txt>

it's worth a try for you, but i find that xp is usually the issue.
check your firewall settings (if you use xp firewall) as that's where
the issue has been when i'm troubleshooting the office computers.
although after the first few weeks of resetting (yes, on more than one
laptop it took me resetting that several times on each) i no longer
have the issue, but when i do - it is someone's firewall.


--
mediadarling
brought to you by http://www.wifi-forum.com/

"mediadarling" <mediadarling.1hmhsa@WiFi-Forum_dot_com> wrote in message
news:mediadarling.1hmhsa@WiFi-Forum_dot_com...
>
> it's worth a try for you, but i find that xp is usually the issue.
> check your firewall settings (if you use xp firewall) as that's where
> the issue has been when i'm troubleshooting the office computers.
> although after the first few weeks of resetting (yes, on more than one
> laptop it took me resetting that several times on each) i no longer
> have the issue, but when i do - it is someone's firewall.
>
>
> --
> mediadarling
> brought to you by http://www.wifi-forum.com/
>

Thank you for your input. Unfortunately, it is not the firewall, at least
what I can see of the GUI.

Progress report:

I run ICS with a hard coded IP address (and gateway & DNS that points to my
host with ICS) on my client (the laptop). I have been up and running without
any problems. It seems like the DHCP feature of XP Pro with ICS enabled was
the problem for me, it totally breaks my connection.