No WAN Acess with Wireless on MR814

With this particular laptop, Toshiba Tecra M1, I cannot get either of
the following adapters to ping outside the MR814 router:

Intel PRO/Wireless 2100 LAN 3B Mini PCI Adapter
Avaya Gold

I have updated router to firmware 4.14 RC4. I can ping the router IP and
local network machines, but cannot ping the DNS or outside IP addresses.
I can also access the router's settings page with both NIC.

My friend has same router and same thing happens there too with this laptop.

Any ideas? Thanks.

DonMiche <(E-Mail Removed)> wrote in
news:dv2sc.13381$(E-Mail Removed):

> With this particular laptop, Toshiba Tecra M1, I cannot get either of
> the following adapters to ping outside the MR814 router:
>
> Intel PRO/Wireless 2100 LAN 3B Mini PCI Adapter
> Avaya Gold
>
> I have updated router to firmware 4.14 RC4. I can ping the router IP
> and local network machines, but cannot ping the DNS or outside IP
> addresses. I can also access the router's settings page with both NIC.
>
> My friend has same router and same thing happens there too with this
> laptop.
>
> Any ideas? Thanks.
>

What IP is the machine getting? If the IP starts with 169 then it's a sign
that the machine cannot get a IP from the DHCP server that's going allow
the machine to access the WAN. The 169. IP will allow the machines to
access each other on the LAN. That's if you're getting the 169 IP, which
usually indicates there is a misconfiguration with the NIC and it could
also lead to the TCP/IP Stack on the mahine being hosed *locked* and cannot
release the 169 IP.

What O/S?

Duane

Duane Arnold <(E-Mail Removed)> wrote in message news:<Xns94F26A7A55D08notmenotmecoml@63.240.76.16> ...
> DonMiche <(E-Mail Removed)> wrote in
> news:dv2sc.13381$(E-Mail Removed):
>
> > With this particular laptop, Toshiba Tecra M1, I cannot get either of
> > the following adapters to ping outside the MR814 router:
> >
> > Intel PRO/Wireless 2100 LAN 3B Mini PCI Adapter
> > Avaya Gold
> >
> > I have updated router to firmware 4.14 RC4. I can ping the router IP
> > and local network machines, but cannot ping the DNS or outside IP
> > addresses. I can also access the router's settings page with both NIC.
> >
> > My friend has same router and same thing happens there too with this
> > laptop.
> >
> > Any ideas? Thanks.
> >
>
> What IP is the machine getting? If the IP starts with 169 then it's a sign
> that the machine cannot get a IP from the DHCP server that's going allow
> the machine to access the WAN. The 169. IP will allow the machines to
> access each other on the LAN. That's if you're getting the 169 IP, which
> usually indicates there is a misconfiguration with the NIC and it could
> also lead to the TCP/IP Stack on the mahine being hosed *locked* and cannot
> release the 169 IP.
>
> What O/S?
>
> Duane


Thanks for your response Duane,

OS is Windows 2000
I am getting 192.168.0.3 with my gateway set at 192.168.0.1. That's
what's really weird about this problem...

Is the problem just PINGs? Can you surf the web?

Ron Bandes, CCNP, CTT+, etc.

"donMiche" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed) om...
> Duane Arnold <(E-Mail Removed)> wrote in message
news:<Xns94F26A7A55D08notmenotmecoml@63.240.76.16> ...
> > DonMiche <(E-Mail Removed)> wrote in
> > news:dv2sc.13381$(E-Mail Removed):
> >
> > > With this particular laptop, Toshiba Tecra M1, I cannot get either of
> > > the following adapters to ping outside the MR814 router:
> > >
> > > Intel PRO/Wireless 2100 LAN 3B Mini PCI Adapter
> > > Avaya Gold
> > >
> > > I have updated router to firmware 4.14 RC4. I can ping the router IP
> > > and local network machines, but cannot ping the DNS or outside IP
> > > addresses. I can also access the router's settings page with both NIC.
> > >
> > > My friend has same router and same thing happens there too with this
> > > laptop.
> > >
> > > Any ideas? Thanks.
> > >
> >
> > What IP is the machine getting? If the IP starts with 169 then it's a
sign
> > that the machine cannot get a IP from the DHCP server that's going allow
> > the machine to access the WAN. The 169. IP will allow the machines to
> > access each other on the LAN. That's if you're getting the 169 IP, which
> > usually indicates there is a misconfiguration with the NIC and it could
> > also lead to the TCP/IP Stack on the mahine being hosed *locked* and
cannot
> > release the 169 IP.
> >
> > What O/S?
> >
> > Duane
>
>
> Thanks for your response Duane,
>
> OS is Windows 2000
> I am getting 192.168.0.3 with my gateway set at 192.168.0.1. That's
> what's really weird about this problem...

In article <(E-Mail Removed) >,
donMiche <(E-Mail Removed)> wrote:
> Duane Arnold <(E-Mail Removed)> wrote in message news:<Xns94F26A7A55D08notmenotmecoml@63.240.76.16> ...
> > DonMiche <(E-Mail Removed)> wrote in
> > news:dv2sc.13381$(E-Mail Removed):
> >
> > > With this particular laptop, Toshiba Tecra M1, I cannot get either of
> > > the following adapters to ping outside the MR814 router:
> > >
> > > Intel PRO/Wireless 2100 LAN 3B Mini PCI Adapter
> > > Avaya Gold
> >
> > What IP is the machine getting?
> >
> > What O/S?
>
> OS is Windows 2000
> I am getting 192.168.0.3 with my gateway set at 192.168.0.1. That's
> what's really weird about this problem...

Is the router's MAC list turned on and the Toshiba's MAC not on the list?
Maybe the router's address is no longer 192.168.0.1. Can you boot from a
CD and try to use it that way? Are there any other machines on the LAN you
can access? Try deleting the device in "Device Manager", then running
"Add/Remove Devices" to let the OS reinstall it. I've had to do that
several times with this NIC under XP.

--
-eben (E-Mail Removed)m home.tampabay.rr.com/hactar
Your pretended fear lest error might step in is like the man who
would keep all wine out of the country lest men should be drunk.
-- Oliver Cromwell