Re: Is there any way of forcing it to Acquire Network Address?

John, sorry but you're on a pointless crusade to fix something that
isn't a problem however a few things.

> >How do you suggest he does that John?
>
> Proper troubleshooting.

Like? You've offered nothing constructive thus far.

> >He has a fine signal
>
> Maybe. Maybe not. Even so, interference could still be an issue.

Yes it can which I suggested some time back too but he said he has 4 of
the little XP bars, that's a pretty good signal any day.

> >end, all the client can do is sit there banging out DHCPDiscover
> >packets, all 342 bytes in size each time. There's *nothing* other than
> >get closer to the AP or improve and already suitable signal but to what
> >end?
>
> That assumes it's just a signal problem. It might well not be.
>
> >Just to get an IP address that he can test and report to his
> >neighbour.
>
> To what end? It's probably not a DHCP issue.

I agree but you maintained that it could still be a DHCP issue yet have
failed to suggest how on earth it can be when he was configured
statically. Please do elabourate... :)

> Properly troubleshoot the problem. Try other DHCP clients. Test closer to
> the AP. Check for other networks and for other sources of interference.

Each of which takes far longer than the 30 seconds to just TRY note the
key word here TRY bunging in an IP address, he has done that, we moved
on, it seems like it was his bluetooth dongle.

> Experience teaches that quick and dirty tends to have negative consequences.

Bollocks, it would have ruled out the problem long long ago.

> Might well be worth helping his neighbor with that.

And would have failed to solve the problem too as it looks like.

> The plot here is the difference between real troubleshooting and throwing
> things against a wall to see what might stick.

Not at all, the original question (see thread title) was how to force an
IP address. There's an answer, it's called static address. Quick to
try, little chance of bad effect. We've done that now. Move on.

> >Really, there is no need to continue this unless you have information on
> >how he gets to fix a DHCP service (that isn't broken) that he doesn't
> >own. :)
>
> We'll just have to agree to disagree.

You want to contiue this pointless discussion? Please then do tell how
*he* should have gone about fixing a DHCP service on a router he didn't
own and has no direct physical access to. I'm fascinated!

On the other hand, i'm done here because I have to say, you've lost the
plot on this one.

David.
.

Relevant Pages

  • Re: A little FYI
    ... You figure out the problem then apply a single fix so you ... Ultimately this is due to problems with DHCP registration so one needs ... On the the server version of the Win 2K O/S, ... It's called looking at *all* the symptoms not just one. ...
    (comp.security.firewalls)
  • Re: DHCP Issue
    ... After using the LSP Fix & the Winsock Fix, the system will now pick up a ... DHCP IP Address. ... You will see a string and dll file name. ... Winsock Fix listed below. ...
    (microsoft.public.windowsxp.network_web)
  • Re: ICS problem. busted tcp/ip stack?
    ... online, and found out the problem and correct it. ... The problem was with DHCP in windows, ... was back up the registry and reinstall winsock. ... called winsock fix and it cleared it right up. ...
    (microsoft.public.windowsxp.network_web)
  • Re: setting IP to 224.0.0.1
    ... If it's DHCP, nothing you do to CE is going to fix it. ... and we've had boxes returned since the network was unavailable after it ... and I have to erase the registry to get it back. ...
    (microsoft.public.windowsce.platbuilder)
  • Re: HELP ! ipfw et natd
    ... I'd suggest trying to fix the rule 501 (is the IP address of the DHCP ... what isn't broken" nothings makes me upgrade the OS there. ... disabling or firewall-blocking vulnerable services that were found ...
    (comp.unix.bsd.freebsd.misc)