Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

Constant Disconnecting.


  • Please log in to reply
13 replies to this topic

#1 ATARi

ATARi

  • Members
  • 29 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:New York
  • Local time:08:26 AM

Posted 12 February 2009 - 01:08 AM

Hi, I've recently started having this random and constant random disconnects. At first I thought it was because of high traffic and the time I was using the internet, but recently this just started to happen more frequently at any time. Sometimes I'll have no problems with disconnecting but then other times I get disconnected every few mintues or so.

I'm currently on the Verizon DSL High Speed Internet plan, with 2 computers and a laptop. Running the internet with a Westell Versalink 327W wireless router though all three computers are wired to the modem/router.

I've called up Verizon to see the problem and the two times I've called they just tell me I have a virus; I can't really see how a virus can cause this to all 3 computers. I've ran virus scans to see no virus's infecting anything. I've also checked all my filters and seems they are all secured and installed. Right now I'm pondering that the problem is probably my modem? I've had the modem for atleast a few years. Would that solve the problem?

I hope what I described would help solve any answers and of course any help would be greatly appreciated!

BC AdBot (Login to Remove)

 


#2 DaffyKantReed

DaffyKantReed

  • Members
  • 190 posts
  • OFFLINE
  •  
  • Location:Vancouver, BC
  • Local time:04:26 AM

Posted 12 February 2009 - 07:39 AM

Hi, I've recently started having this random and constant random disconnects. At first I thought it was because of high traffic and the time I was using the internet, but recently this just started to happen more frequently at any time. Sometimes I'll have no problems with disconnecting but then other times I get disconnected every few mintues or so.

I'm currently on the Verizon DSL High Speed Internet plan, with 2 computers and a laptop. Running the internet with a Westell Versalink 327W wireless router though all three computers are wired to the modem/router.

I've called up Verizon to see the problem and the two times I've called they just tell me I have a virus; I can't really see how a virus can cause this to all 3 computers. I've ran virus scans to see no virus's infecting anything. I've also checked all my filters and seems they are all secured and installed. Right now I'm pondering that the problem is probably my modem? I've had the modem for atleast a few years. Would that solve the problem?


Start>run>cmd>OK

At the command prompt type "ping -n 100 www.google.com" without the quotation marks. Press Enter.

Repeat using "ping -n 100 " without the quotation marks.

Post back to the thread with your results.


Also see http://www.dslreports.com/forum/remark,13747078

Edited by The weatherman, 12 February 2009 - 05:45 PM.


#3 tos226

tos226

    BleepIN--BleepOUT


  • Members
  • 1,568 posts
  • OFFLINE
  •  
  • Gender:Female
  • Location:LocalHost
  • Local time:08:26 AM

Posted 12 February 2009 - 07:38 PM

Do you use a firewall and if so which?
Maintaining a connection is often a problem when the firewall was not configured properly according to instructions.

Ignore Verizon telling you have a virus. They just want to sell you their security product for $7 a month :thumbsup:
You may have a virus, of course, but I doubt it.

Added on edit:
Perhaps this will help - also Verizon issue
http://www.wilderssecurity.com/showthread.php?p=1394609
post #19 ends the story

Edited by tos226, 12 February 2009 - 09:12 PM.


#4 tahitianflower

tahitianflower

  • Members
  • 5 posts
  • OFFLINE
  •  
  • Gender:Female
  • Location:In the 5th Dimention
  • Local time:06:26 AM

Posted 13 February 2009 - 03:00 AM

I'm having a disconnect problem myself, not every few minutes though and I don't think any of the other computers in my home are experiencing the same problem either. Can you post your hi-jack this file? if you need to download it you can go here: http://www.download.com/Trend-Micro-Hijack...4-10227353.html and if you need more information watch the video tutorial.

#5 ATARi

ATARi
  • Topic Starter

  • Members
  • 29 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:New York
  • Local time:08:26 AM

Posted 13 February 2009 - 06:37 AM

Thanks for the replies!

To: DaffyKentReed
My results are:
Microsoft Windows [Version 6.0.6001]
Copyright © 2006 Microsoft Corporation. All rights reserved.

C:\Users\DennisL>ping -n 100 www.google.com

Pinging www.l.google.com [64.233.169.104] with 32 bytes of data:
Reply from 64.233.169.104: bytes=32 time=32ms TTL=244
Reply from 64.233.169.104: bytes=32 time=32ms TTL=244
Reply from 64.233.169.104: bytes=32 time=32ms TTL=244
Reply from 64.233.169.104: bytes=32 time=31ms TTL=244
Reply from 64.233.169.104: bytes=32 time=32ms TTL=244
Reply from 64.233.169.104: bytes=32 time=32ms TTL=244
Reply from 64.233.169.104: bytes=32 time=32ms TTL=244
Reply from 64.233.169.104: bytes=32 time=32ms TTL=244
Reply from 64.233.169.104: bytes=32 time=32ms TTL=244
Reply from 64.233.169.104: bytes=32 time=32ms TTL=244
Reply from 64.233.169.104: bytes=32 time=32ms TTL=244
Reply from 64.233.169.104: bytes=32 time=31ms TTL=244
Reply from 64.233.169.104: bytes=32 time=54ms TTL=244
Reply from 64.233.169.104: bytes=32 time=280ms TTL=244
Reply from 64.233.169.104: bytes=32 time=287ms TTL=244
Reply from 64.233.169.104: bytes=32 time=280ms TTL=244
Reply from 64.233.169.104: bytes=32 time=285ms TTL=244
Reply from 64.233.169.104: bytes=32 time=289ms TTL=244
Reply from 64.233.169.104: bytes=32 time=283ms TTL=244
Reply from 64.233.169.104: bytes=32 time=291ms TTL=244
Reply from 64.233.169.104: bytes=32 time=284ms TTL=244
Reply from 64.233.169.104: bytes=32 time=283ms TTL=244
Reply from 64.233.169.104: bytes=32 time=278ms TTL=244
Reply from 64.233.169.104: bytes=32 time=282ms TTL=244
Reply from 64.233.169.104: bytes=32 time=286ms TTL=244
Reply from 64.233.169.104: bytes=32 time=277ms TTL=244
Reply from 64.233.169.104: bytes=32 time=288ms TTL=244
Reply from 64.233.169.104: bytes=32 time=285ms TTL=244
Reply from 64.233.169.104: bytes=32 time=290ms TTL=244
Reply from 64.233.169.104: bytes=32 time=289ms TTL=244
Reply from 64.233.169.104: bytes=32 time=281ms TTL=244
Reply from 64.233.169.104: bytes=32 time=281ms TTL=244
Reply from 64.233.169.104: bytes=32 time=285ms TTL=244
Reply from 64.233.169.104: bytes=32 time=284ms TTL=244
Reply from 64.233.169.104: bytes=32 time=291ms TTL=244
Reply from 64.233.169.104: bytes=32 time=287ms TTL=244
Reply from 64.233.169.104: bytes=32 time=292ms TTL=244
Reply from 64.233.169.104: bytes=32 time=285ms TTL=244
Reply from 64.233.169.104: bytes=32 time=277ms TTL=244
Reply from 64.233.169.104: bytes=32 time=283ms TTL=244
Reply from 64.233.169.104: bytes=32 time=278ms TTL=244
Reply from 64.233.169.104: bytes=32 time=290ms TTL=244
Reply from 64.233.169.104: bytes=32 time=281ms TTL=244
Reply from 64.233.169.104: bytes=32 time=286ms TTL=244
Reply from 64.233.169.104: bytes=32 time=294ms TTL=244
Reply from 64.233.169.104: bytes=32 time=290ms TTL=244
Reply from 64.233.169.104: bytes=32 time=282ms TTL=244
Reply from 64.233.169.104: bytes=32 time=313ms TTL=244
Reply from 64.233.169.104: bytes=32 time=279ms TTL=244
Reply from 64.233.169.104: bytes=32 time=299ms TTL=244
Reply from 64.233.169.104: bytes=32 time=284ms TTL=244
Reply from 64.233.169.104: bytes=32 time=301ms TTL=244
Reply from 64.233.169.104: bytes=32 time=296ms TTL=244
Reply from 64.233.169.104: bytes=32 time=291ms TTL=244
Reply from 64.233.169.104: bytes=32 time=285ms TTL=244
Reply from 64.233.169.104: bytes=32 time=306ms TTL=244
Reply from 64.233.169.104: bytes=32 time=327ms TTL=244
Reply from 64.233.169.104: bytes=32 time=279ms TTL=244
Reply from 64.233.169.104: bytes=32 time=283ms TTL=244
Reply from 64.233.169.104: bytes=32 time=289ms TTL=244
Reply from 64.233.169.104: bytes=32 time=284ms TTL=244
Request timed out.
Reply from 64.233.169.104: bytes=32 time=282ms TTL=244
Reply from 64.233.169.104: bytes=32 time=284ms TTL=244
Reply from 64.233.169.104: bytes=32 time=289ms TTL=244
Reply from 64.233.169.104: bytes=32 time=288ms TTL=244
Reply from 64.233.169.104: bytes=32 time=281ms TTL=244
Reply from 64.233.169.104: bytes=32 time=291ms TTL=244
Reply from 64.233.169.104: bytes=32 time=283ms TTL=244
Reply from 64.233.169.104: bytes=32 time=289ms TTL=244
Reply from 64.233.169.104: bytes=32 time=281ms TTL=244
Reply from 64.233.169.104: bytes=32 time=289ms TTL=244
Reply from 64.233.169.104: bytes=32 time=281ms TTL=244
Reply from 64.233.169.104: bytes=32 time=286ms TTL=244
Reply from 64.233.169.104: bytes=32 time=281ms TTL=244
Reply from 64.233.169.104: bytes=32 time=289ms TTL=244
Reply from 64.233.169.104: bytes=32 time=288ms TTL=244
Reply from 64.233.169.104: bytes=32 time=287ms TTL=244
Reply from 64.233.169.104: bytes=32 time=280ms TTL=244
Reply from 64.233.169.104: bytes=32 time=285ms TTL=244
Reply from 64.233.169.104: bytes=32 time=279ms TTL=244
Reply from 64.233.169.104: bytes=32 time=285ms TTL=244
Reply from 64.233.169.104: bytes=32 time=293ms TTL=244
Reply from 64.233.169.104: bytes=32 time=285ms TTL=244
Reply from 64.233.169.104: bytes=32 time=293ms TTL=244
Reply from 64.233.169.104: bytes=32 time=278ms TTL=244
Reply from 64.233.169.104: bytes=32 time=283ms TTL=244
Reply from 64.233.169.104: bytes=32 time=283ms TTL=244
Reply from 64.233.169.104: bytes=32 time=283ms TTL=244
Reply from 64.233.169.104: bytes=32 time=288ms TTL=244
Reply from 64.233.169.104: bytes=32 time=283ms TTL=244
Reply from 64.233.169.104: bytes=32 time=288ms TTL=244
Reply from 64.233.169.104: bytes=32 time=282ms TTL=244
Reply from 64.233.169.104: bytes=32 time=289ms TTL=244
Reply from 64.233.169.104: bytes=32 time=281ms TTL=244
Reply from 64.233.169.104: bytes=32 time=285ms TTL=244
Reply from 64.233.169.104: bytes=32 time=289ms TTL=244
Reply from 64.233.169.104: bytes=32 time=291ms TTL=244
Reply from 64.233.169.104: bytes=32 time=284ms TTL=244
Reply from 64.233.169.104: bytes=32 time=289ms TTL=244

Ping statistics for 64.233.169.104:
Packets: Sent = 100, Received = 99, Lost = 1 (1% loss),
Approximate round trip times in milli-seconds:
Minimum = 31ms, Maximum = 327ms, Average = 253ms

C:\Users\DennisL>ping -n 100 www.google.com

Pinging www.l.google.com [64.233.169.104] with 32 bytes of data:
Reply from 64.233.169.104: bytes=32 time=31ms TTL=244
Reply from 64.233.169.104: bytes=32 time=32ms TTL=244
Reply from 64.233.169.104: bytes=32 time=32ms TTL=244
Reply from 64.233.169.104: bytes=32 time=32ms TTL=244
Reply from 64.233.169.104: bytes=32 time=32ms TTL=244
Reply from 64.233.169.104: bytes=32 time=32ms TTL=244
Reply from 64.233.169.104: bytes=32 time=32ms TTL=244
Reply from 64.233.169.104: bytes=32 time=32ms TTL=244
Reply from 64.233.169.104: bytes=32 time=32ms TTL=244
Reply from 64.233.169.104: bytes=32 time=32ms TTL=244
Reply from 64.233.169.104: bytes=32 time=32ms TTL=244
Reply from 64.233.169.104: bytes=32 time=32ms TTL=244
Reply from 64.233.169.104: bytes=32 time=31ms TTL=244
Reply from 64.233.169.104: bytes=32 time=32ms TTL=244
Reply from 64.233.169.104: bytes=32 time=32ms TTL=244
Reply from 64.233.169.104: bytes=32 time=33ms TTL=244
Reply from 64.233.169.104: bytes=32 time=32ms TTL=244
Reply from 64.233.169.104: bytes=32 time=32ms TTL=244
Reply from 64.233.169.104: bytes=32 time=33ms TTL=244
Reply from 64.233.169.104: bytes=32 time=32ms TTL=244
Reply from 64.233.169.104: bytes=32 time=32ms TTL=244
Reply from 64.233.169.104: bytes=32 time=32ms TTL=244
Reply from 64.233.169.104: bytes=32 time=32ms TTL=244
Reply from 64.233.169.104: bytes=32 time=31ms TTL=244
Reply from 64.233.169.104: bytes=32 time=31ms TTL=244
Reply from 64.233.169.104: bytes=32 time=32ms TTL=244
Reply from 64.233.169.104: bytes=32 time=32ms TTL=244
Reply from 64.233.169.104: bytes=32 time=33ms TTL=244
Reply from 64.233.169.104: bytes=32 time=32ms TTL=244
Reply from 64.233.169.104: bytes=32 time=32ms TTL=244
Reply from 64.233.169.104: bytes=32 time=32ms TTL=244
Reply from 64.233.169.104: bytes=32 time=32ms TTL=244
Reply from 64.233.169.104: bytes=32 time=31ms TTL=244
Reply from 64.233.169.104: bytes=32 time=32ms TTL=244
Reply from 64.233.169.104: bytes=32 time=32ms TTL=244
Reply from 64.233.169.104: bytes=32 time=32ms TTL=244
Reply from 64.233.169.104: bytes=32 time=32ms TTL=244
Reply from 64.233.169.104: bytes=32 time=32ms TTL=244
Reply from 64.233.169.104: bytes=32 time=32ms TTL=244
Reply from 64.233.169.104: bytes=32 time=32ms TTL=244
Reply from 64.233.169.104: bytes=32 time=34ms TTL=244
Reply from 64.233.169.104: bytes=32 time=32ms TTL=244
Reply from 64.233.169.104: bytes=32 time=32ms TTL=244
Reply from 64.233.169.104: bytes=32 time=33ms TTL=244
Reply from 64.233.169.104: bytes=32 time=32ms TTL=244
Reply from 64.233.169.104: bytes=32 time=32ms TTL=244
Reply from 64.233.169.104: bytes=32 time=32ms TTL=244
Reply from 64.233.169.104: bytes=32 time=32ms TTL=244
Reply from 64.233.169.104: bytes=32 time=33ms TTL=244
Reply from 64.233.169.104: bytes=32 time=32ms TTL=244
Reply from 64.233.169.104: bytes=32 time=285ms TTL=244
Reply from 64.233.169.104: bytes=32 time=282ms TTL=244
Reply from 64.233.169.104: bytes=32 time=288ms TTL=244
Reply from 64.233.169.104: bytes=32 time=280ms TTL=244
Reply from 64.233.169.104: bytes=32 time=286ms TTL=244
Reply from 64.233.169.104: bytes=32 time=284ms TTL=244
Reply from 64.233.169.104: bytes=32 time=285ms TTL=244
Reply from 64.233.169.104: bytes=32 time=281ms TTL=244
Reply from 64.233.169.104: bytes=32 time=287ms TTL=244
Reply from 64.233.169.104: bytes=32 time=282ms TTL=244
Reply from 64.233.169.104: bytes=32 time=287ms TTL=244
Reply from 64.233.169.104: bytes=32 time=288ms TTL=244
Reply from 64.233.169.104: bytes=32 time=252ms TTL=244
Reply from 64.233.169.104: bytes=32 time=294ms TTL=244
Reply from 64.233.169.104: bytes=32 time=286ms TTL=244
Reply from 64.233.169.104: bytes=32 time=285ms TTL=244
Reply from 64.233.169.104: bytes=32 time=305ms TTL=244
Reply from 64.233.169.104: bytes=32 time=289ms TTL=244
Reply from 64.233.169.104: bytes=32 time=283ms TTL=244
Reply from 64.233.169.104: bytes=32 time=288ms TTL=244
Reply from 64.233.169.104: bytes=32 time=283ms TTL=244
Reply from 64.233.169.104: bytes=32 time=288ms TTL=244
Reply from 64.233.169.104: bytes=32 time=290ms TTL=244
Reply from 64.233.169.104: bytes=32 time=283ms TTL=244
Reply from 64.233.169.104: bytes=32 time=289ms TTL=244
Reply from 64.233.169.104: bytes=32 time=281ms TTL=244
Reply from 64.233.169.104: bytes=32 time=287ms TTL=244
Reply from 64.233.169.104: bytes=32 time=282ms TTL=244
Reply from 64.233.169.104: bytes=32 time=283ms TTL=244
Reply from 64.233.169.104: bytes=32 time=288ms TTL=244
Reply from 64.233.169.104: bytes=32 time=283ms TTL=244
Reply from 64.233.169.104: bytes=32 time=281ms TTL=244
Reply from 64.233.169.104: bytes=32 time=287ms TTL=244
Reply from 64.233.169.104: bytes=32 time=280ms TTL=244
Reply from 64.233.169.104: bytes=32 time=287ms TTL=244
Reply from 64.233.169.104: bytes=32 time=286ms TTL=244
Reply from 64.233.169.104: bytes=32 time=289ms TTL=244
Reply from 64.233.169.104: bytes=32 time=281ms TTL=244
Reply from 64.233.169.104: bytes=32 time=280ms TTL=244
Reply from 64.233.169.104: bytes=32 time=284ms TTL=244
Reply from 64.233.169.104: bytes=32 time=286ms TTL=244
Reply from 64.233.169.104: bytes=32 time=278ms TTL=244
Reply from 64.233.169.104: bytes=32 time=283ms TTL=244
Reply from 64.233.169.104: bytes=32 time=292ms TTL=244
Reply from 64.233.169.104: bytes=32 time=293ms TTL=244
Reply from 64.233.169.104: bytes=32 time=285ms TTL=244
Reply from 64.233.169.104: bytes=32 time=284ms TTL=244
Reply from 64.233.169.104: bytes=32 time=289ms TTL=244
Reply from 64.233.169.104: bytes=32 time=281ms TTL=244
Reply from 64.233.169.104: bytes=32 time=63ms TTL=244

Ping statistics for 64.233.169.104:
Packets: Sent = 100, Received = 100, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 31ms, Maximum = 305ms, Average = 156ms

And I will look into that post also.


To: tos226
To my knowledge, I believe I'm still using Windows Firewall provided by Vista. Of course I'll be looking into that post as well.

To: tahitianflower
I've just made this computer, so I don't know if my computer would be the problem. But I'll look into it.

#6 tahitianflower

tahitianflower

  • Members
  • 5 posts
  • OFFLINE
  •  
  • Gender:Female
  • Location:In the 5th Dimention
  • Local time:06:26 AM

Posted 13 February 2009 - 03:27 PM

Good luck in the diagnosis :thumbsup:

#7 DaffyKantReed

DaffyKantReed

  • Members
  • 190 posts
  • OFFLINE
  •  
  • Location:Vancouver, BC
  • Local time:04:26 AM

Posted 14 February 2009 - 01:31 PM

To: DaffyKentReed
My results are:
Ping statistics for 64.233.169.104:
Packets: Sent = 100, Received = 99, Lost = 1 (1% loss),
Approximate round trip times in milli-seconds:
Minimum = 31ms, Maximum = 327ms, Average = 253ms



Ping statistics for 64.233.169.104:
Packets: Sent = 100, Received = 100, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 31ms, Maximum = 305ms, Average = 156ms



Packet loss is not a problem, but ping times are getting a bit high.

Do you have Verizon FiOS at home?

Is the wireless router secured as to not allow neighbours access?

#8 ATARi

ATARi
  • Topic Starter

  • Members
  • 29 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:New York
  • Local time:08:26 AM

Posted 14 February 2009 - 01:36 PM

I currently just use the Verizon Online DSL (High Speed Internet), advertised at 3MB download.

The wireless router is enabled with a WEP key.

#9 DaffyKantReed

DaffyKantReed

  • Members
  • 190 posts
  • OFFLINE
  •  
  • Location:Vancouver, BC
  • Local time:04:26 AM

Posted 14 February 2009 - 04:01 PM

I currently just use the Verizon Online DSL (High Speed Internet), advertised at 3MB download.

The wireless router is enabled with a WEP key.



Disable the wireless entirely and see if doing so helps matters. It is entirely possible that others are using your connection even with WEP enabled.

#10 ATARi

ATARi
  • Topic Starter

  • Members
  • 29 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:New York
  • Local time:08:26 AM

Posted 15 February 2009 - 11:51 AM

I'll try that out, thanks for the help. From my uncle's point of view (He works for Verizon), he said to try out some new modem/router also. So I guess I'll try out the wireless off first also.

#11 tos226

tos226

    BleepIN--BleepOUT


  • Members
  • 1,568 posts
  • OFFLINE
  •  
  • Gender:Female
  • Location:LocalHost
  • Local time:08:26 AM

Posted 15 February 2009 - 03:50 PM

DSL runs over copper wires.
Often things get slow or variable when the line is in a bit of trouble, such as water in the switches out there on the street.
Even if your phone is crystal clear, DSL might suffer.
I'd encourage you to try to get Verizon repair over to look. They do not need to be in your house, but they can diagnose line problems, albeit, reluctantly.

#12 DaffyKantReed

DaffyKantReed

  • Members
  • 190 posts
  • OFFLINE
  •  
  • Location:Vancouver, BC
  • Local time:04:26 AM

Posted 16 February 2009 - 08:16 AM

I'll try that out, thanks for the help. From my uncle's point of view (He works for Verizon), he said to try out some new modem/router also. So I guess I'll try out the wireless off first also.




Good stuff. My next piece of advice would have been to swap the modem/gateway device as well as replacing microfilters within your house.

#13 ATARi

ATARi
  • Topic Starter

  • Members
  • 29 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:New York
  • Local time:08:26 AM

Posted 16 February 2009 - 12:46 PM

Well currently after wireless off, I still get disconnects but not as often. Verizon did come down to check the wirings and everything went fine. Though since I had the Versalink 327W for a couple of years they advised me to switch, thus I did get a free modem switch; coming in next week. Thankfully they said it would not be a Westell. I appreciate all the help and would report after new modem is used.

#14 ATARi

ATARi
  • Topic Starter

  • Members
  • 29 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:New York
  • Local time:08:26 AM

Posted 03 March 2009 - 07:30 PM

Just switched to the ActionTec modem and currently not experiencing any more random disconnects.




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users