BSNL Modem Configuration [Help]

S

Spekter

Disciple
Hi guys,

I was having trouble connecting via my newly received modem from BSNL, a Teracom DSL699E9...so I went ahead and reset the device.

I don't really have much knowledge about the procedure,this is what I did to set it back up...

1.Set up a bridged connection as listed in the modem manual.

[VPI/VCI - 0/35 , Encapsulation Type - LLC/SNAP]

Though I am being able to connect,I am getting VERY high pings and very low speed.

Could someone please tell me what I may be doing wrong and the correct procedure for setting up the device/connection.
DNS - 208.67.222.222
Alternate - 208.67.220.220
[After trying 61.1.96.69]
Results of pingtest :
16052010.jpg

Thanks
 
try using

Google public DNS 8.8.8.8 and 8.8.4.4

OR open DNS 208.67.222.222 and 208.67.220.220

if you still get low speeds and high pings then get your cable checked & /

OR request BSNL Exchange to change the port connection at the server

I'd suggest to use command prompt to ping popular sites & paste the result(s) like this

Microsoft Windows [Version 6.0.6000]

Copyright (c) 2006 Microsoft Corporation. All rights reserved.

C:\Users\mvs>ping google.com

Pinging google.com [209.85.231.104] with 32 bytes of data:

Reply from 209.85.231.104: bytes=32 time=56ms TTL=57

Reply from 209.85.231.104: bytes=32 time=77ms TTL=56

Reply from 209.85.231.104: bytes=32 time=62ms TTL=57

Reply from 209.85.231.104: bytes=32 time=62ms TTL=57

Ping statistics for 209.85.231.104:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 56ms, Maximum = 77ms, Average = 64ms
Click to expand...
 
the better option I find is call BSNL customer care..

whenever I have modem/broadband connection making trouble I call them, they ask modem model and then tell the procedure..
 
Sorry for the late reply...net had been completely dysfunctional.

Tried 'Open' as well as 'Google' DNS as suggested,none of them made a difference.

Ping Results :

C:\>ping Google

Pinging Google [209.85.231.104] with 32 bytes of data:

Reply from 209.85.231.104: bytes=32 time=83ms TTL=56

Reply from 209.85.231.104: bytes=32 time=82ms TTL=55

Reply from 209.85.231.104: bytes=32 time=82ms TTL=56

Reply from 209.85.231.104: bytes=32 time=83ms TTL=56

Ping statistics for 209.85.231.104:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 82ms, Maximum = 83ms, Average = 82ms

C:\>ping www.facebook.com

Pinging a2047.w7.akamai.net [210.212.26.19] with 32 bytes of data:

Reply from 210.212.26.19: bytes=32 time=228ms TTL=61

Reply from 210.212.26.19: bytes=32 time=230ms TTL=61

Reply from 210.212.26.19: bytes=32 time=231ms TTL=61

Reply from 210.212.26.19: bytes=32 time=233ms TTL=61

Ping statistics for 210.212.26.19:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 228ms, Maximum = 233ms, Average = 230ms

C:\>ping YouTube - Broadcast Yourself.

Pinging youtube-ui.l.google.com [64.233.183.93] with 32 bytes of data:

Reply from 64.233.183.93: bytes=32 time=331ms TTL=48

Reply from 64.233.183.93: bytes=32 time=343ms TTL=48

Reply from 64.233.183.93: bytes=32 time=328ms TTL=48

Reply from 64.233.183.93: bytes=32 time=355ms TTL=48

Ping statistics for 64.233.183.93:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 328ms, Maximum = 355ms, Average = 339ms

C:\>ping Vimeo, Video Sharing For You

Pinging vimeo.com [66.235.126.128] with 32 bytes of data:

Reply from 66.235.126.128: bytes=32 time=328ms TTL=246

Reply from 66.235.126.128: bytes=32 time=328ms TTL=246

Reply from 66.235.126.128: bytes=32 time=327ms TTL=246

Reply from 66.235.126.128: bytes=32 time=328ms TTL=246

Ping statistics for 66.235.126.128:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 327ms, Maximum = 328ms, Average = 327ms

C:\>ping Speedtest.net - The Global Broadband Speed Test

Pinging Speedtest.net - The Global Broadband Speed Test [69.17.117.207] with 32 bytes of data:

Reply from 69.17.117.207: bytes=32 time=245ms TTL=52

Reply from 69.17.117.207: bytes=32 time=245ms TTL=52

Reply from 69.17.117.207: bytes=32 time=245ms TTL=52

Reply from 69.17.117.207: bytes=32 time=246ms TTL=52

Ping statistics for 69.17.117.207:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 245ms, Maximum = 246ms, Average = 245ms

On a configured DLink 502T ADSL modem now with Rs 500 (2MBPS Dataone plan.)

Are my pings okay and what sort of speeds should I expect?

Thank you both for your replies.
 
^ above ping results appear to be fine for me ! although it is a 2mbps connection ,

you can expect to download a 10MB file in 2 minutes as download speed depends

on many factors including server speed ...
 
Speed/ping readings seem to have gotten better.

837966011.png


837966821.png


837967312.png


Earlier pings were in the region of 1k.Despite these improved readings,video buffering is taking a while and not getting more that 70-120 kbps on RS/Hotfile downloads.Is this because of the capped speed for free users?

Also well seeded torrents rarely go above 100-120 kbps(if lucky.)

[Verified on both Windows without Firewall also on a Linux system without Firewall,so I don't think it's a port issue on my side.]
 
Back
Top