D-Link Forums

The Graveyard - Products No Longer Supported => D-Link Storage => DNS-323 => Topic started by: cutback32 on August 22, 2010, 11:51:17 AM

Title: BitTorrent problem
Post by: cutback32 on August 22, 2010, 11:51:17 AM
Hi all!

I've searched here and the web and haven't found any solution.  I hope you can steer me in the right direction.

On the downloads page, I do not see any of my torrents.  I just started a new one and it is not listed however I checked the incomplete folder and it is there and downloading.  Also, when I go to the setting page it says "Please wait... Downloading settings." but never does anything else.

(http://i84.photobucket.com/albums/k16/cutback32/random3/a292446f.jpg)
(http://i84.photobucket.com/albums/k16/cutback32/random3/20ed047e.jpg)

I use Firefox so I thought maybe that was the problem so I tried IE8 and got the following error:

Webpage error details

User Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 5.1; Trident/4.0; .NET CLR 1.1.4322; .NET CLR 2.0.50727; .NET CLR 3.0.4506.2152; .NET CLR 3.5.30729; .NET4.0C)
Timestamp: Sun, 22 Aug 2010 18:44:25 UTC


Message: Expected ':'
Line: 48
Char: 27
Code: 0
URI: http://192.168.1.67/imodule/BitTorrent/webui/btsdk.js

When I first setup BitTorrent, it worked.  Then I started to get a "retry" error when looking at the list of torrents and now I have nothing.

Any help would be appreciated.  Thanks!
Title: Re: BitTorrent problem
Post by: ninjalawyer on August 22, 2010, 01:37:39 PM
I started the having the same problem as soon as I inserted a second drive.  Have you recently added a new drive?
Title: Re: BitTorrent problem
Post by: cutback32 on August 22, 2010, 02:23:21 PM
Haven't changed anything since I set it up
Title: Re: BitTorrent problem
Post by: jamieburchell on August 22, 2010, 03:30:06 PM
Try clearing your Internet cache and perhaps temporarily disable any script blockers or scanners you may have running as part of antivirus software. Of couse, make sure JavaScript is enabled. That JavaScript error may be a red herring, it may not be the cause of the issue. As Internet Explorer's JavaScript error reporting is lame, what does Firefox's error console say?