Re: HELP - can reach ISP through cable, not through wireless ?

sorry for the mess, the previous post went out too early... below is the
right one...

--------------

Jeff, thanks for replying.


> 2. Do you have a default gateway assigned on the wireless client?
> If Windoze W2K or XP, try:
> start -> run -> cmd <enter>
> ipconfig
> The default gateway displayed needs to be the IP address of the
> Sitecom router. My guess is that it's either 0.0.0.0 or some other
> value left over from a previous wireless exercise.

Indeed - this is where the problem was. When I did a ipconfig /all I saw the
default gateway on the laptop (wireless client) was set to the address of
the wireless router, not the Sitecom router. I had to force this in the
wireless card's tcp/ip settings - although DHCP on the wireless router was
there was no way to convince the wireless client to get settings
automatically from DHCP on the Sitecom. I found this interesting because
when I connect the same client to the same (wireless) router with a
cable/network card instead of a wirelecc PC card, the client gets the
settings from the Ditecom DHCP without a hitch.
At any rate, this made the ISP's IP address pingable, and manually setting
the DNS servers in the wireless PC card's tcp/ip settings, internet started
to work as well.

All's well that ends well. Now for catching up on sleep.

Best regards,

BN

"Bob Newheart" <paddo16_kill_spam@hotmail.com> wrote in message news:...
> Jeff, thanks for replying.
>
>
> > 2. Do you have a default gateway assigned on the wireless client?
> > If Windoze W2K or XP, try:
> > start -> run -> cmd <enter>
> > ipconfig
> > The default gateway displayed needs to be the IP address of the
> > Sitecom router. My guess is that it's either 0.0.0.0 or some other
> > value left over from a previous wireless exercise.
>
> Indeed - this is where the problem was. When I did a ipconfig /all I saw
the
> default gateway on the laptop (wireless client) was set to the address of
> the wireless router, not the Sitecom router. I had to force this in the
> wireless card's tcp/ip settings - although DHCP on the wireless router was
> there was no way to convince the wireless client to get settings
> automatically from DHCP on the Sitecom. I found this interesting because
> when I connect the same client to the same (wireless) router with a
> cable/network card instead of a wirelecc PC card, the client gets the
> settings from the Ditecom DHCP without a hitch.
> At any rate, this made the ISP's IP address pingable, and manually setting
> the DNS servers in the wireless PC card's tcp/ip settings, internet
started
> to work as well.
>
> All's well that ends well. Now catch
>
>
>
>
> e on the laptop (wireless client) was set to the ip of the wireless
router,
> not the sitecom router. I fixed that (had to set it manually, couldn't get
> wireless to get it from the DHCP on the Sitecom (strange, a wireless
> connection to the USR router doesn't connect to DHCP on Sitecom while a
> cabled connection to the same USR router does.)
>
> Now I can ping the ISP fine. However, still cannot surf the net
>
> This one was right on - the default gateway had the address of the
wireless
> router instead of the Sitecom, must somehow be set through the wireless
side
> of things even if DHCP on the wireless router is turned off. It's
> counter-intuitive as a cable connection through the same wireless router
has
> a different result but hey, this is the weird world of wireless.
>
>
> > 3. Try refreshing DHCP with:
> > ipconfig /release
> > (wait about 10 seconds)
> > ipconfig /renew
> > ipconfig (see if you get a decent IP and gateway)
> > If it hangs, your Sitecom DHCP server setup is probably screwed up, or
> > your DHCP client on the laptop has a problem or is disabled.
> >
> >
> > --
> > Jeff Liebermann jeffl@comix.santa-cruz.ca.us
> > 150 Felker St #D http://www.LearnByDestroying.com
> > Santa Cruz CA 95060 http://802.11junk.com
> > AE6KS 831-336-2558
>
>