Problems with 220BX (AIRTEL)

C

ComradE_BeaN

Discoverer
Modem : 220BX
Connection : 128kbps unlimited
OS : WinXP corp with SP2
Interference: USB(currently)
Security : Zonelabs Antivirus + Antispyware + Firewall

the connec gets interupted @ random times.
no time specification or anything ... when this happens the ping to 192.168.1.1 gets timed out...
if i go to network connections --- > disable the n/w & enable it again --- > it gets fixed for sometime..& again the same thing happens after a few time.

Called up CC.. they asked me to install patch from beetelmodems.com , which i did he said he has taken some shots of my motem (remotely) & process it & get back to me...but i am running out of patience...
The thing is this did not happn when i was on ETHERNET conn with the same modem... <_<

Anyone experienced this?? any recomendadtions other than going back to eth connection ..?
i dont think its' a problem with my USB slot .. cause all other USB devices just work fine....so is it the problem with the OS..?

Anyway to uninstall & reinstall the whole USB drivers/system drivers for WINXP without reinstalling the OS?
 
i have the same modem and i was running it through the usb port for a few days. personally, i wouldn't recommend it at all. for some odd reason, my download speed dropped by 10kbps (almost as if it were capped at 50kbps instead of the 58-60 that i usually get at night) and my pings to servers increased by about 20ms. i went back to ethernet immediately. no problems at all. i haven't installed any patches either.
 
220BX is working perfectly fine for me. I keep it on for days, then give it a 2-6 hr break as its steaming hot then put it back on. Get easily 55kBps at nights.

If the problem continous just ask the Airtel guys to send it someone, ask them to change the modem.
 
ive been using the same modem with usb without any problems for 6 months now. get very good speeds (29-30k). maybe the problem is with ur particular modem..
 
@checksum : maybe...i'll see if this happens again within a hour.i'm getting it replaced..
@yuvraj: no...it is not abt bandwidth drop,,
@ that time...even ipconfig doesnt even give any results...:(
 
me also using the same modem... gives lots of troubles on USB...frquesnt disconnections being the major one...so i put it on ethernet and it works perfectly.
 
I got the same problem using ethernet a few days back, but i called up and they said they were havin server problems so thats why. Other than that its been working perfectly fine.
 
there are 2 nics ....1 is for a local LAN (friends)& other for connetion to a Laptop.....hence thought of using this USB interface...since last night..there has been no disconnections...:confused:..
is this the same with USB to ETH CONVERTERS ???anyone using a usb to eth converter..?
 
just a thought.. maybe its a problem with the drivers? like i said, when i was usb, it was like my speed was CAPPED at 10kbps. all my downloads used to climb upto 50kbps and get stuck there.

@checksum, do you play games online? have you checked pings to servers on both ethernet and usb? i guess i have the same plan as you.. (airtel chennai) and my pings were about 60 to 80 on usb to all the indian servers. switching to ethernet dropped them to 50s. very weird.

could someone else try switching between usb and ethernet to see if there are any problems?
 
super_saiyan said:
@ params7 : u using USB interference or eth connection?
Click to expand...

ethernet, with no dialing chakar and it was the only way to connect to the PS2.

But the airtel guys took the damn USB cable with them but left the driver CD with me, lol morons. I'll be asking for the USB cable back soon so i can test which mode performs better on 220BX, which i'm afraid is subjective to differen't PC's.
 
not much difference in ping to google servers ..
this is from ETHERNET conn
---------------------------------------------
Pinging www.l.google.com [66.102.7.147] with 32 bytes of data:

Reply from 66.102.7.147: bytes=32 time=272ms TTL=239
Reply from 66.102.7.147: bytes=32 time=276ms TTL=239
Reply from 66.102.7.147: bytes=32 time=268ms TTL=239
Reply from 66.102.7.147: bytes=32 time=270ms TTL=239
Reply from 66.102.7.147: bytes=32 time=277ms TTL=239
Reply from 66.102.7.147: bytes=32 time=276ms TTL=239
Reply from 66.102.7.147: bytes=32 time=269ms TTL=239
Reply from 66.102.7.147: bytes=32 time=272ms TTL=239
Reply from 66.102.7.147: bytes=32 time=269ms TTL=239
Reply from 66.102.7.147: bytes=32 time=273ms TTL=239
Reply from 66.102.7.147: bytes=32 time=272ms TTL=239
Reply from 66.102.7.147: bytes=32 time=272ms TTL=239

Ping statistics for 66.102.7.147:
Packets: Sent = 12, Received = 12, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 268ms, Maximum = 277ms, Average = 272ms
----------------------------------------------

this is from USB connection
----------------------------------------------
Pinging www.l.google.com [66.102.7.99] with 32 bytes of data:

Reply from 66.102.7.99: bytes=32 time=275ms TTL=239
Reply from 66.102.7.99: bytes=32 time=276ms TTL=239
Reply from 66.102.7.99: bytes=32 time=283ms TTL=239
Reply from 66.102.7.99: bytes=32 time=269ms TTL=239
Reply from 66.102.7.99: bytes=32 time=275ms TTL=239
Reply from 66.102.7.99: bytes=32 time=272ms TTL=239
Reply from 66.102.7.99: bytes=32 time=269ms TTL=239
Reply from 66.102.7.99: bytes=32 time=278ms TTL=239
Reply from 66.102.7.99: bytes=32 time=277ms TTL=239
Reply from 66.102.7.99: bytes=32 time=274ms TTL=239
Reply from 66.102.7.99: bytes=32 time=267ms TTL=239

Ping statistics for 66.102.7.99:
Packets: Sent = 11, Received = 11, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 267ms, Maximum = 283ms, Average = 274ms
----------------------------------------------------
 
Dude the network latency of the Ping times on airtel connection is supposed to be less 100ms. Call up the CC ppl and request them to change the cable.
This might as well solve the problem related to disconnections. Ping time for the DNS server for my connection remains less than 100ms, I am also on Airtel (128 Kbps).
 
I too would advise you to use the Eth port rather then the USB port... I have setted up mine in such a way that i dont need to dial and the modem, it does that automatically as soon as i power on the modem irrespective of the PC being off or on...

Also the connection drops happenes if you have disturbance in your telephone line... Get that checked... More often then not it is the telephone line rather then the modem being faulty :)...
 
@overclocked... : If u see my posts in the last page closely .. i had pinged to www.google.co.in.Dns servers will always give best latency to the hosts..thats no surprise...here is the ping result for me (USB)...
Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : USB Remote NDIS Device
Physical Address. . . . . . . . . : 00-08-5C-58-E0-80
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.1.2
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1
DHCP Server . . . . . . . . . . . : 192.168.1.1
DNS Servers . . . . . . . . . . . : 192.168.1.1
Lease Obtained. . . . . . . . . . : Saturday, April 29, 2006 11:59:

Lease Expires . . . . . . . . . . : Sunday, April 30, 2006 11:59:17

C:\Documents and Settings\Girish>ping 192.168.1.1

Pinging 192.168.1.1 with 32 bytes of data:

Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64

Ping statistics for 192.168.1.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 1ms, Maximum = 1ms, Average = 1ms
Also the connection drops happenes if you have disturbance in your telephone line... Get that checked... More often then not it is the telephone line rather then the modem being faulty ...
Click to expand...
The thing is the disconnections is happening in the USB conn only..not in ETHERNET conn...:(..
so i'm confused if its' the problem with the modem or the USB drivers.... ! !

i applied the autodialer patch from beetelmodems.com & till now there is no disconnections...:)... i think the problem is solved..:).
lemme see for a few more hours. :D
 
super_saiyan said:
@overclocked... : If u see my posts in the last page closely .. i had pinged to www.google.co.in.Dns servers will always give best latency to the hosts..thats no surprise...here is the ping result for me (USB)...
Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : USB Remote NDIS Device
Physical Address. . . . . . . . . : 00-08-5C-58-E0-80
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.1.2
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1
DHCP Server . . . . . . . . . . . : 192.168.1.1
DNS Servers . . . . . . . . . . . : 192.168.1.1
Lease Obtained. . . . . . . . . . : Saturday, April 29, 2006 11:59:

Lease Expires . . . . . . . . . . : Sunday, April 30, 2006 11:59:17

C:\Documents and Settings\Girish>ping 192.168.1.1

Pinging 192.168.1.1 with 32 bytes of data:

Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64

Ping statistics for 192.168.1.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 1ms, Maximum = 1ms, Average = 1ms

:D
Click to expand...

Dude 192.168.1.1 IP is used for private LAN that in this case is your modem and not the DNS server. Ping the DNS server and post the times.
 
pinging the primary DNS server & secondary server from USB
-------------------------------------------------------
primary

Pinging 203.145.184.32 with 32 bytes of data:

Reply from 203.145.184.32: bytes=32 time=37ms TTL=249
Reply from 203.145.184.32: bytes=32 time=32ms TTL=249
Reply from 203.145.184.32: bytes=32 time=35ms TTL=249
Reply from 203.145.184.32: bytes=32 time=33ms TTL=249

Ping statistics for 203.145.184.32:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss)
Approximate round trip times in milli-seconds:
Minimum = 32ms, Maximum = 37ms, Average = 34ms
--------------------------------------------------------
secondary server

Pinging 202.56.250.5 with 32 bytes of data:

Reply from 202.56.250.5: bytes=32 time=39ms TTL=249
Reply from 202.56.250.5: bytes=32 time=39ms TTL=249
Reply from 202.56.250.5: bytes=32 time=41ms TTL=249
Reply from 202.56.250.5: bytes=32 time=38ms TTL=249

Ping statistics for 202.56.250.5:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 38ms, Maximum = 41ms, Average = 39ms
---------------------------------------------------------
pinging the primary DNS server & secondary server from Ethernet adapter
----------------------------------------------------
primary DNS

Pinging 203.145.184.32 with 32 bytes of data:

Reply from 203.145.184.32: bytes=32 time=33ms TTL=249
Reply from 203.145.184.32: bytes=32 time=33ms TTL=249
Reply from 203.145.184.32: bytes=32 time=32ms TTL=249
Reply from 203.145.184.32: bytes=32 time=30ms TTL=249

Ping statistics for 203.145.184.32:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 30ms, Maximum = 33ms, Average = 32ms
---------------------------------------------------------
secondary server

Pinging 202.56.250.5 with 32 bytes of data:

Reply from 202.56.250.5: bytes=32 time=40ms TTL=249
Reply from 202.56.250.5: bytes=32 time=43ms TTL=249
Reply from 202.56.250.5: bytes=32 time=39ms TTL=249
Reply from 202.56.250.5: bytes=32 time=41ms TTL=249

Ping statistics for 202.56.250.5:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 39ms, Maximum = 43ms, Average = 40ms

----------------------------------------------------
i think my USB disconnect issue is fixed after applying that patch....net up & running from ~10hrs without any problems :)
 
Back
Top