attention all dogs with bones.
not great news but just a (boring)update. After paying $15 to return
original 8011 router to USR after 10days I received a replacement
router, an upgraded model even - the 8022 22Mbps.
unfortunately they didn't include an AC adapter and the AC adapter
they told me to NOT return with the old router doesn't seem to work.
the NEW router doesn't power up at all, not a flicker and it appears
to need a different AC adapter (needs a 5Vdc 2A and the old adapter is
12Vdc 1500mA.) sooooo, we are back to the drawing board.
a call to USR nad they are apparently sending ANOTHER router AND the
correct AC adapter.
don't touch that dial. the saga continues.
Peter
Sylvan Butler <Zsbutler+(E-Mail Removed) > wrote in message news:<slrnbhgcot.8m5.Zsbutler+noZs_0307@hpb13799Z. Zboi.hpZ.com.invalid>...
> On 17 Jul 2003 21:23:40 -0700, peter <(E-Mail Removed)> wrote:
> > Sylvan Butler <Znospam+(E-Mail Removed) d> wrote in message news:<slrnbhdlor.vdm.Znospam+(E-Mail Removed) boi.hpZ.com.invalid>...
> >> Also, WEP can be tricky, especially with different makes of
> >> equipment (not necessarily brands, but the underlying OEM). I'd
> >> recommend disabling it when trying to add anything new to your WLAN.
> >>
> >> The problem sounds like WEP or mac filtering but it may be just DHCP
> >> / IP address related...
>
> > I am not sure how vefify that DHCP on the router is seeing requests.
> > here is the only form of a Log that I could find (but I don't really
> > know what it means):
>
> Nothing helpful. 
>
>
> > WAN Type: PPP over Ethernet (V2.0)
> > Display time: Friday, July 18, 2003 12:14:09 AM
> >
> > * Restarted by 192.168.123.114
>
> That is probably the IP address of the system you used to clear the
> log or restart the router.
>
> > * DOD:TCP trigger from 192.168.123.114:1829 to 69.20.5.22:80
> > Friday, July 18, 2003 12:04:12 AM PPPoE start to dial-up
>
> Dial-On-Demand (DOD) is triggered, so PPP-over-Ethernet (PPPoE) is
> starting.
>
> > * PADT sent
> > * PADI sent
> > * PADO recv 0006 62031020044491-sms8-toronto63
> > * PADR sent
> > * PADS recv 8002 DE83
> > * PAP3: OK
>
> Those are PPP phases.
>
> > * IPCP3: IP is 216.221.57.36
> > * IPCP3: DNS0 is 206.123.6.11
> > * IPCP3: DNS1 is 206.123.6.10
>
> And those are the results of the connection -- your assigned IP
> address on your provider's network, and the two DNS servers
> configured by your provider.
>
>
> > So, I can conclude that none of the adapters are completely defective.
>
> Yup.
>
> > I'll keep you posted though. Have you ever heard of such wacky
> > incompatibility issues between adapters and routers?
>
> Not in general, no. And if both are "802.11b" there is little
> chance of it, and if both are "WiFi" (Wireless Fidelity) certified
> then that chance is supposed to be eliminated.
>
> The only thing left for compatibility problems is the WEP (or other
> authentication or privacy) settings I alluded to before.
>
> Sounds to me like the USR rep knows of something and they don't want
> to admit to it so they offer a replacement. If they admit then
> everybody, even customers who are not having problems, will demand a
> replacment. $$$. So they treat the complaints one at a time...
> (Very typical customer support model.)
>
> Networking has a level of complexity that adds to the chance of
> problems. Wireless adds a bit more. Often it just works (as
> witnessed by all the access points left operating at their factory
> default configuration) but sometimes it doesn't.
>
> sdb