D-Link Forums
The Graveyard - Products No Longer Supported => Routers / COVR => DIR-655 => Topic started by: stogs on May 05, 2009, 11:56:40 AM
-
I have a HP mediasmart server that attempts to automatically configure port forwarding to enable my home website and remote access. This all worked well in 1.21 and 1.22b, I seem to be having issues with it in 1.31.
I followed all the instructions for the upgrade and did not reload the old config. I started from scratch after restoring to defaults. I see the following items in the log when my homeserver attempts to configure port forwarding, these entries have always been the same between firmware versions:
INFO] Sat Jan 31 12:35:14 2004 UPnP added entry 255.255.255.255 <-> XXX.XXX.XXX.XXX:4125 <-> 192.168.1.198:4125 TCP timeout:0 'WHS_4125'
[INFO] Sat Jan 31 12:35:14 2004 UPnP added entry 255.255.255.255 <-> XXX.XX.XXX.XXX:443 <-> 192.168.1.198:443 TCP timeout:0 'WHS_443'
[INFO] Sat Jan 31 12:35:14 2004 UPnP added entry 255.255.255.255 <-> XXX.XXX.XXX.XXX:80 <-> 192.168.1.198:80 TCP timeout:0 'WHS_80'
Note: Actual IP removed and replaced with X, it was correct. :)
After it executes, everything works fine for about 10 minutes and then the settings must timeout. I have manually added the port forwarding entries and everything seems to work ok so far, I am just curious as to why this behavior changed. Any thoughts?
-
It would depend on how the server is communicating with the gateway device. Is it using UPnP?
-
I believe so, yes.
-
It should ber working without a problem. Unless you turned off uPnP on the router or there is an internet gateway device on the WAN side and those ports need to be opened too. That does not happen automatically....
-
I agree it should be working. Since it was working fine in previous firmware versions for months. I have Upnp turned on. From the logs I can see it forwarding the ports. It will work for about 10 minutes and then I start to see request blocked in the logs for those same ports.
It has been working fine for a couple days after I manually forwarded the ports. I was just curious if this was a bug in the new firmware or if I had some setting messed up. I was also curious if anyone else was seeing this issue. This automatic router configuration is out of the box functionality for Windows Home Server.
-
Hi stogs!
I had exactly the same issue with 1.31 and my Windows Home Server.
I solved it by disabling UPnP and manually forwarding the ports.
UPnP does not work properly in version 1.31.
-
Hi stogs!
I had exactly the same issue with 1.31 and my Windows Home Server.
I solved it by disabling UPnP and manually forwarding the ports.
UPnP does not work properly in version 1.31.
Apparently only with WHs, because 1.31 uPnP does a fine job with torrent clients, all sorts of games, RDP....
-
I am having a port forwarding problem, I am trying to configure several ports for 3 computers on my network. I have tried to configure several rules depending on each computers static LAN address, I save it and reboot the router and the list is empty, no rules whatsoever are saved.
Another question, Is there a way to create rules for the LAN and not machine specific? The 3 computers have the same software. I would like to be able to just open the ports so the 3 can actually interact with the internet. Is this possible?
Thanks,
AJ
-
What browser are you using to configure the router?
-
IE 8 or Firefox 3.0.10, neither one saves. I even tried Chrome, still no saving. I will try Safari.
Ok I got it working as Application Rules. So all the necessary ports are open for all computers in my LAN.
I thought I had it configured but no, the Application Rules table won't get deleted, either manually or hard resetting the router. It is driving me crazy.
-
I am also having this issue with my windows home server.
-
Hey guys,
I have had the same problem and was experiencing the uPnP issue with my slingbox as well.
What I did was uncheck the uPnP option, reboot the router, re-check uPnP, and reboot the router and suddenly everything started working again.
Might be a glitch in the firmware.
Try it and let me know if it worked for you.
D.
-
I skipped right to the end of this post, so sorry if its been said already:
You mentioned you went from 1.2x to 1.3x. What I want to know:
1) Did you backup your 655 config prior to the upgrade?
2) In lieu of that, did you write down your settings?
3) If you haven't yet, can you? :)
4) Have you tried resetting to defaults via either the GUI and/or the RESET button?
5) Would you be willing to do that and put said settings back into the 655?
Most of the issues I see are from when the router makes a generational jump in firmware and somehow, someway the config gets screwy. The only solutions I've seen in the forum and real life that really worked included factory resets. You could spend hours instead of fixing the actual problem doing things such as turning an unrelated feature off... suddenly makes port forwarding work. Solutions like that simly mask the issue.
Just my two cents.
-
1) Did you backup your 655 config prior to the upgrade?
No not in this instance as I was going to configure the router from scratch
2) In lieu of that, did you write down your settings?
I have print out of each page where I have non standard settings
4) Have you tried resetting to defaults via either the GUI and/or the RESET button?
I have tried two factory re-sets using both the web to re-set the router,
and have also tried the button on the back of the router
Neither scenrio worked, its not really a problem as I forwarded the ports on manually, but if a feature is there I do like to use it..lol
Is there anything else we can do to try and resolve this? Will the logs show why the ports have been closed when they were previously opened by UPnP?
-
I am wondering if it could be somthing to do with the below logging.
[INFO] Thu May 14 21:59:06 2009 Blocked incoming TCP connection request from xxx.xxx.xx.xxx:3176 to xxx.xxx.xx.xxx:443
[INFO] Thu May 14 21:58:57 2009 Above message repeated 2 times
[INFO] Thu May 14 21:58:41 2009 Blocked incoming TCP connection request from xxx.xxx.xx.xxx:3175 to xxx.xxx.xx.xxx:80
[INFO] Thu May 14 21:58:31 2009 Above message repeated 2 times
443 and 80 are 2 of the ports which windows home servers uses. Both the request from IP address and the to IP address were my static IP address assigned by my ISP.
Any thoughts?
-
I am having a port forwarding problem, I am trying to configure several ports for 3 computers on my network. I have tried to configure several rules depending on each computers static LAN address, I save it and reboot the router and the list is empty, no rules whatsoever are saved.
Another question, Is there a way to create rules for the LAN and not machine specific? The 3 computers have the same software. I would like to be able to just open the ports so the 3 can actually interact with the internet. Is this possible?
Thanks,
AJ
I had to make port forwarding rule too, saved it (and rebooted like it ask), and after this, port forwarding rules are empty again.
IE 8 & Chrome... Have no other browsers installed so i can not make any rules with thise? cmon.. Is this firmware really full of this kind of issues and we have no chance to go back...
-
I have a HP mediasmart server that attempts to automatically configure port forwarding to enable my home website and remote access. This all worked well in 1.21 and 1.22b, I seem to be having issues with it in 1.31.
Like the OP, I am experiencing the same problem with the DIR-655 and FW 1.31 and Windows Home Server that I did not experience under 1.21.
The Console will complain of port forwarding failures often. Opening the Home Server Console, going to "Settings", then "Remote Access" and selecting "Repair" will often restore proper function, but it will shortly complain some minutes later that port forwarding has failed once again (persumably during some sort of periodic renegotiation?).
Problem persists after a 30-30-30 reset, and entering the router configuration again by hand from scratch.
Since the only change was upgrading the router firmware to 1.31, I can only conclude the fault lies there. For that reason alone (compounded by the inability to downgrade to what was a working version), I'm very unhappy with this firmware release. This feature worked properly in earlier firmware releases.
-
Does anyone have any ideas as to what could be causing this? What has changed in the formware between 1.21 amd 1.31? Or is this a simple case of each sompany having a slightly different understanding of the UPnP standard.
TLE
-
try un checking your DNS & reboot router & system.
-
Do you mean 'Enable DNS Relay' in the Network setup section?
-
try un checking your DNS & reboot router & system.
DNS relay?
DNS or not, i can not save any changes in port forwarding page... After save&reboot this page is empty again..
-
try un checking your DNS & reboot router & system.
No effect on the problem with uPnP and WHS.
-
how many of you restored configuration file?
-
how many of you restored configuration file?
Neither of us, apparently.
I followed all the instructions for the upgrade and did not reload the old config. I started from scratch after restoring to defaults.
Problem persists after a 30-30-30 reset, and entering the router configuration again by hand from scratch.
A corrupted config file was the first thing I thought of. I don't think it's related to that, and at this point there's two independent corroborations.
It worked fine in 1.21, it doesn't in 1.31. Simple as that. Given the other problems, this feature breaking doesn't seem to far-fetched to me. I would, however, want to be sure that this issue gets sufficient attention for the next release.
-
Yup, fresh config here too. Port forwarding just do not work at all..
-
Same here, fresh config on each attempt. Even tried the 30:30:30 reset. Even tried downloading a fresh copy of the firmware.
Agreed, I would like to seem some response from maybe some of the D-link engineers or somthing.
However I suspect that this could be due to an inconsistency in the way UPnP is implemented. Although there is a standard each software house or hardware place seem too interpret the standard slightly differently.
Let's hope we get it fixed.
TLE
-
No go with upnp off too... :-X
Maybe d-link remove this port forwarding option in next firmware. ;D
-
Glad to see I'm not the only one...
Really disappointing that D-Link dropped the ball on this though. I don't care so much about UPnP, but I need my Port Forwarding/Virtual Server options to work.
I sent them an email about it too, I suggest everyone does in case you haven't already. That way they'll definitely see it.
-
It's odd that so many of you guys are seeing this, we're not able to replicate the error. Has any of you tried reflashing the firmware?
Also that 30-30-30 "reset" you're doing will not have an effect on the 655, Ubicom products do not have a crash reset.
-
I have tried re-flashing mine on a few occasions with no success, and always re-configuring the router from scratch.
There seems to be two seperate issues within this the thread, the original which was port fowarding was failing after x amount of minutes when set up by UPnP, and those who cannot save there port forwarding rules manually.
Lycan, as for the UPnP problem, is there anything in the logs which may or may not help?
Thanks
TLE
-
It's odd that so many of you guys are seeing this, we're not able to replicate the error. Has any of you tried reflashing the firmware?
I'll give that a shot today and manually configure everything again. I won't reload my current configuration.
I don't really use UPnP so I can't comment there, I just cannot keep any of my port forwarding and virtual server settings after the router reboots, but every single other setting stays.
UPDATE:
Well I opened up IE8 (Windows 7 RC), loaded the defaults on the router, then enabled Compatibility Mode in IE8. Then I logged back in and flashed the firmware again. Once it was done rebooting, logged in and restored defaults yet again. After it rebooted, then I went ahead and configured all my settings (didn't load them). Now all seems to be working fine.
Previously I had updated the firmware using Firefox 3.5 Beta 4, no idea if using IE8 in compatibility mode helped or not but might as well detail what I did precisely.
EDIT: Spoke too soon I guess. Just logged in and everything was gone...
-
try "Use Unicasting", Ive noticed a drop in blocked ports.
-
It's odd that so many of you guys are seeing this, we're not able to replicate the error. Has any of you tried reflashing the firmware?
Also that 30-30-30 "reset" you're doing will not have an effect on the 655, Ubicom products do not have a crash reset.
No other recommendations Lycan?
-
bump:
After taking a closer look @ my setup I have same issues as others with port forwarding. Torrent client and some web pages loading into right ports which explains the 404's for some web sites. I thought maybe DNS Relay was the issue but was wrong. Not sure if dropped packets on the wireless side can be blamed on this as well, just a thought.
The other posts on this topic explain it all, port forwarding dose not work with 1.31NA. 1.21 had no problem.
-
Did you have a good look at your internet gateway device? Some need a restart to reconnect properly with an updated router.
-
Here is log for my port forwarding setup attempt..
Mon 1.6.2009 20:42:31 : 192.168.0.1 >>LOGAUDIT.Info<<<110>Mon Jun 01 20:42:33 2009 D-Link Systems DIR-655 System Log: Allowed configuration authentication by IP address 192.168.0.100
Mon 1.6.2009 20:43:12 : 192.168.0.1 >>LOGAUDIT.Info<<<110>Mon Jun 01 20:43:14 2009 D-Link Systems DIR-655 System Log: primary: Unlock AP setup
Mon 1.6.2009 20:43:12 : 192.168.0.1 >>LOGAUDIT.Info<<<110>Mon Jun 01 20:43:14 2009 D-Link Systems DIR-655 System Log: guest: Unlock AP setup
Mon 1.6.2009 20:43:13 : 192.168.0.1 >>LOGAUDIT.Info<<<110>Mon Jun 01 20:43:15 2009 D-Link Systems DIR-655 System Log: Stored configuration to non-volatile memory
Mon 1.6.2009 20:43:21 : 192.168.0.1 >>LOGAUDIT.Info<<<110>Mon Jun 01 20:43:22 2009 D-Link Systems DIR-655 System Log: Disconnect all stations
Mon 1.6.2009 20:43:21 : 192.168.0.1 >>LOGAUDIT.Info<<<110>Mon Jun 01 20:43:22 2009 D-Link Systems DIR-655 System Log: The DHCP address xx.xxx.xxx.xxx is released by the user
Mon 1.6.2009 20:43:21 : 192.168.0.1 >>LOGAUDIT.Info<<<110>Mon Jun 01 20:43:22 2009 D-Link Systems DIR-655 System Log: primary: Unlock AP setup
Mon 1.6.2009 20:43:21 : 192.168.0.1 >>LOGAUDIT.Info<<<110>Mon Jun 01 20:43:22 2009 D-Link Systems DIR-655 System Log: guest: Unlock AP setup
Mon 1.6.2009 20:43:22 : 192.168.0.1 >>LOGAUDIT.Info<<<110>Mon Jun 01 20:43:23 2009 D-Link Systems DIR-655 System Log: Stored configuration to non-volatile memory
Mon 1.6.2009 20:43:22 : 192.168.0.1 >>LOGAUDIT.Info<<<110>Mon Jun 01 20:43:23 2009 D-Link Systems DIR-655 System Log: Time server ntp1.dlink.com is at IP address 207.232.83.70
Mon 1.6.2009 20:43:22 : 192.168.0.1 >>LOGAUDIT.Info<<<110>Mon Jun 01 20:43:23 2009 D-Link Systems DIR-655 System Log: Requesting time from 207.232.83.70
Mon 1.6.2009 20:43:22 : 192.168.0.1 >>LOGAUDIT.Info<<<110>Mon Jun 01 20:43:24 2009 D-Link Systems DIR-655 System Log: Time synchronized
Mon 1.6.2009 20:43:28 : 192.168.0.1 >>LOGAUDIT.Info<<<110>Mon Jun 01 20:43:27 2009 D-Link Systems DIR-655 System Log: guest: Unlock AP setup
Mon 1.6.2009 20:43:28 : 192.168.0.1 >>LOGAUDIT.Warning<<<108>Mon Jun 01 20:43:27 2009 D-Link Systems DIR-655 System Log: Wireless schedule init
Mon 1.6.2009 20:43:28 : 192.168.0.1 >>LOGAUDIT.Info<<<110>Mon Jun 01 20:43:27 2009 D-Link Systems DIR-655 System Log: Device initialized
Mon 1.6.2009 20:43:28 : 192.168.0.1 >>LOGAUDIT.Info<<<110>Mon Jun 01 20:43:28 2009 D-Link Systems DIR-655 System Log: LAN Ethernet Carrier Detected
Mon 1.6.2009 20:43:28 : 192.168.0.1 >>LOGAUDIT.Info<<<110>Mon Jun 01 20:43:28 2009 D-Link Systems DIR-655 System Log: LAN interface is up
Mon 1.6.2009 20:43:28 : 192.168.0.1 >>LOGAUDIT.Info<<<110>Mon Jun 01 20:43:29 2009 D-Link Systems DIR-655 System Log: WAN interface cable has been connected
Mon 1.6.2009 20:43:29 : 192.168.0.1 >>LOGAUDIT.Info<<<110>Mon Jun 01 20:43:29 2009 D-Link Systems DIR-655 System Log: Bringing up WAN using DHCP
Mon 1.6.2009 20:43:30 : 192.168.0.1 >>LOGAUDIT.Info<<<110>Mon Jun 01 20:43:30 2009 D-Link Systems DIR-655 System Log: Obtained IP Address using DHCP. IP address is xx.xxx.xxx.xxx
Mon 1.6.2009 20:43:31 : 192.168.0.1 >>LOGAUDIT.Info<<<110>Mon Jun 01 20:43:31 2009 D-Link Systems DIR-655 System Log: Estimating speed of WAN interface
Mon 1.6.2009 20:43:36 : 192.168.0.1 >>LOGAUDIT.Info<<<110>Mon Jun 01 20:43:36 2009 D-Link Systems DIR-655 System Log: Starting DHCP server
Mon 1.6.2009 20:43:40 : 192.168.0.1 >>LOGAUDIT.Info<<<110>Mon Jun 01 20:43:40 2009 D-Link Systems DIR-655 System Log: Wireless link is up
Mon 1.6.2009 20:43:48 : 192.168.0.1 >>LOGAUDIT.Info<<<110>Mon Jun 01 20:43:49 2009 D-Link Systems DIR-655 System Log: WAN interface speed measurement completed. Upstream speed is 2909 kbps
Mon 1.6.2009 20:43:52 : 192.168.0.1 >>LOGAUDIT.Info<<<110>Mon Jun 01 20:43:53 2009 D-Link Systems DIR-655 System Log: Time server ntp1.dlink.com is at IP address 207.232.83.70
Mon 1.6.2009 20:43:52 : 192.168.0.1 >>LOGAUDIT.Info<<<110>Mon Jun 01 20:43:53 2009 D-Link Systems DIR-655 System Log: Requesting time from 207.232.83.70
Mon 1.6.2009 20:43:52 : 192.168.0.1 >>LOGAUDIT.Info<<<110>Mon Jun 01 20:43:54 2009 D-Link Systems DIR-655 System Log: Time synchronized
Mon 1.6.2009 20:43:53 : 192.168.0.1 >>LOGAUDIT.Info<<<110>Mon Jun 01 20:43:54 2009 D-Link Systems DIR-655 System Log: Firmware upgrade server wrpd.dlink.com.tw is at IP address 210.242.32.129
Mon 1.6.2009 20:43:55 : 192.168.0.1 >>LOGAUDIT.Info<<<110>Mon Jun 01 20:43:57 2009 D-Link Systems DIR-655 System Log: primary: Unlock AP setup
Mon 1.6.2009 20:43:55 : 192.168.0.1 >>LOGAUDIT.Info<<<110>Mon Jun 01 20:43:57 2009 D-Link Systems DIR-655 System Log: guest: Unlock AP setup
Mon 1.6.2009 20:43:56 : 192.168.0.1 >>LOGAUDIT.Info<<<110>Mon Jun 01 20:43:58 2009 D-Link Systems DIR-655 System Log: Stored configuration to non-volatile memory
Mon 1.6.2009 20:43:58 : 192.168.0.1 >>LOGAUDIT.Info<<<110>Mon Jun 01 20:44:00 2009 D-Link Systems DIR-655 System Log: Firmware upgrade server wrpd.dlink.com.tw is at IP address 210.242.32.129
Mon 1.6.2009 20:44:10 : 192.168.0.1 >>LOGAUDIT.Info<<<110>Mon Jun 01 20:44:12 2009 D-Link Systems DIR-655 System Log: Allowed configuration authentication by IP address 192.168.0.100
Mon 1.6.2009 20:44:13 : 192.168.0.1 >>LOGAUDIT.Info<<<110>Mon Jun 01 20:44:14 2009 D-Link Systems DIR-655 System Log: Log viewed by IP address 192.168.0.100
All log from router login, port forward rule make, save, boot and new router login. Port forwarding page is all empty again.
Re-flash done, and no go.
-
Oh CMON D-link!
Enabled Securespot and BAM port forwarding works ok... My securespot test period has expired allready but i did get this annoying "last change to buy" window and didnt get to net before i choose to abandon this great promotion...
So, enabled securespot, save & boot, make port forward rule, save & reboot and there it is. Working and saved settings..
This is BS... ;D
edit: Can not add OR remove any port forwarding rules if securespot is not enabled...
When i make or remove rule with securespot theres this in log:
Mon 1.6.2009 21:41:42 : 192.168.0.1 >>LOGAUDIT.Info<<<110>Mon Jun 01 21:41:44 2009 D-Link Systems DIR-655 System Log: Establishing connection w/ auth server: 165.193.49.40:443.
Mon 1.6.2009 21:41:43 : 192.168.0.1 >>LOGAUDIT.Info<<<110>Mon Jun 01 21:41:44 2009 D-Link Systems DIR-655 System Log: Local firewall edits sent successfully.
Hope this help
-
Your unit needs to be replaced and the replacement needs to be tested.
Let me see what I can set up.
-
Your unit needs to be replaced and the replacement needs to be tested.
Let me see what I can set up.
Easy to say, but not so easy to do...
So everyone who have this problem have broken router because of 1.3x f/w? I think we should wait if someone else try this out and then see what next. It seems to me that this router and securespot are little too married with each other... How can this be hardware problem?
btw. If i change this router, i should update new one to 1.3x too to see if theres everything ok?! Have to take securespot trial to use too and let it expire etc...
So maybe this "new router" is not nr1 solution for now?
-
It has nothing to do with shareport. I want your unit so I can see it happen for myself.
Please understand that if this was a failure of the firmware as a whole then the entire community would be suffering.
Rather I beleive there is a factor thats causing select units to behave improperly and I need a failing unit to prove it.
I offer you an RMA with a replacement unit that I've tested myself.
-
It has nothing to do with shareport. I want your unit so I can see it happen for myself.
Please understand that if this was a failure of the firmware as a whole then the entire community would be suffering.
Rather I beleive there is a factor thats causing select units to behave improperly and I need a failing unit to prove it.
I offer you an RMA with a replacement unit that I've tested myself.
Sure i can do that. Send you PM.
-
I did some more testing and found that if i reset router to factory defaults, and do port forward rule with securespot enabled (default), and restore factory defaults after this again, it wont reset port forwarding at all. So this rules are saved to somewhere in securespot service, not in router? Securespot is have to use feature?
edit: disabled securespot and restored factory default after this but still didn't wipe out port forward rule...
-
You can add me to the list of people have trouble with Windows Home Server port forwarding and firmware 1.31 on the DIR-655. I will try disabling the upnp and manually setting the ports. I have tried to set the ports without disabling the upnp and the settings only hold for a few minutes. I too am glad I am not the only one with this problem.
-
Add me to that same list with WHS,firmware 1.31 and port forwarding not working. How long are we going to have to complain about this before something is done?
-
It seems as though we have not even passed the first step.....acknowledging that there is a problem. All I have seen is that they (D-link), cannot recreate. Have they tried with Windows Home Server?
-
Can someone with "port forwarding rule not saved" problem try to make rule with and without securespot checked?
-
I didn't read through every page, so sorry if this has been mentioned. Firmware 1.3x has not been good to me (A1 hardware) and this is one of the problems I was experiencing. The fix for me (and I can reproduce it) was keeping graphic authentication ON. As soon as I turn it off I can make one or two changes in the advanced tab but then after that no more take effect and ever so often it defaults to no settings there. With graphic authentication ON (which is the default for me on the 1.3x firmware) I haven't had this problem occur.
-
New Beta firmware has been posted
http://forums.dlink.com/index.php?topic=5841.0
-
I didn't read through every page, so sorry if this has been mentioned. Firmware 1.3x has not been good to me (A1 hardware) and this is one of the problems I was experiencing. The fix for me (and I can reproduce it) was keeping graphic authentication ON. As soon as I turn it off I can make one or two changes in the advanced tab but then after that no more take effect and ever so often it defaults to no settings there. With graphic authentication ON (which is the default for me on the 1.3x firmware) I haven't had this problem occur.
Any luck with the beta 1.32?
-
I have finally gotten the manual port forwarding settings to stick. I have securespot turned off and upnp turned on. Everything seems to be working except I now have to cycle the power on the dir-655 a couple of times a week. I just installed the new beta 1.32. The release notes say the only change is the captcha is off by default now.
-
Hello i am with the 1.30NA firmware and i had the problem where i couldn't save the ports that i forwarded.I've tried everything and the problem fixed when i opened the router with IE 8 the 32bit one .And everything was ok so i suggest you give it a try.
-
bump
-
Bump -> with what purpose?
-
It is useless. I have had to cycle the power twice this week. I will be leaving town for a couple of weeks and won't be able to access my server. I wish there was a way to go back on this firmware. I can't believe dlink can't recreate the problem with this many people complaining about it. btw I have the A3 hardware.
-
Bump -> with what purpose?
Another member has an issue (cdysthe ) I thought this thread might give him some insight incase he/she missed it.
-
Can anybody help me because i'm having the same problem i save the port forward or the virtual server and when i test the ports on they are always closed even when they are part of the port forwarding table , i already updated to 1.32 NA same thing when i do a Hw reset it clears everything except the port forwarding rules and virtual servers .
-
This sucks!
I've got the problem too. This really makes the whole piece of **** totally useless.
Please fix this asap, ive alreade spent 2 hours with this ****!
Edit: I tried to install the 1.32 firmware. It took a minute to upload and then like 90 seconds for it to install. No when i log on to the Router it still says "Hardware Version: A4" and "Firmware Version: 1.21EU"
-
Bump -> with what purpose?
Are you really bump critiquing?
That is a new one by me.
-
This sucks!
I've got the problem too. This really makes the whole piece of **** totally useless.
Please fix this asap, ive alreade spent 2 hours with this ****!
Edit: I tried to install the 1.32 firmware. It took a minute to upload and then like 90 seconds for it to install. No when i log on to the Router it still says "Hardware Version: A4" and "Firmware Version: 1.21EU"
Did you try to disconnect everything but power and your wired computer, then reset the router to its factory defaults by pressing the reset button for about 10 seconds ?
Wait until it restarts and try to update again.
But there is no way to downgrade to an earlier version before 1.3x ! So if it doesn't help...
I would suggest, you contact the D-Link support in your country.
-
Are you really bump critiquing?
That is a new one by me.
Funny Ah.. :-\
-
Are you really bump critiquing?
That is a new one by me.
The lack of 'moderation enthousiasm' shows...
-
The lack of 'moderation enthousiasm' shows...
Do I need to start keeping a second account with no mod privilege just to give you a hard time without my job coming up? You are right, I am too lazy for that.
Or would you prefer I become one of those lock, ban, delete, and ask questions later mods? I prefer to do as little modding as possible, only when the situation warrants it do I mod.
A single bump in a thread this long is WAY below my moderation threshold, your still dealing with personable me. I just couldn't figure out why you would care.
Have a nice day Demonized! And also to the rest of you!
-
Perhaps keep the thought in your mind and not on the forum?
Apparently a bump is way below your standards for a reply, I'm really puzzled why my reply to the bump sets you off, especially when it contains no offending words, insults or such.
If it is 'personal' (which I suspect from earlier comments on my replies) you're not acting really as a professional, perhaps creating a non-mod account to enable you're urges is a good idea.
-
man you guys are bitter!
-
I'm still laughing ;D
-
Yeah I wouldn't call it setting me off, I have been laughing the entire time as well.