"-keevill-" <keevillus@yahoo.com> hath wroth:

>> Easy. Download a DHCP/BOOTP query tool:
>> <http://www.weirdsolutions.com/weirdSolutions/files/products/desktopSoftware/desktopQueryTool/querytool_free.exe>
>> Fire it up on your LAN/WLAN and see if it can find a DHCP server. Type
>> anything you want into the "device identifier" field.

>I am sorry to report a total failure of that test. I cannot get any response
>from that test tool no matter whether I use hard wired connection or
>wireless. Connecting my laptop to any of the access points whether they have
>DHCP enabled or not produces a 'no responses received' message from the
>tool.

Weird. It has always worked on everything I've tried except for a
Windoze Server 2003 with all the sandbox security features enabled. It
also doesn't work with DHCP AUTH (RFC-3118).

I did some tinkering and produced "No response received" if I
unchecked the "Request Broacast Response" box. Please check this box.
Also, uncheck the "Use BOOTP protocol" box.

>I can ping any station on the network from the notebook and an IPCONFIG/all
>shows an ip address 192.168.0.83 which has been given my by the only router
>with DHCP configured. The router IP is correctly shown as 192.168.0.247
>which is also the DG.

Sounds correct. If you can get a DHCP assigned IP address, the query
tool should work. There's no way you can get a valid DHCP assigned IP
address and also not have the query tool work. They go together. Does
your router have a logging feature, which might show some errors?
Syslog?

Did you do the aformentioned failed test via wired or wireless?

Can I presume that the DHCP server is your unspecified model Belkin
router? Could you disclose the model number and firmware version?
Also the SMC access points.

>If I move away to another access point on which DCHP has NOT been configured
>to run, then I cannot connect. All this has been done from my notebook.

I don't know what to tell you. This may be an indication of why using
a single DHCP server wasn't working for you. It *SHOULD* work, but
apparently doesn't. Do you have a home system or another router
available for tinkering? If so, then plug your computer into the
router and try the DHCP query tool again.

However, that doesn't really solve the original problem. If the query
tool doesn't work on your LAN/WLAN, then DHCP is not going to work
through multiple bridges (access points).

At this point, I usually drag out the protocol analyzer (Wireshark or
Ethereal), sniff the traffic, spend an hour decoding the junk, but
usually can identify the problem. If you feel ambitious, download
Wireshark:
<http://www.wireshark.org>
and sniff some exchanges (using ipconfig /renew to initiate the
exchange). Compare with what the query tool does. I should mention
that if you've never done this before, there's going to be a rather
major learning curve.

Methinks we're onto the cause of the problem. I guess(tm) is that
it's pointing to the unspecified model Belkin router, if that's the
DHCP server.


--
Jeff Liebermann jeffl@cruzio.com
150 Felker St #D http://www.LearnByDestroying.com
Santa Cruz CA 95060 http://802.11junk.com
Skype: JeffLiebermann AE6KS 831-336-2558