Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[FurryNutz]

Seems like the router is just having a hard time doing large xfers either way.
Try using Reserved IP addresses for all of the devices and test.
I presume all of your cables are good?
Are you using any other features on the router besides Multicast Streaming?
I presume this happens even after a full factory reset?

[Trippler]

I am not using any other features, it happens after factory reset, and i have to go now, but will test with static ip when i get back. its wierd though that it can handle 42MiB/s for a long time (like 15 minutes), but will crash after about an equall ammount of time at 3MiB/s when doing sftp (the acctuall output network stream is about 3.2MiB due to overhead data).

[FurryNutz]

Ok let us know the results when you get back. One other thing you could test. Remove the ISP modem and router for a test. Set up static IPs and a subnet address on the PC and the Server. Connect these 2 to the switch and you should be able to connect and share. Test again the file xfer. If you don't see any issues, them I'm thinking this router could be possibly bad.  If you happen to see the same issues, Possibly one of the LAN cards on either PC could be bad.

[Trippler]

Ok, i am back, gonna test transfeers between a 3rd and 4th pc to rule out that it may be the lan cards.
Edit: Just ruled out the lan cards ^_^

[FurryNutz]

Ok then, so your cables, switch, and LAN cards are good. I would presume that your router is having an issue here. Is the FW up to date on the router? Whats currently loaded?

[Trippler]

Its firmware is 1.31EU
I updated to that since this happened with old firmware aswell.

[FurryNutz]

Are you in Europe or over seas?
What Hardware version is this router?

[Trippler]

Like i said in OP, A4 is hardware, im in Europe

[FurryNutz]

I guess I didn't look into the next page of postes. hehe. So your in Europe. I would probably get ahold of DLink and see if you can upgrade the FW and see if that helps as a last resort. I would say go ahead if you were in North America as there is updates that are more resent however your in the EU and recommend getting ahold of them directly and finding out what is available for you.
I see that there is something more recent by posting here:
http://forums.dlink.com/index.php?topic=16160.0

If you can get an update, do the following:
Factory reset
Update the FW
Factory reset once more

Then test. If you see the same issues then I would presume the router needs to be RMA'd. Let DLink know what you have done thus far in testing.

Let us know how it goes.

[Redu]

Hi, i have a DIR-655 router, and am mostly happy with it. When under heavy load though, it crashes and completely shuts down.

A little more information:
The load i am talking about is me uploading files from one computer on the network to another with filezilla over sftp. The connection route goes like this: #1 Pc uploading files-> #2 D-Link switch-> #3 DIR-655 Router-> #4 File server.

The file server has a network card that supports 100MBit which is 12.5MiB/s if my math is correct. So theoretically i wouldn't expect any problems before reaching those speeds. Now to the main problem. If i limit filezilla's speed to 12MiB/s the router will crash fast, after like a minute. When limiting to 5MiB/s it will stay up a few minutes before crashing (i have it at 5MiB/s now and it has crashed 4 times while writing this post).
When limiting to 3MiB/s it is stable almost 15 minutes before crashing.
The acctuall speed output from my computer is hovering around 3000 to < 3200 KiB/s

What happens when it crashes?
All connections get broken. Every other computer on the network gets cut off the net. No connections can be established to computers inside or outside the network. Can't connect to the router controllpanel (192.168.1.1 in my case).

I'm running Hardware version: A4 and Firmware version: 1.31EU.
The router does not seem 'too hot' when this happens, maybe 30ish degrees C.
The files i am uploading are flac files, often a few (like 20)GiB at the time.
I do not have the wireless net activated.
edit: I just flick the power switch off and on to make it work again.

My question: Does anyone know what causes this? Does anyone know how to fix this?

Thanks,
Niklas

Yes this was exactly my case. It was very very annoying to have crashes in the middle of large (~4GB) hd movie file transfers from my PC to the Media Player downstairs over 100Mbps connection. Luckily this issue is now a matter of past for me.

Conditions;

1) FTP client on the PC is Filezilla and the Media Player has an FTP server of it's own which i have no idea what it is other than it's IP address (192.168.1.253) username and password.
2) The media player is directly connected to one of the ports of my cable modem's router at 100Mbps.
3) DIR 655's internet connection goes to another port of the cable modem's router at 100Mbps.
4) PC and MAC computers are conected to DIR 655 at gigabit speed.
5) Wireless print server connected to DIR 655 over wireless.
6) Browser installed on the PC is Chrome. (15.0.865.1000)

Problem : DIR-655 crashes during FTP transfer from PC to Media Player after 20-30 seconds and needs power disconnected and reconnected to go up again. If i am lucky transfer resumes; mostly not.

I have noticed that browser activity accelerates the crash. I thought may be a port or something is being accessed both by Filezilla and Chrome at the same time which ought not to be. So closing Chrome has solved the problem in the first place. Then a little tuning in Filezilla has enabled it working perfectly fine even when Chrome is fully active, just as it should be. So...

Prompt Solution : Close all open browsers completely and it wouldn't crash.
Real Solution : Take filezilla into Active mode (edit->network configuration wizard...) select use servers external ip address, select get ip address from the following url (http://ip.filezilla-project.org/ip.php) use following port range (6000-7000) Do the test and it shall pass.

With the real solution it's never crashed again even with very busy web sites are open simultaneously.

[FurryNutz]

How many connections in and out are you allowing in FileZilla, if your allowing alot of connections then it's possible that the connections are crashing the router. I would cut back the connections to minimum that you need only for downloading. Let us know if this helps. If your only seeing the crash when doing FTP using Filezilla, then the cause probably lies here.
Might have someone use teamviewer.com and remote in to review your router settings to be sure.

Yes this was exactly my case. It was very very annoying to have crashes in the middle of large (~4GB) hd movie file transfers from my PC to the Media Player downstairs over 100Mbps connection. Luckily this issue is now a matter of past for me.

Conditions;

1) FTP client on the PC is Filezilla and the Media Player has an FTP server of it's own which i have no idea what it is other than it's IP address (192.168.1.253) username and password.
2) The media player is directly connected to one of the ports of my cable modem's router at 100Mbps.
3) DIR 655's internet connection goes to another port of the cable modem's router at 100Mbps.
4) PC and MAC computers are conected to DIR 655 at gigabit speed.
5) Wireless print server connected to DIR 655 over wireless.
6) Browser installed on the PC is Chrome. (15.0.865.1000)

Problem : DIR-655 crashes during FTP transfer from PC to Media Player after 20-30 seconds and needs power disconnected and reconnected to go up again. If i am lucky transfer resumes; mostly not.

I have noticed that browser activity accelerates the crash. I thought may be a port or something is being accessed both by Filezilla and Chrome at the same time which ought not to be. So closing Chrome has solved the problem in the first place. Then a little tuning in Filezilla has enabled it working perfectly fine even when Chrome is fully active, just as it should be. So...

Prompt Solution : Close all open browsers completely and it wouldn't crash.
Real Solution : Take filezilla into Active mode (edit->network configuration wizard...) select use servers external ip address, select get ip address from the following url (http://ip.filezilla-project.org/ip.php) use following port range (6000-7000) Do the test and it shall pass.

With the real solution it's never crashed again even with very busy web sites are open simultaneously.