This happens to me frequently and to others in my area.
ut300-r2u (Small).jpg
What is reason behind this ?
Is this a issue with the customer's modem or with the BSNL ?![]()
This happens to me frequently and to others in my area.
ut300-r2u (Small).jpg
What is reason behind this ?
Is this a issue with the customer's modem or with the BSNL ?![]()
seems OK. Test in Tools. similar modem.
On "Always On" PPP/PPPoE mode. "Pass" In Diagnostics page also.
2.
Test PING command externally in your computer.
6:44 PM 3/16/2011
C:\Users\essbebe >ping 192.168.1.1
Pinging 192.168.1.1 with 32 bytes of data:
Reply from 192.168.1.1: bytes=32 time=3ms TTL=63
Reply from 192.168.1.1: bytes=32 time=2ms TTL=63
Reply from 192.168.1.1: bytes=32 time=2ms TTL=63
Reply from 192.168.1.1: bytes=32 time=2ms TTL=63
Ping statistics for 192.168.1.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 2ms, Maximum = 3ms, Average = 2ms
Last edited by essbebe; 03-16-11 at 06:45 PM.
WA3002-G4 QUICK GUIDE=>20 MODEMS 74,000+45,400 hits
*Beetel220BX/450TCI type !****
*AN1020-21 type models ****23,700 hits ** BSNL LINKS**9900******USAGE check ** 54,600
probably the problem is with ur computer since i faced the same problem and the reason was my computer
Please see the Device Information page of your router.
I think this test is happening on BSNL's side of the router, not the home LAN side. Thus, 192.168.1.1 has nothing to do with this.
The device info, or status, as appropriate to your model, should show you the router's default gateway on the WAN side. It is the ping to that which is failing.
Whilst you can try pinging it from your PC, if the router can't reach it, it is unlikely that you will.
This is a BSNL problem. One for the Helpdesk.
duplicate post deleted.
I feel, The "PING" test is same as OS cmd application.
we access the cmd from modem.
I entered 192.168.1.1 ) modem to computer)
Device info bsnl gateway
google dns 8.8.8.8
If not functioning in Modem Tools, problem may be on OS side.
"Fail" in Diagnostics may also indicate problem in connection.
You can verify. Unplug the telephone connection. That ping, along with a few other things, will now fail.I feel, The "PING" test is same as OS cmd application.
Having tried that (it did fail as I predicted), I noticed the magic words above that section of the test screen:
Test the connection to your Internet Service Provider
Aha! Voila! I should have seen before.
The first section is called Test the connection to your local network
By the way: your router need have no idea what your PC's default gateway is.
Removed cable rj11 to modem. ( no connection to BSNL)
Ping 192.168.1.1 OK as reported earlier. ( from Tools menu)
tests the connection from modem to laptop.
Also direct :
http://192.168.1.1/pingtrace.html
Obviously Ping DNS or Gateway won't work.
("Other things in "Diagnostics" result depend on Internet connection.( not the point under discussion )
You can verify. Unplug the telephone connection. That ping, along with a few other things, will now fail.
Please follow my reasoning, my example, and, most important, my quote from the screen (Test the connection to your Internet Service Provider) carefuly. You picking up on two words, "default gateway," and thinking they refer to one thing. They don't: they refer to another.
Try it without DHCP (I don't use it). How, then, would your router know what your PC's "default gateway" was? It wouldn't, and it is not relevant to your router to know that anyway. It could be some other router.
Also considerMore evidence that it is not one guy's LAN problem.This happens to me frequently and to others in my area.
will wait for feedback from @Sledgehammer.
Checked the stats today. The Default Gateway is working fine.
I'm not having any problem with pinging the modem. (Also I'm not using DHCP.)
Done a traceroute to google.com. No packet losses. Everything is fine.
But the Default Gateway usually Fails even when the Internet is working fine. Don't know the reason behind it.
OK.
Been away for ten days. How are things now?
Keep fingers crossed. Could be BSNL fixed something their end.
Hopefuly, problem is resolved.
There are currently 1 users browsing this thread. (0 members and 1 guests)