David803sc
Premium
join:2001-02-22
Charleston, SC | reply to sbccustomer
Re: DIR-655 New Firmware Version 1.10
I had to change the DST day and times manually, and than told it to sync with a time server time-b.nist.gov and it is now showing the correct time and date. |
|
stlgera
join:2004-05-02
Sweden
| I had problems with the times as well. Summertime - Wintertime. The problem was that Daylight Saving was adjusted to DST End 5th week in October. I changed it to 4th week and this solved my problem with the times. 
No reboot nothing. Having a 100 Mbit down, and 10 Mbit up connection and running Web-Server, FTP-Server and Bittorrent File sharing from my LAN. Great having this QoS function as well, where you can set up each service / computer / port, individual, so those traffics don't effect my speed when I'm surfing on the internet, or watching VideoOnDemand.
The only thing I found is that with FW V 1.10, some settings require a reboot. With 1.04 I could change settings in the Virtual Server, Port-forwarding, and save it without rebooting the router to make it valid. Now with 1.10 he wants a reboot after setting changes. |
|
llgomezg
join:2003-04-12
Miami, FL
| reply to dsring
I recently updated to fw v1.10, but I couldn't restore the settings from the Configuration file. Maybe it's just because I modify so many settings (Virtual Servers, WiFi Settings, Port Forwarding, Port Triggering, DHCP, and the list goes on...) that whenever I update the firmware, I'm out of luck restoring the settings from a previous firmware configuration file. Also I updated because I wanted to see if the "Bridge" option was back, but the sad news is that the Bridge is gone...
I haven't really seen any change from v1.05, but I've being using v1.10 for a couple of hours now... |
|
PackRat
@shawcable.net
|  reply to decane
Whaddya mean .. some DIR-655 does not work with Shaw cable modems ???! I upgraded from 1.04 to 1.05 quite some time ago and everything was fine until this morning when the WAN port could not get an IP. Did Shaw update the firmware of their modems recently and messed some Dlink DIR-655 owners up ?
So via a direct connection from laptop to Shaw, I snagged the 1.10 firmware update. It did not resolve the Shaw issue unfortunately, so we all assumed it was a dead WAN port.
Is this a known issue?? Based on "decane"'s comment earlier in this thread I am thinking it might be. It would be nice to know if going back to 1.04 could fix this issue.
But at the same time I just swapped the unit under warranty and will be trying 1.10 tonight on Shaw with the new unit.
Any and all feedback would be appreciated regarding Dlink DIR-655 and Shaw modems. |
|
decane
join:2004-03-24
Vancouver, BC | Yes. going back to firmware version 1.04 works with Shaw. |
|
KenAF
join:2006-01-23
Arlington, VA
2 edits | I upgraded to 1.10 and restored my settings from 1.05. I was having trouble with WAN connectivity so I reset the router back to its defaults. That fixed it.
I tried restoring my settings from 1.05 again and that caused the same problem with WAN connectivity.
It seems obvious to me that some saved settings from 1.05 are not compatible with 1.10, and will cause trouble for the router if you restore them.
I would suggest writing down (copying and pasting) your settings and then re-entering them from scratch with 1.10. I finally did that and 1.10 has been problem free. |
|
AdamMS
@shawcable.net
| reply to dsring
quote:
Whaddya mean .. some DIR-655 does not work with Shaw cable modems ???! I upgraded from 1.04 to 1.05 quite some time ago and everything was fine until this morning when the WAN port could not get an IP. Did Shaw update the firmware of their modems recently and messed some Dlink DIR-655 owners up ?
So via a direct connection from laptop to Shaw, I snagged the 1.10 firmware update. It did not resolve the Shaw issue unfortunately, so we all assumed it was a dead WAN port.
Is this a known issue?? Based on "decane"'s comment earlier in this thread I am thinking it might be. It would be nice to know if going back to 1.04 could fix this issue.
But at the same time I just swapped the unit under warranty and will be trying 1.10 tonight on Shaw with the new unit.
Any and all feedback would be appreciated regarding Dlink DIR-655 and Shaw modems.
HAHAHAHA OMG!
I just spent like 5 hours today talking to Shaw and D-link technical support. I have been on 1.5 for awhile now with no problems, but this morning it would not establish an IP address.
Upgraded to 1.10.. several factory resets.. swapped out ethernet cables.. set everything to dynamic IP.. switched around all my network settings.
I eventually got a replacement from Memory Express. Hooked it up and it immediately worked. Flashed the firmware to 1.10 because you need to have the latest firmware, right?
Ohh man my whole day is gone because of Shaw. 
So, do I just download firmware 1.04 off of D-link's site? I flash my firmware just like any other time?
We should all call into Shaw and make sure they know what the problem is. Hopefully they can fix it, so we all benefit from the new firmware. |
|
Shawn33
@shawcable.net
| It seems many of us are having this problem and I've emailed Shaw about it.
The response? They've changed nothing with their systems, routers aren't supported, try older firmware, power cycle your modem and router, etc. etc.
Many of us were already using fw 1.05 without a hitch so I find it hard to believe that this is a fw issue. If it is, wouldn't the problem have existed right from the start of using 1.05? |
|
celly
join:2007-09-08
Calgary, AB
| reply to dsring
I've had the same grief with the Shaw too. Used 1.05 for a long time and then went to 1.10 with no issues either. Suddenly Shaw went down in the wee hours of this morning and when it came back, my 655 didn't. I thought it was dead. I'm glad 1.04 took care of the issue. I like this router. |
|
DB4DTECHMAN
@co.uk
| reply to dsring
Hi all,
I just updated my router to v1.10 three days ago and everyday my LAN on the router were DEAD,I have to restart my router by taking the power lead out and putting it back in and the router reset it self.
I have to do this everyday,going back to v1.05 it was more stable.
TECHMAN |
|
Devhux
@shawcable.net
| reply to celly
Chalk up two more DIR-655 routers having issues with Shaw.
Yesterday I received a note from a friend who had the DIR-655 warning me not to upgrade to firmware 1.10 as he had just spent quite a while troubleshooting his Shaw connection with said firmware. The end result was that he had to downgrade to 1.04.
Today I woke up to see my internet was down as well. Although I didn't upgrade to 1.10, I had been running 1.05 for quite some time with no issues. Still, I pretty much figured I was having the same issue. Strange thing was, I still had to phone Shaw when I hooked a laptop up to the modem directly for it to work, as the laptop wouldn't even get an IP. They did a reset, and then the laptop worked.
I still had to downgrade to 1.04 to get the router to accept an IP from the modem however.
All I can say is that Shaw is darn lucky that a friend tipped me off to this beforehand -- otherwise I probably still would have no net connection. |
|
hkyu
@shawcable.net
| Good news All.
I just got a follow up call from D-Link and the tech asked me to try their latest 1.11 firmware which should fix this problem. And it did! Not sure when they will post it publicly and hopefully I am not causing anyone any troubles by doing this - but here is the link »dlinksupport.dyndns.org/router/dir-655_a/ |
|
YukonHawk
join:2001-01-07
Patterson, NY
 ·Comcast
|  reply to dsring
I bought the DIR 655 last week from ebay and the unit has been flawless. I did several firmware upgrades as well and each worked perfectly. D-Link has made a really great product. My last wireless router was a Motorola G which worked well for 3 years until died. The range and performance on the 655 is spectacular.
Quick question on the logs...I see that Level 3 Communications has been trying to gain access to my router but has been denied. The only reason I can think is do they provide the backbone for Comcast? Any thoughts as to why they would try to gain access ?  Thanks for any help. |
|
mb
join:2000-07-23
Washington, NJ
·Comcast
 ·Callcentric
·Vonage
 ·Verizon Online DSL
| said by YukonHawk  :I see that Level 3 Communications has been trying to gain access to my router but has been denied. Please describe the log entry caused you to arrive at that conclusion. |
|
YukonHawk
join:2001-01-07
Patterson, NY
·Comcast
| Hi MB...Thanks for the response....Here is a partial list of the log I copied. I went to "whois" to track the IP Address and it came back as Level 3 Communications. Hope that helps
[INFO] Tue Nov 06 22:49:12 2007 Sending log email as log is full
[INFO] Tue Nov 06 22:49:12 2007 Blocked incoming TCP connection request from
4.79.142.206:55301 to 71.234.12.133:426
[INFO] Tue Nov 06 22:49:12 2007 Blocked incoming TCP connection request from
4.79.142.206:55301 to 71.234.12.133:425
[INFO] Tue Nov 06 22:49:12 2007 Blocked incoming TCP connection request from
4.79.142.206:55301 to 71.234.12.133:424
[INFO] Tue Nov 06 22:49:12 2007 Blocked incoming TCP connection request from
4.79.142.206:55301 to 71.234.12.133:423
[INFO] Tue Nov 06 22:49:12 2007 Blocked incoming TCP connection request from
4.79.142.206:55301 to 71.234.12.133:422
[INFO] Tue Nov 06 22:49:12 2007 Blocked incoming TCP connection request from
4.79.142.206:55301 to 71.234.12.133:421
[INFO] Tue Nov 06 22:49:12 2007 Blocked incoming TCP connection request from
4.79.142.206:55301 to 71.234.12.133:420
[INFO] Tue Nov 06 22:49:12 2007 Blocked incoming TCP connection request from
4.79.142.206:55301 to 71.234.12.133:419
[INFO] Tue Nov 06 22:49:12 2007 Blocked incoming TCP connection request from
4.79.142.206:55301 to 71.234.12.133:418
[INFO] Tue Nov 06 22:49:12 2007 Blocked incoming TCP connection request from
4.79.142.206:55301 to 71.234.12.133:417
[INFO] Tue Nov 06 22:49:12 2007 Blocked incoming TCP connection request from
4.79.142.206:55301 to 71.234.12.133:416
[INFO] Tue Nov 06 22:49:12 2007 Blocked incoming TCP connection request from
4.79.142.206:55301 to 71.234.12.133:447
[INFO] Tue Nov 06 22:49:12 2007 Blocked incoming TCP connection request from
4.79.142.206:55301 to 71.234.12.133:446
[INFO] Tue Nov 06 22:49:12 2007 Blocked incoming TCP connection request from
4.79.142.206:55301 to 71.234.12.133:444
[INFO] Tue Nov 06 22:49:12 2007 Blocked incoming TCP connection request from
4.79.142.206:55301 to 71.234.12.133:443 |
|
mb
join:2000-07-23
Washington, NJ
·Comcast
·Callcentric
·Vonage
·Verizon Online DSL
| Are you running or were you running a file trading client? It looks like it might be someones file trading client making an incoming connection request. The whois reports who owns the source IP address. If you did a whois inquiry on my IP address, it would return as Verizon Online. |
|
Scree
In the pipe 5 by 5
join:2001-04-24
Mount Laurel, NJ | Actually, doesn't that look more like a port scanner? |
|
mb
join:2000-07-23
Washington, NJ
·Comcast
·Callcentric
·Vonage
·Verizon Online DSL
| said by Scree :Actually, doesn't that look more like a port scanner? Yes it does. |
|
YukonHawk
join:2001-01-07
Patterson, NY
·Comcast
| reply to YukonHawk
MB...I did have iTunes open at some point during the day the logs were recorded. I did check out BitTorrent's web site, but did not download the program for fear of TOS violations. Although I suspect if I wanted to d/l shows on a legit basis I may need to do so? Anyway....I guess I shouldn't worry to much about the logs as the transmissions were denied. Thanks for the help |
|
acorange
join:2007-11-22
Tallahassee, FL
|  reply to Sim_007
For the one pc that can't use the internet, I found that I had used the "clone this pc's mac address" feature during the router setup, and that pc couldn't use the internet (firmware 1.10). Once I changed the router's mac to be something random, all was ok!
Chip |
|
