how-to block ads
|
|
Uniqs:
14802 |
Share Topic
 |
 |
|
|
|
| reply to Mystiky4
Re: Actiontec MI424WR Router Revision I - bug/problem ?! Wow! The problem is suddenly back. Same exact problems (and symptoms) as described in the initial message of this thread. Some pages load fast, while others don't load at all. Hitting refresh sometimes work, and sometimes doesn't.
The interesting thing is that since I am using OpenDNS's DNS address, when everything works, I would get the OpenDNS error for any bad webpage. well, now when the page doesn't load, I get the ole "Internet Explorer cannot display page" error.
Now, I have NOT rebooted the Actiontec this time around. Will wait to see in the morning to see if it by any chance the situation will "resolve" itself.
I looked at the Actiontec LOG FILE and found nothing strange.
So I had one week of NO problems whats so ever and now this. Uggh!
It will be interesting what happens in the AM. | |
1 edit | The problem did not fix itself overnight. Also, ran a parallel program to see if there were any disconnects, and there were not any.
But the loading of pages issues remained, so I have Verizon ship me a replacement.
Hopefully, it will fixed the problem.
EDIT: Just did manual OFF on the Actiontec and back ON and everything works like a charm without any reboots of the PC and/or WNDR4500. | |
| Looks like an BETA update was just posted on Netgear website for the WNDR4500:
»support.netgear.com/app/answers/···id/19894
Descirption is:
Bug Fixes & Enhancements:
•[Fixed]: Guest network can’t access internet when client access main wifi network first.
•[Fixed]: can’t find DNS server.
•[Fixed]: when using fix ip, DHCP will send NAK and connection will drop and re-connect.
•[Enhancement]: improve the read/write speed for ReadyShare NTFS file system.
Wondering if this has anything to do with resolving my issue.
Going to wait to get my Actiontec swapped, before playing with this BETA firmware. | |
 MrKal_El
join:2003-01-19
Franklin Square, NY | reply to Mystiky4
said by Mystiky4:The problem did not fix itself overnight. Also, ran a parallel program to see if there were any disconnects, and there were not any.
But the loading of pages issues remained, so I have Verizon ship me a replacement.
Hopefully, it will fixed the problem.
EDIT: Just did manual OFF on the Actiontec and back ON and everything works like a charm without any reboots of the PC and/or WNDR4500.
Sorry if I missed it earlier in the thread....but have you tried connecting a laptop directly to the ONT? (Also trying another ethernet cord?)
--
Twitter: MrKal_El | |
| Hi MrKal,
No. My laptop is very old while my hardwired PC never had any problems like this until 3 weeks ago, when I went the FIOS TV way. Remember, I had Intternet/Phone only via FIOS before.
As far as using a different cord, I am pretty sure that should not be the case. Remember, I don't loose any connections when the issue starts. Just webpages get or don't get loaded. If it was an Windows / Internet Explorer issue, those should had been auto-fixed when the PC was cold-rebooted. But it just doesn't.
I just hope I have a flaky Rev. I and that it will be solved with a replaced one, which should be here today or on Monday. | |
| The "replacement" router that was sent to me just arrived. They sent me a Rev F. So the technician is coming out on Monday with an a Rev. I.
What a waste of money (UPS overnight) and of everyone's time...
Will keep you posted. | |
| While I am waiting for the new "Rev I" router from Verizon (sometime on Monday), I just wanted to report that I had the same issue happen again with the current one (4th occurance). And again, all I had to to do is turn off the Actiontec for 2 seconds, turn it back on and everything works like a charm!
Again, no reboot required on the PC, Netgear WNDR4500 router or even closing any IE windows thsat were having an problem loading pages.
Will keep you posted on any (I hope...) progress once the replacement is online. | |
1 edit | Update: Got my replacement Rev I. installed yesterday evening. So far so good, but we have to wait for up to a week to make sure it has made any difference.
For the record: I swapped the cables from my old Actiontec into the new one, called Verizon tech support, they released the DHCP, then I turned on the new Actiontec. Went into the setup of the Actiontec, made the same changes (killed WIFI, set the IP range, made one IP static) to what they were in my old one and then turned off the PC, WNDR4500, then the Actiontect. Waited 20 seconds and then started the Actiontec, then the WNDR4500 and finally the PC. | |
| reply to Mystiky4
Well, my replacement Rev I lasted for the same 48 hours or so and then the same exact thing happened.
I have decided to flash my WNDR4500 with the BETA firmware as the next step of trying to solve my issue. It is : Version 1.0.0.103 - BETA
In the mentime, here is a copy of my Actiontec LOG file from the moment the replacement Rev I. was installed to the moment I had to turn it off/on manually to fix thing (at 9:44:05 on Feb 2). I don't see anything wrong anywhere.
I have redacted my IP address for privacy.
Dec 14 19:00:29 2007 System Log Failed GUI Authentication Failed Login for GUI access
Dec 14 19:00:03 2007 System Log WAN ETH WAN Ethernet Link Up
Dec 14 19:00:06 2007 System Log WAN DHCP DHCP WAN connection IP:108.41.xxx.xxx,DNS:68.237.161.12 71.250.0.12 ,GTW:108.41.xxx.1,Subnet:255.255.255.0 (WAN Ethernet)
Jan 30 21:12:33 2012 System Log LAN Coax LAN Coax Link Up
Jan 30 21:13:18 2012 System Log LAN Coax LAN Coax Link Rate
Jan 30 21:13:43 2012 System Log LAN DHCP DHCP LAN Connection IP:192.168.1.26, DNS:192.168.1.1, GTW:192.168.1.1,Subnet:255.255.255.0 (Ethernet)
Jan 30 21:14:09 2012 System Log LAN DHCP DHCP LAN Connection IP:192.168.1.21, DNS:192.168.1.1, GTW:192.168.1.1,Subnet:255.255.255.0 (Ethernet)
Jan 30 21:14:35 2012 System Log LAN DHCP DHCP LAN Connection IP:192.168.1.20, DNS:192.168.1.1, GTW:192.168.1.1,Subnet:255.255.255.0 (Ethernet)
Jan 30 21:17:33 2012 System Log LAN Coax LAN Coax Link Rate
Jan 30 21:24:59 2012 System Log LAN DHCP DHCP LAN Connection IP:192.168.1.21, DNS:192.168.1.1, GTW:192.168.1.1,Subnet:255.255.255.0 (Ethernet)
Jan 30 22:12:32 2012 System Log WAN DHCP DHCP WAN connection IP:108.41.xxx.xxx,DNS:68.237.161.12 71.250.0.12 ,GTW:108.41.xxx.1,Subnet:255.255.255.0 (WAN Ethernet)
Jan 30 22:26:01 2012 System Log LAN DHCP DHCP LAN Connection IP:192.168.1.21, DNS:192.168.1.1, GTW:192.168.1.1,Subnet:255.255.255.0 (Ethernet)
Jan 30 23:12:33 2012 System Log WAN DHCP DHCP WAN connection IP:108.41.xxx.xxx,DNS:68.237.161.12 71.250.0.12 ,GTW:108.41.xxx.1,Subnet:255.255.255.0 (WAN Ethernet)
Jan 31 00:03:15 2012 System Log LAN DHCP DHCP LAN Connection IP:192.168.1.22, DNS:192.168.1.1, GTW:192.168.1.1,Subnet:255.255.255.0 (Ethernet)
Jan 31 00:12:33 2012 System Log WAN DHCP DHCP WAN connection IP:108.41.xxx.xxx,DNS:68.237.161.12 71.250.0.12 ,GTW:108.41.xxx.1,Subnet:255.255.255.0 (WAN Ethernet)
Jan 31 04:08:50 2012 System Log LAN DHCP DHCP LAN Connection IP:192.168.1.100, DNS:192.168.1.1, GTW:192.168.1.1,Subnet:255.255.255.0 (Ethernet)
Jan 31 04:12:34 2012 System Log WAN DHCP DHCP WAN connection IP:108.41.xxx.xxx,DNS:68.237.161.12 71.250.0.12 ,GTW:108.41.xxx.1,Subnet:255.255.255.0 (WAN Ethernet)
Jan 31 04:15:49 2012 System Log LAN DHCP DHCP LAN Connection IP:192.168.1.101, DNS:192.168.1.1, GTW:192.168.1.1,Subnet:255.255.255.0 (Ethernet)
Jan 31 05:12:34 2012 System Log WAN DHCP DHCP WAN connection IP:108.41.xxx.xxx,DNS:68.237.161.12 71.250.0.12 ,GTW:108.41.xxx.1,Subnet:255.255.255.0 (WAN Ethernet)
Jan 31 05:27:57 2012 System Log LAN DHCP DHCP LAN Connection IP:192.168.1.100, DNS:192.168.1.1, GTW:192.168.1.1,Subnet:255.255.255.0 (Ethernet)
Jan 31 06:12:34 2012 System Log WAN DHCP DHCP WAN connection IP:108.41.xxx.xxx,DNS:68.237.161.12 71.250.0.12 ,GTW:108.41.xxx.1,Subnet:255.255.255.0 (WAN Ethernet)
Jan 31 09:13:54 2012 System Log LAN DHCP DHCP LAN Connection IP:192.168.1.26, DNS:192.168.1.1, GTW:192.168.1.1,Subnet:255.255.255.0 (Ethernet)
Jan 31 09:30:30 2012 System Log LAN DHCP DHCP LAN Connection IP:192.168.1.20, DNS:192.168.1.1, GTW:192.168.1.1,Subnet:255.255.255.0 (Ethernet)
Jan 31 10:12:35 2012 System Log WAN DHCP DHCP WAN connection IP:108.41.xxx.xxx,DNS:68.237.161.12 71.250.0.12 ,GTW:108.41.xxx.1,Subnet:255.255.255.0 (WAN Ethernet)
Jan 31 10:26:03 2012 System Log LAN DHCP DHCP LAN Connection IP:192.168.1.21, DNS:192.168.1.1, GTW:192.168.1.1,Subnet:255.255.255.0 (Ethernet)
Jan 31 11:12:35 2012 System Log WAN DHCP DHCP WAN connection IP:108.41.xxx.xxx,DNS:68.237.161.12 71.250.0.12 ,GTW:108.41.xxx.1,Subnet:255.255.255.0 (WAN Ethernet)
Jan 31 12:03:17 2012 System Log LAN DHCP DHCP LAN Connection IP:192.168.1.22, DNS:192.168.1.1, GTW:192.168.1.1,Subnet:255.255.255.0 (Ethernet)
Jan 31 12:12:36 2012 System Log WAN DHCP DHCP WAN connection IP:108.41.xxx.xxx,DNS:68.237.161.12 71.250.0.12 ,GTW:108.41.xxx.1,Subnet:255.255.255.0 (WAN Ethernet)
Jan 31 13:22:47 2012 System Log LAN DHCP DHCP LAN Connection IP:192.168.1.23, DNS:192.168.1.1, GTW:192.168.1.1,Subnet:255.255.255.0 (Ethernet)
Jan 31 14:12:36 2012 System Log WAN DHCP DHCP WAN connection IP:108.41.xxx.xxx,DNS:68.237.161.12 71.250.0.12 ,GTW:108.41.xxx.1,Subnet:255.255.255.0 (WAN Ethernet)
Jan 31 16:15:49 2012 System Log LAN DHCP DHCP LAN Connection IP:192.168.1.101, DNS:192.168.1.1, GTW:192.168.1.1,Subnet:255.255.255.0 (Ethernet)
Jan 31 17:12:37 2012 System Log WAN DHCP DHCP WAN connection IP:108.41.xxx.xxx,DNS:68.237.161.12 71.250.0.12 ,GTW:108.41.xxx.1,Subnet:255.255.255.0 (WAN Ethernet)
Jan 31 17:27:58 2012 System Log LAN DHCP DHCP LAN Connection IP:192.168.1.100, DNS:192.168.1.1, GTW:192.168.1.1,Subnet:255.255.255.0 (Ethernet)
Jan 31 18:03:28 2012 System Log LAN DHCP DHCP LAN Connection IP:192.168.1.23, DNS:192.168.1.1, GTW:192.168.1.1,Subnet:255.255.255.0 (Ethernet)
Jan 31 18:12:37 2012 System Log WAN DHCP DHCP WAN connection IP:108.41.xxx.xxx,DNS:68.237.161.12 71.250.0.12 ,GTW:108.41.xxx.1,Subnet:255.255.255.0 (WAN Ethernet)
Jan 31 20:05:33 2012 System Log CWMP Periodic Inform initial 401 challenge
Jan 31 20:05:34 2012 System Log CWMP Periodic Inform challenge response with 200 OK from server
Jan 31 20:05:34 2012 System Log CWMP Periodic Inform 204 No Content
Jan 31 20:12:37 2012 System Log WAN DHCP DHCP WAN connection IP:108.41.xxx.xxx,DNS:68.237.161.12 71.250.0.12 ,GTW:108.41.xxx.1,Subnet:255.255.255.0 (WAN Ethernet)
Jan 31 21:12:38 2012 System Log WAN DHCP DHCP WAN connection IP:108.41.xxx.xxx,DNS:68.237.161.12 71.250.0.12 ,GTW:108.41.xxx.1,Subnet:255.255.255.0 (WAN Ethernet)
Jan 31 21:14:04 2012 System Log LAN DHCP DHCP LAN Connection IP:192.168.1.26, DNS:192.168.1.1, GTW:192.168.1.1,Subnet:255.255.255.0 (Ethernet)
Jan 31 21:46:20 2012 System Log LAN DHCP DHCP LAN Connection IP:192.168.1.20, DNS:192.168.1.1, GTW:192.168.1.1,Subnet:255.255.255.0 (Ethernet)
Jan 31 22:12:37 2012 System Log WAN DHCP DHCP WAN connection IP:108.41.xxx.xxx,DNS:68.237.161.12 71.250.0.12 ,GTW:108.41.xxx.1,Subnet:255.255.255.0 (WAN Ethernet)
Jan 31 22:26:04 2012 System Log LAN DHCP DHCP LAN Connection IP:192.168.1.21, DNS:192.168.1.1, GTW:192.168.1.1,Subnet:255.255.255.0 (Ethernet)
Jan 31 23:12:38 2012 System Log WAN DHCP DHCP WAN connection IP:108.41.xxx.xxx,DNS:68.237.161.12 71.250.0.12 ,GTW:108.41.xxx.1,Subnet:255.255.255.0 (WAN Ethernet)
Jan 31 23:37:50 2012 System Log LAN DHCP DHCP LAN Connection IP:192.168.1.22, DNS:192.168.1.1, GTW:192.168.1.1,Subnet:255.255.255.0 (Ethernet)
Feb 1 00:12:38 2012 System Log WAN DHCP DHCP WAN connection IP:108.41.xxx.xxx,DNS:68.237.161.12 71.250.0.12 ,GTW:108.41.xxx.1,Subnet:255.255.255.0 (WAN Ethernet)
Feb 1 04:15:49 2012 System Log LAN DHCP DHCP LAN Connection IP:192.168.1.101, DNS:192.168.1.1, GTW:192.168.1.1,Subnet:255.255.255.0 (Ethernet)
Feb 1 05:12:39 2012 System Log WAN DHCP DHCP WAN connection IP:108.41.xxx.xxx,DNS:68.237.161.12 71.250.0.12 ,GTW:108.41.xxx.1,Subnet:255.255.255.0 (WAN Ethernet)
Feb 1 05:27:58 2012 System Log LAN DHCP DHCP LAN Connection IP:192.168.1.100, DNS:192.168.1.1, GTW:192.168.1.1,Subnet:255.255.255.0 (Ethernet)
Feb 1 06:12:39 2012 System Log WAN DHCP DHCP WAN connection IP:108.41.xxx.xxx,DNS:68.237.161.12 71.250.0.12 ,GTW:108.41.xxx.1,Subnet:255.255.255.0 (WAN Ethernet)
Feb 1 09:14:13 2012 System Log LAN DHCP DHCP LAN Connection IP:192.168.1.26, DNS:192.168.1.1, GTW:192.168.1.1,Subnet:255.255.255.0 (Ethernet)
Feb 1 10:00:15 2012 System Log LAN DHCP DHCP LAN Connection IP:192.168.1.20, DNS:192.168.1.1, GTW:192.168.1.1,Subnet:255.255.255.0 (Ethernet)
Feb 1 10:12:40 2012 System Log WAN DHCP DHCP WAN connection IP:108.41.xxx.xxx,DNS:68.237.161.12 71.250.0.12 ,GTW:108.41.xxx.1,Subnet:255.255.255.0 (WAN Ethernet)
Feb 1 10:26:05 2012 System Log LAN DHCP DHCP LAN Connection IP:192.168.1.21, DNS:192.168.1.1, GTW:192.168.1.1,Subnet:255.255.255.0 (Ethernet)
Feb 1 11:12:40 2012 System Log WAN DHCP DHCP WAN connection IP:108.41.xxx.xxx,DNS:68.237.161.12 71.250.0.12 ,GTW:108.41.xxx.1,Subnet:255.255.255.0 (WAN Ethernet)
Feb 1 14:11:16 2012 System Log LAN DHCP DHCP LAN Connection IP:192.168.1.20, DNS:192.168.1.1, GTW:192.168.1.1,Subnet:255.255.255.0 (Ethernet)
Feb 1 14:12:41 2012 System Log WAN DHCP DHCP WAN connection IP:108.41.xxx.xxx,DNS:68.237.161.12 71.250.0.12 ,GTW:108.41.xxx.1,Subnet:255.255.255.0 (WAN Ethernet)
Feb 1 16:15:49 2012 System Log LAN DHCP DHCP LAN Connection IP:192.168.1.101, DNS:192.168.1.1, GTW:192.168.1.1,Subnet:255.255.255.0 (Ethernet)
Feb 1 17:12:42 2012 System Log WAN DHCP DHCP WAN connection IP:108.41.xxx.xxx,DNS:68.237.161.12 71.250.0.12 ,GTW:108.41.xxx.1,Subnet:255.255.255.0 (WAN Ethernet)
Feb 1 17:27:58 2012 System Log LAN DHCP DHCP LAN Connection IP:192.168.1.100, DNS:192.168.1.1, GTW:192.168.1.1,Subnet:255.255.255.0 (Ethernet)
Feb 1 18:12:42 2012 System Log WAN DHCP DHCP WAN connection IP:108.41.xxx.xxx,DNS:68.237.161.12 71.250.0.12 ,GTW:108.41.xxx.1,Subnet:255.255.255.0 (WAN Ethernet)
Feb 1 20:05:33 2012 System Log CWMP Periodic Inform initial 401 challenge
Feb 1 20:05:34 2012 System Log CWMP Periodic Inform challenge response with 200 OK from server
Feb 1 20:05:34 2012 System Log CWMP Periodic Inform 204 No Content
Feb 1 20:12:42 2012 System Log WAN DHCP DHCP WAN connection IP:108.41.xxx.xxx,DNS:68.237.161.12 71.250.0.12 ,GTW:108.41.xxx.1,Subnet:255.255.255.0 (WAN Ethernet)
Feb 1 20:52:51 2012 System Log LAN DHCP DHCP LAN Connection IP:192.168.1.20, DNS:192.168.1.1, GTW:192.168.1.1,Subnet:255.255.255.0 (Ethernet)
Dec 14 19:00:05 2007 System Log WAN ETH WAN Ethernet Link Up
Dec 14 19:00:06 2007 System Log WAN DHCP DHCP WAN connection IP:108.41.xxx.xxx,DNS:68.237.161.12 71.250.0.12 ,GTW:108.41.xxx.1,Subnet:255.255.255.0 (WAN Ethernet)
Feb 2 09:44:05 2012 System Log LAN Coax LAN Coax Link Up
Feb 2 09:44:50 2012 System Log LAN Coax LAN Coax Link Rate
Feb 2 09:44:53 2012 System Log LAN DHCP DHCP LAN Connection IP:192.168.1.26, DNS:192.168.1.1, GTW:192.168.1.1,Subnet:255.255.255.0 (Ethernet)
Feb 2 09:45:15 2012 System Log LAN DHCP DHCP LAN Connection IP:192.168.1.21, DNS:192.168.1.1, GTW:192.168.1.1,Subnet:255.255.255.0 (Ethernet)
Feb 2 09:46:03 2012 System Log LAN DHCP DHCP LAN Connection IP:192.168.1.20, DNS:192.168.1.1, GTW:192.168.1.1,Subnet:255.255.255.0 (Ethernet)
Feb 2 09:49:05 2012 System Log LAN Coax LAN Coax Link Rate | |
| reply to Mystiky4
One thing I can add is this: At NO TIME does my actual internet connection go down. I am running mIRC, and that program ping/pongs almost every second. If there is any drop in the connection, it is reported to me.
And guess, what, mIRC keeps (and some Java applets) keep working with no problems and without stopping while the pages stop loading. | |
2 edits | Looks like you've tried most of the "obvious" stuff, including swapping out the Rev I.
Sounds like it's only happening from ONE, hardwired PC? (I didn't read the thread in detail, so if I missed something, apologies.) Silly question: Have you cleaned out the browser cache on that PC? Grasping at straws, but there's a slight chance it could be related.
Hard-code the OpenDNS server addresses on the Win 7 box and see if the problem persists. In this config, the client will completely bypass the Actiontec for DNS resolution.
As I recall from our previous conversation, the 4500 is in AP mode, so it's not doing any DNS resolution for your clients at all. I doubt the firmware update will make any difference.
My next step would be to make the 4500 primary, and turn the I into a MoCA bridge for the STB's. Let the 4500 handle DNS resolution and see what happens.
Beyond all that obvious stuff, you'd need to sniff packets to see what's actually going on.
EDIT -- One more thing to try. When you see this happen, open a command.com window on the PC and run nslookup. Enter the name of the site you're getting slow response on, e.g., "www.website.com." (and add the last period). If you get a quick response with the IP address(es), DNS resolution is most likely not the problem. | |
| Claibourne, thanks for the great reply, as always!
I have one other step to take, which is to swap my WNDR4500 for another one, as I am on day 25 of my staples buy and I get 30 days to return it.
Another thing that I relazied I have not mentioned is that when my web pages stop loading normally, my iPhone (in wifi only mode) also stops working. Meaning, the wireless stops working also. This means that the wireless section of the WNDR4500 is also being effected.
I shall keep my vigil to see what the next 48 hours bring. | |
| So it's happening from both wired clients on the AT, and wireless clients on the 4500, at the same time; they all work, or they all don't?
So yeah, again, repeating the obvious....  Without inspecting the traffic, hard to say. DNS, routing problems, router hardware, ONT hardware, all could potentially be the issue. If it keeps happening even after replacing the router, I'd suggest re-opening the ticket with VZ. You may have to talk to several people, and go through the hardware-replacement cycle a few times, but if you're running in a supported config, with the VZ router as primary, you should eventually be able to get a resolution. I had a problem once with slow upload speeds, they replaced the router a couple of times, then someone looked at whatever logs can be looked at on my ONT, said there was an obvious problem with it (what, I don't know), they sent someone out to replace it, and the problem was solved. Polite persistence usually pays off. | |
| >
Yes, exactly. Either all work or none. It's been 24 hours and all is honky-dore but usually the fireworks start at 48 hours.
By the way, my ONT is the Motorola ONT1000GJ2, which is inside in my basement. On the box its says FG Rev: 16.
Cheers!
Michael | |
| I actually decided to do a "Reset to Default" on the WNDR4500, as I realized that although I updated the firmware, it is probably better to have done this reset. I re-built everything again from scratch, meaning:
1) Reset to factory defaults
2) Connect 4500 WAN to Actiontec LAN
4) The 4500 should sense its subnet is the same as the AT, and change to 10.0.0.x
5) Go through the initial 4500 setup. Tell it to configure the internet connection automatically. It should say it did that successfully, then give you an option to "go to the internet" or somesuch.
6) Click on that option, you should then get another Netgear page. For some reason I can't explain, this seems to be important to the whole process.
7) Disconnect the 4500 WAN from the Actiontec LAN.
8) Change the 4500 to "AP Mode." Leave the defaults in place, i.e., don't specify an IP, or netmask, or default route, and don't change the DNS settings.
9) Apply the change.
10) Wait about 30 seconds, turn off the 4500.
11) Connect a 4500 LAN port to an Actiontec LAN port.
12) Turn the 4500 back on.
I then manually (not restored from a saved .CFG file) re-entered all of the information.
Now, the wait begins. Although I turned off the WNDR4500 for this procedure, I never touched the Actiontect, which has now been running for 28 hours. | |
| reply to Mystiky4
Right on schedule, 52 hours later, the problem re-appeared again.
Tommorow (Sunday), I shall replace my WNDR4500 with another WNDR4500.
Just dissapointing... | |
 rtcyFACTS only pleasePremium
join:1999-10-16
Norwalk, CA | reply to Mystiky4
said by Mystiky4:While I am waiting for the new "Rev I" router from Verizon (sometime on Monday), I just wanted to report that I had the same issue happen again with the current one (4th occurance). And again, all I had to to do is turn off the Actiontec for 2 seconds, turn it back on and everything works like a charm!
Again, no reboot required on the PC, Netgear WNDR4500 router or even closing any IE windows thsat were having an problem loading pages.
Will keep you posted on any (I hope...) progress once the replacement is online.
maybe I missed it at the top, are the ethernet wires from the house connected to the Actiontec ? or are they connected to the 4500?. I know you were asked to do without the 4500, but at the very least you should have all hardwires going straight to the Actiontec and see if the machines that are hardwired also freeze up.
it's starting to sound like this new router may have issues. it's a shame Verizon has never added a feature to reboot every 24 hours. it would solve so much | | |
|
| My connection from the ONT is both Ethernet and Coax.
The Ethernet one goes from the ONT to the WAN port of the Actiontec. The Ethernet from the WNDR4500 (from it's LAN port)is going into the LAN port of the Actiontec.
The Coax from the ONT goes into a 4-splitter, of which one part goes into the Coax of the Actiontec. The other 2 ends go into my two STB boxes, and the 4th end is capped.
Now, as far as the 24-hour reboot, I am not sure it's a good idea as some of us keep connections which should not go down (like applets for stock traders, mIRC, etc.). If there is a reboot, you would then need to restart all those applications and that would create a hassle. | |
| reply to Mystiky4
Image-1 | 
Image-2 | 
Image-3 | 
Image-4 |
I flashed the WNDR4500 to the latest firmware and then redid the whole routine to turn the WNDR4500 into an "AP" (see above 10-step suggested a few msgs back). My previous WNDR4500 was assigned a Static IP of 192.168.1.26 by the Actiontect. Of course I forgot "clear it" before installing this replacement one, so my new WNDR4500 got the 192.168.1.24 assigned to it. I then went into the Actiontec and removed the 192.168.1.26 completely from the IP Address Distribution.
I then went to change the 192.168.1.24 to be the "Static". I then rebooted both the Actiontec and the WNDR4500 (also turned off the PC) and upon the full restart I have this strange situation where (see the Image-4 attached here) Actiontec clearely shows the IP address of the WNDR4500 to be selected as "Static", but as you can see (Image2 & Image-3), it is still being displayed as "DHCP" in My Network/ Connections.
In addition, when I go to "Network" in Windows 7 SP1, it doesn't show WNDR4500 under "Network Infrastructure" as it did with the original WNDR4500 (see Image-1). I know it displayed it there together with the Actiontect before as all I had to do is double-click on it and it would take me to the login screen for the WNDR4500.
Taking the two above situation into consideration, everything else seems to be working. Of course, we must now wait at least 48 hours to see if this swap made any difference.
Does anyone have any suggestions in the meantime how to fix this "Static" issue and also the non-display of the WNDR4500 in the "Network Infastructure"?
| |
 More FiberPremium,MVM
join:2005-09-26
West Chester, PA
kudos:28 | This is a semantics issue. What you (and the Actiontec) are referring to as static is not really static. A true static IP address is set at the device and the router is not involved.
What you've done is create a "DHCP Reservation". Actiontec incorrectly refers to this as a static assignment.
With a DHCP reservation, the device (the WNDR4500) sends a DHCP request just as it normally would. The Actiontec responds with a DHCP response containing a preassigned IP address for that MAC address.
--
There are 10 kinds of people in the world; those who understand binary and those who don't.
| |
|
