Belkin F5D7234-4 Router Sporadically Connected?
in [Wireless Internet]
|
From: Kaimbridge on 21 Sep 2009 13:46 On Sep 20, 9:23 pm, Char Jackson <n...(a)none.invalid> wrote: > On Thu, 17 Sep 2009 12:46:22 -0700 (PDT), Kaimbridge > <kaimbri...(a)gmail.com> wrote: >> On Sep 16, 1:41 am, Kaimbridge <kaimbri...(a)gmail.com> wrote: >>> On Sep 2, 9:02 pm, Char Jackson <n...(a)none.invalid> wrote: > >> <snip> >>>> Looks like DNS so far. I would look there first, especially if >>>> you're asking the router to relay DNS requests. > >>> Okay, I've tried some "ping"-ing and "tracert"-ing and, where > >>> WAN IP = ##.##.40.249 and Default Gateway = ##.##.40.1, > >>> using the gateway seems to work okay, but using the WAN IP >>> mostly was unreachable except for one tracert which snagged >>> a hit on the 13th "hop" (and none succeeded using the >>> "regular" IP). >>> So if it is a DNS issue, would it be the router or the ISP >>> (ComCast)...or either? > >> Okay, I tried plugging the host's modem into the netbook and >> it works fine (after recycling, of course). >> After disconnecting the modem (i.e., becoming "wireless" again), >> I tried pinging ##.##40.1 and got >> "Reply from 192.168.2.1: Destination net unreachable." >> After reconnecting the host computer back to the modem, before >> recycling, I "pung" and got >> "Destination host unreachable." >> After recycling, ##.##.40.1 "pung" okay. >> Then when I tried ##.##.44.19 (the netbook's given "IP address"), >> it came back "Request timed out." >> When I tracert'ed it, >> 1-30 = "* * * Request timed out." >> But when I tracert'ed ##.##.40.1, >> "1 * * * Request timed out." >> "2 >10ms >10ms >20ms ##.##.40.1" >> I got the same result several times (first hit timed out but >> second >> took less than 10-20ms). > > I'm sorry, but I can't quite follow what you're doing. Between > the obfuscated IP's and the strange terms like "host's modem" > and "pung", I guess I'm easily distracted. "##.##.44.19" and "##.##.40.1" have the same left sections ("66.30."--I was just trying not to show the whole number, in terms of it being googled or whatever); by "host's modem", I just meant the wired computer's ISP cable modem and as for "pung", I was just trying to be funny ("pung" = "pinged" P=). Sorry about that. P=/ > Having said that, your latest description makes it look a little > more serious than just DNS issues. If I'm following you even > partially, it looks like the router is crapping out. But then, as pointed out earlier, why would it hold a streaming connection. Also, it has "Skype" on it, and that also does connect, sometimes disconnecting for up to a few minutes, then reconnects?!? In any event, it (the netbook) is still under warranty from Best Buy, so she may just take it to the Geek Squad and see what they say! (FYI, they just left again with the netbook for a week or so, so I won't have access to it, for now). ~Kaimbridge~ ----- WikipediaContributor Home Page: http://en.wikipedia.org/wiki/User:Kaimbridge ***** Void Where Permitted; Limit 0 Per Customer. *****
From: Char Jackson on 21 Sep 2009 17:26 On Mon, 21 Sep 2009 10:46:21 -0700 (PDT), Kaimbridge <kaimbridge(a)gmail.com> wrote: >On Sep 20, 9:23 pm, Char Jackson <n...(a)none.invalid> wrote: >> Having said that, your latest description makes it look a little >> more serious than just DNS issues. If I'm following you even >> partially, it looks like the router is crapping out. > >But then, as pointed out earlier, why would it hold a streaming >connection. Also, it has "Skype" on it, and that also does >connect, sometimes disconnecting for up to a few minutes, then >reconnects?!? It still looks like the router to me, partly because of your description of how it's acting and partly because it's a Belkin. >In any event, it (the netbook) is still under warranty from >Best Buy, so she may just take it to the Geek Squad and see what >they say! >(FYI, they just left again with the netbook for a week or so, so I >won't have access to it, for now). Like I said before, just bypass the router to troubleshoot this further. If everything works without the router, but craps out when the router is in the path, you'll have a good indication that it's the router.
From: John Navas on 21 Sep 2009 17:37
On Wed, 2 Sep 2009 11:05:54 -0700 (PDT), Kaimbridge <kaimbridge(a)gmail.com> wrote in <85da4cc4-9a8c-457a-945d-f0d90205554b(a)o9g2000yqj.googlegroups.com>: >A few weeks ago I got a Belkin F5D7234-4 Wireless-G router >(firmware version 4.00.05, boot version 0.03), for an Eee PC >netbook that is mainly used for traveling. >I first set up the wired host computer (Win XP, 5.1.2600, SP3), >using Belkin's CD set-up program, then verified settings via the >"on-line" router IP set-up page ( http://192.168.2.1 ). >I then tried logging the netbook on to the router (yes, fully >secured with password P=). >Connection was reported as successful, at which time I shut off >the SSID broadcast: The WiFi icon flashed "connection successful, >reception excellent!" >So I tried for a couple of sites (such as www.google.com), but >nothing happened (they timed out). After taking the manual's >suggestion of pulling the power plug out of the router's back, >waiting a few seconds, plugging it back in and waiting 20-30 >seconds, until all of the lights come back on (i.e., "recycle" the >router). That seemed to do the trick...the first few site attempts. >But, then, attempts again timed out. So, IIRC, I again recycled the >router, with similar results. >Up at the campground and here, in town at a local cafe, the >netbook's WiFi works fine, so the problem appears to be host >computer's end, with the router. >... Yep. I encountered a similar problem with the same wireless router and an Acer Aspire One netbook, isolated it down to the Belkin wireless router, and solved it by replacing the Belkin wireless router. Switch, don't fight. -- Best regards, FAQ for Wireless Internet: <http://wireless.navas.us> John FAQ for Wi-Fi: <http://wireless.navas.us/wiki/Wi-Fi> Wi-Fi How To: <http://wireless.navas.us/wiki/Wi-Fi_HowTo> Fixes to Wi-Fi Problems: <http://wireless.navas.us/wiki/Wi-Fi_Fixes> |