Reply
bpowar
Posts: 1
Registered: ‎02-15-2012

Re: E3000 Connection Problems

Hi, Can anyone please help me out with intermittent connection problem on E3200.

The internet drops after a minute or two for 10 to 15 seconds.

I have PPPoE internet with a CAT5  directly into the router from my ISP.

i have latest firmware (FW_E3200_1.0.02.009_20110901_code,0) on the router.

 

Below is the ping response to DNS of my ISP.

 

Reply from 123.108.225.6: bytes=32 time=5ms TTL=59
Reply from 123.108.225.6: bytes=32 time=2ms TTL=59
Reply from 123.108.225.6: bytes=32 time=4ms TTL=59
Reply from 123.108.225.6: bytes=32 time=2ms TTL=59
Reply from 123.108.225.6: bytes=32 time=2ms TTL=59
Reply from 123.108.225.6: bytes=32 time=3ms TTL=59
Reply from 123.108.225.6: bytes=32 time=2ms TTL=59
Reply from 123.108.225.6: bytes=32 time=2ms TTL=59
Reply from 123.108.225.6: bytes=32 time=3ms TTL=59
Reply from 123.108.225.6: bytes=32 time=3ms TTL=59
Reply from 123.108.225.6: bytes=32 time=3ms TTL=59
Reply from 123.108.225.6: bytes=32 time=3ms TTL=59
Reply from 123.108.225.6: bytes=32 time=2ms TTL=59
Reply from 123.108.225.6: bytes=32 time=2ms TTL=59
Reply from 123.108.225.6: bytes=32 time=2ms TTL=59
Reply from 123.108.225.6: bytes=32 time=3ms TTL=59
Reply from 123.108.225.6: bytes=32 time=3ms TTL=59
Reply from 123.108.225.6: bytes=32 time=2ms TTL=59
Reply from 123.108.225.6: bytes=32 time=2ms TTL=59
Reply from 123.108.225.6: bytes=32 time=3ms TTL=59
Reply from 123.108.225.6: bytes=32 time=2ms TTL=59
Reply from 123.108.225.6: bytes=32 time=3ms TTL=59
Reply from 123.108.225.6: bytes=32 time=2ms TTL=59
Reply from 123.108.225.6: bytes=32 time=2ms TTL=59
Reply from 123.108.225.6: bytes=32 time=3ms TTL=59
Reply from 123.108.225.6: bytes=32 time=2ms TTL=59
Reply from 123.108.225.6: bytes=32 time=2ms TTL=59
Reply from 123.108.225.6: bytes=32 time=2ms TTL=59
Reply from 123.108.225.6: bytes=32 time=2ms TTL=59
Reply from 123.108.225.6: bytes=32 time=2ms TTL=59
Reply from 123.108.225.6: bytes=32 time=2ms TTL=59
Reply from 123.108.225.6: bytes=32 time=3ms TTL=59
Reply from 123.108.225.6: bytes=32 time=3ms TTL=59
Reply from 123.108.225.6: bytes=32 time=3ms TTL=59
Reply from 123.108.225.6: bytes=32 time=2ms TTL=59
Reply from 123.108.225.6: bytes=32 time=3ms TTL=59
Reply from 123.108.225.6: bytes=32 time=3ms TTL=59
Reply from 123.108.225.6: bytes=32 time=5ms TTL=59
Reply from 123.108.225.6: bytes=32 time=2ms TTL=59
Reply from 123.108.225.6: bytes=32 time=2ms TTL=59
Reply from 123.108.225.6: bytes=32 time=2ms TTL=59
Reply from 123.108.225.6: bytes=32 time=2ms TTL=59
Reply from 123.108.225.6: bytes=32 time=2ms TTL=59
Reply from 123.108.225.6: bytes=32 time=2ms TTL=59
Reply from 123.108.225.6: bytes=32 time=1ms TTL=59
Reply from 123.108.225.6: bytes=32 time=6ms TTL=59
Reply from 123.108.225.6: bytes=32 time=2ms TTL=59
Reply from 123.108.225.6: bytes=32 time=4ms TTL=59
Reply from 123.108.225.6: bytes=32 time=6ms TTL=59
Reply from 123.108.225.6: bytes=32 time=3ms TTL=59
Reply from 123.108.225.6: bytes=32 time=3ms TTL=59
Reply from 123.108.225.6: bytes=32 time=3ms TTL=59
Reply from 123.108.225.6: bytes=32 time=3ms TTL=59
Reply from 123.108.225.6: bytes=32 time=2ms TTL=59
Reply from 123.108.225.6: bytes=32 time=2ms TTL=59
Reply from 123.108.225.6: bytes=32 time=2ms TTL=59
Reply from 123.108.225.6: bytes=32 time=4ms TTL=59
Reply from 123.108.225.6: bytes=32 time=4ms TTL=59
Reply from 123.108.225.6: bytes=32 time=3ms TTL=59
Reply from 123.108.225.6: bytes=32 time=2ms TTL=59
Reply from 123.108.225.6: bytes=32 time=2ms TTL=59
Reply from 123.108.225.6: bytes=32 time=4ms TTL=59
Reply from 123.108.225.6: bytes=32 time=2ms TTL=59
Reply from 123.108.225.6: bytes=32 time=2ms TTL=59
Reply from 123.108.225.6: bytes=32 time=3ms TTL=59
Reply from 123.108.225.6: bytes=32 time=3ms TTL=59
Reply from 123.108.225.6: bytes=32 time=4ms TTL=59
Reply from 123.108.225.6: bytes=32 time=3ms TTL=59
Reply from 123.108.225.6: bytes=32 time=4ms TTL=59
Reply from 123.108.225.6: bytes=32 time=4ms TTL=59
Reply from 123.108.225.6: bytes=32 time=3ms TTL=59
Reply from 123.108.225.6: bytes=32 time=3ms TTL=59
Reply from 123.108.225.6: bytes=32 time=5ms TTL=59
Reply from 123.108.225.6: bytes=32 time=3ms TTL=59
Reply from 123.108.225.6: bytes=32 time=3ms TTL=59
Reply from 123.108.225.6: bytes=32 time=3ms TTL=59
Reply from 123.108.225.6: bytes=32 time=3ms TTL=59
Reply from 123.108.225.6: bytes=32 time=3ms TTL=59
Reply from 123.108.225.6: bytes=32 time=6ms TTL=59
Reply from 123.108.225.6: bytes=32 time=2ms TTL=59
Reply from 123.108.225.6: bytes=32 time=3ms TTL=59
Reply from 123.108.225.6: bytes=32 time=2ms TTL=59
Reply from 123.108.225.6: bytes=32 time=2ms TTL=59
Request timed out.
Reply from 123.108.225.6: bytes=32 time=3ms TTL=59
Reply from 123.108.225.6: bytes=32 time=5ms TTL=59
Reply from 123.108.225.6: bytes=32 time=3ms TTL=59
Reply from 123.108.225.6: bytes=32 time=4ms TTL=59
Reply from 123.108.225.6: bytes=32 time=3ms TTL=59
Reply from 123.108.225.6: bytes=32 time=1ms TTL=59
Reply from 123.108.225.6: bytes=32 time=4ms TTL=59
Reply from 192.168.1.1: Destination net unreachable.
Reply from 192.168.1.1: Destination net unreachable.
Reply from 192.168.1.1: Destination net unreachable.
Reply from 192.168.1.1: Destination net unreachable.
Reply from 192.168.1.1: Destination net unreachable.
Reply from 192.168.1.1: Destination net unreachable.
Reply from 192.168.1.1: Destination net unreachable.
Reply from 192.168.1.1: Destination net unreachable.
Reply from 192.168.1.1: Destination net unreachable.
Reply from 192.168.1.1: Destination net unreachable.
Reply from 192.168.1.1: Destination net unreachable.
Reply from 192.168.1.1: Destination net unreachable.
Reply from 192.168.1.1: Destination net unreachable.
Reply from 192.168.1.1: Destination net unreachable.
Reply from 192.168.1.1: Destination net unreachable.
Reply from 192.168.1.1: Destination net unreachable.
Reply from 192.168.1.1: Destination net unreachable.
Reply from 192.168.1.1: Destination net unreachable.
Reply from 192.168.1.1: Destination net unreachable.
Reply from 192.168.1.1: Destination net unreachable.
Reply from 192.168.1.1: Destination net unreachable.
Reply from 192.168.1.1: Destination net unreachable.
Reply from 192.168.1.1: Destination net unreachable.
Reply from 192.168.1.1: Destination net unreachable.
Reply from 123.108.225.6: bytes=32 time=3ms TTL=59
Reply from 123.108.225.6: bytes=32 time=3ms TTL=59
Reply from 123.108.225.6: bytes=32 time=18ms TTL=59
Reply from 123.108.225.6: bytes=32 time=6ms TTL=59
Request timed out.
Reply from 123.108.225.6: bytes=32 time=2ms TTL=59
Reply from 123.108.225.6: bytes=32 time=2ms TTL=59
Reply from 123.108.225.6: bytes=32 time=2ms TTL=59
Reply from 123.108.225.6: bytes=32 time=3ms TTL=59
Reply from 123.108.225.6: bytes=32 time=3ms TTL=59
Reply from 123.108.225.6: bytes=32 time=2ms TTL=59
Reply from 123.108.225.6: bytes=32 time=3ms TTL=59
Reply from 123.108.225.6: bytes=32 time=2ms TTL=59
Reply from 123.108.225.6: bytes=32 time=4ms TTL=59
Reply from 123.108.225.6: bytes=32 time=3ms TTL=59
Reply from 123.108.225.6: bytes=32 time=4ms TTL=59
Reply from 123.108.225.6: bytes=32 time=3ms TTL=59
Reply from 123.108.225.6: bytes=32 time=2ms TTL=59
Reply from 123.108.225.6: bytes=32 time=5ms TTL=59
Reply from 123.108.225.6: bytes=32 time=2ms TTL=59
Reply from 123.108.225.6: bytes=32 time=3ms TTL=59
Reply from 123.108.225.6: bytes=32 time=3ms TTL=59
Reply from 123.108.225.6: bytes=32 time=4ms TTL=59
Reply from 123.108.225.6: bytes=32 time=6ms TTL=59
Reply from 123.108.225.6: bytes=32 time=4ms TTL=59
Reply from 123.108.225.6: bytes=32 time=2ms TTL=59
Reply from 123.108.225.6: bytes=32 time=2ms TTL=59
Reply from 123.108.225.6: bytes=32 time=2ms TTL=59
Reply from 123.108.225.6: bytes=32 time=4ms TTL=59
Reply from 123.108.225.6: bytes=32 time=3ms TTL=59
Reply from 123.108.225.6: bytes=32 time=2ms TTL=59
Reply from 123.108.225.6: bytes=32 time=2ms TTL=59
Reply from 123.108.225.6: bytes=32 time=2ms TTL=59
Reply from 123.108.225.6: bytes=32 time=3ms TTL=59
Reply from 123.108.225.6: bytes=32 time=3ms TTL=59
Reply from 123.108.225.6: bytes=32 time=3ms TTL=59
Reply from 123.108.225.6: bytes=32 time=5ms TTL=59
Reply from 123.108.225.6: bytes=32 time=2ms TTL=59
Reply from 123.108.225.6: bytes=32 time=3ms TTL=59
Reply from 123.108.225.6: bytes=32 time=2ms TTL=59
Reply from 123.108.225.6: bytes=32 time=3ms TTL=59
Reply from 123.108.225.6: bytes=32 time=2ms TTL=59
Reply from 123.108.225.6: bytes=32 time=2ms TTL=59
Reply from 123.108.225.6: bytes=32 time=2ms TTL=59
Reply from 123.108.225.6: bytes=32 time=2ms TTL=59
Reply from 123.108.225.6: bytes=32 time=2ms TTL=59
Reply from 123.108.225.6: bytes=32 time=2ms TTL=59
Reply from 123.108.225.6: bytes=32 time=2ms TTL=59
Reply from 123.108.225.6: bytes=32 time=2ms TTL=59
Reply from 123.108.225.6: bytes=32 time=2ms TTL=59

 

 

Thanks

 

Bhushan

357th_Sundance
Posts: 2
Registered: ‎06-26-2012

Re: E3000 Connection Problems


tarisea wrote:

I just bought a new E3000 router less than 2 weeks ago.  I spent hours with my tech guy setting up the router so that I was getting excellent internet speed and the connection between my computer and my nas was maximized.  In the process of setting up the router my laptop (Windows 7) and the basement laptop (Vista) were set up to access the router.  Both work perfectly

 

These are now the only two devices in the house that can get internet access.

 

The other devices that should connect are:

 

2 Laptops (both Vista)

1 iPhone 4

2 iPhone 3gs

1 Printer

 

I can't get them to connect.  I spent an hour with a guy at Cisco tonight who just couldn't seem to get past the idea that it was not the laptop that was the problem.  I don't understand.

 

Someone please help.

 

 



Can anyone please help me out with intermittent connection problem on E3000.

The internet drops anywhere between a few minutes a 45 minutes.

I Just got this E3000 I Have been using Teamspeak to monitor the  amount of time it would drop in an hour

I have after having this problem upgrade the firmware and still have the same problem

This route was to replace my 5 year old linksys WRT54GS V7 which really have no problem.

But I want a new router to stream video from the different computer to My new Samsung Smart TV

 

So if anyone can help. Thank you

Chip Groff
Posts: 1
Registered: ‎07-01-2012

Re: E3000 Connection Problems

This is a new computer with the hard drive added from the old computer. I can't find anthing that allows me to access the router software. The disk will not allow me to re-install the software. What do I do?

ScarletJamie
Posts: 1,534
Registered: ‎04-22-2012

Re: E3000 Connection Problems


Chip Groff wrote:

This is a new computer with the hard drive added from the old computer. I can't find anthing that allows me to access the router software. The disk will not allow me to re-install the software. What do I do?


Hi, you can reset and reconfigure the router. Just follow the steps below.

 

* Setting up a Linksys router for DSL Internet connection

 

http://www6.nohold.net/Cisco2/ukp.aspx?vw=1&docid=20ee1457387f40178cd5f41d4b585db4_3687.xml&pid=80&r...

 

 

* Setting up a Linksys router with Cable Internet service

 

http://www6.nohold.net/Cisco2/ukp.aspx?vw=1&docid=0ff4c94586a345d082828ec2161aaecf_3686.xml&pid=80&r...

 

cptnick
Posts: 1
Registered: ‎07-15-2012

Re: E3000 Connection Problems

hi, I am posting here because I am experiencing a similar problem to the above post. I have an E3200 router and I believe it is defective. I have attempted over and over to set it up but I get the same message "we could not find your router." I have tried about 10 times 10 different ways to hard reset the router, nothing changes. There seems to be no other way to make this work. I also tried connecting to the computer with the ethernet line and it still says that it can't find the router.

jaymay
Posts: 1,690
Registered: ‎04-22-2012

Re: E3000 Connection Problems

How about you try to reconfgure it manually. Just follow what ScarletJamie provided above. The links are for how to manually setup a linksys router  thru a cable or dsl internet service.

srsmith14
Posts: 1
Registered: ‎08-01-2012

Re: E3000 Connection Problems

I was having the exact problem with my E3200 router once I received a new Arris TM722G cable modem last week.  After ruling out the cable modem as the problem (calls, resets, technician visit and line tests, and running direct off the modem without issue), the Cisco chat rep provided these steps to follow which solved the issue.  We had lightning in the area the day I installed the modem, and I suspect the real issue was a power surge or brown out conidtion corrupting the router configuration.  In any case, if you have this issue, try these steps:

 

Start with step 1 and do not skip any of the instructions. You will only connect Internet/Modem when you reach step 7.

 

  1. DO NOT connect the cable modem to the Linksys router yet. (No Internet needed)
  2. Connect computer to port 4 of the router. (Only one computer must be wired, not wirelessly connected)
  3. To reset the router to its factory default, look for the press and hold the reset button on the bottom of the router for 30 seconds.
  4. Power off the router for 20 seconds and power it on after 20 seconds. Make sure that Power and 4 is lit on the router.
  5. Access the router's set-up page by going to http://192.168.1.1 in a web browser. Ignore the warnings and continue to the login screen.  Leave the username blank or empty and enter “admin” for the password and then hit “OK”.
  6. In the router's page, do the following:
    1. Under the Setup tab and the MAC Address Clone sub tab, enable it and click Clone this PC's Mac. Save.
    2. For the 5 Ghz Settings, change the Network Mode to Mixed, change the SSID from Cisco to a personalized name, leave the Channel Width and Channel to Auto.
    3. For the 2.4 Ghz settings, Network Mode is still Mixed, personalize SSID, change the Channel Width to 20 Mhz and Standard Channel to 6. Click Save.
    4. Click the Wireless Security sub tab. Change the Security Mode to WPA2 Personal. In the Passphrase field type in your password. Make sure it is not less than 8 digits. No spaces and no symbols. When done click Save settings.
    5. Power off the computer and the Linksys router. Connect the modem to the Internet or WAN port of the Linksys router and the computers to any numbered ports of the Linksys router. (No other device wired to modem when router is connected to it.)
    6. Perform a complete power cycle (shut down PC's, router and the modem for one minute. Power on modem first, then the router and lastly your PC's.

 

Almo0nd
Posts: 1
Registered: ‎08-22-2012

Re: E3000 Connection Problems

Thank you!  This solved my connection problem!

@NO_SCREENNAME@
Posts: 1
Registered: ‎10-12-2012

Re: E3000 Connection Problems

I can't get the wifi connection for our customers.And I don't remember the password.

Moderator
24JUAN80
Posts: 882
Registered: ‎04-06-2010

Re: E3000 Connection Problems

If you mean the WIFI password, just log in using  a wired computer (Router to Computer) to access its admin page. (Type 192.168.1.1 on a browsers address bar) You need to supply your routers username and password, otherwise, you will have to reset and reconfigure the router from scratch. Find the reset button and follow my signature on how to manually configure your router depending on what ISP type you have.

 

Do post back if you need more help.

------------------------------------------------------------------------------------
The Search Function is your friend.... and Google too.

How to Secure your Network
How to Upgrade Routers Firmware
Setting-Up a Router with DSL Internet Service
Setting-Up a Router with Cable Internet Service
How to Hard Reset or 30/30/30 your Router
------------------------------------------------------------------------------------