Print

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

[Clancy]

I now have a log entry for when I temporarily lost connection during which Shareport said that my drive did not disconnect properly. I don't think this is related to Shareport, its just that this kind of disconnect wreaks havoc on any attempt to copy a large file to my USB drive. Can anyone tell me what just happened when I see this?:

UPnP renew entry 255.255.255.255 <-> 173.74.174.35:15827 <-> 192.168.0.190:4907 UDP timeout:0 'svchost (192.168.0.190:4907) 15827 UDP'

173.74.174.35 is my WAN address and 192.168.0.190 is my LAN address. I have UPnP discovery turned on. OK, I understand that the Router renewed my entry, I just want to understand why. Is it normal?

[coppertrail]

Just did the upgrade. An EBKAC gave me a problem with the wireless which was quickly resolved. So far, so good.

[jim2664258]

I must be the only person on here that has always been able to restore a saved configuration file after upgrading firmware, and have it work every time.  I change quite a few settings too.  However I don't use SharePort, CAPTCHA (which I freaking hate) and who knows what else others here do.  Probably depends on what features you enable, or likely what combinations of features you use.

And I use Firefox every time.  I think the browser-specific comments are way overplayed.

Of course all it takes is getting burned once to completely change your opinion on that 

[EddieZ]

Got burned once with a restored config, but tried again anyhow. And it worked perfectly.

[Clancy]

Since first updating my firmware to 1.31 and now 1.32 Beta and installing Shareport, for weeks my energy has been spent trying to successfully create a drive image onto a USB drive attached to the USB shareport. Each attempt was met with eventual failure in the way of Delayed Write Errors. At first I thought it was a fault of either my drivers, my paging memory, USB cabling, etc. I never tried to simply hang the drive off of my Laptop and see what happened until today. I incorrectly assumed that I would receive the same Delayed Write Error since the issue is related to the transference of large chunks of data over USB ports. I could not have been more wrong. I imaged 33GB of data in 53 minutes and it worked so flawlessly that it made my head spin. I will not stop trying to image to the drive using Shareport so long as D-Link continues to provide updates to either the firmware, or software, or both. I have copied a 20MB file to the Shareport drive without a problem but any attempt to continuously copy data, as in my imaging program, will ultimately crash the drive and bring my computer to it's knees.

Edit: Not sure what has changed since taking the drive off the router, creating a backup, and reattaching it to the router but now Shareport says that the connection to my mass storage device has failed. This is a popup window and one that I have never seen. Then it cycles to another message (onscreen) with a red x, and then to one with a yellow triangle that says no USB devices were found. The router logs say otherwise since it states that the silex driver has found the drive. I think I'm officially hosed. If I reconnect the drive to my computer everything looks fine. I did change the drive from a primary partition to a logical partition and when it would not connect, I changed it back to a primary partition yet this did not work.

06/08
Edit: Performing a Computer reboot fixed the aforementioned problem. I can see and access my drive now but after leaving Shareport on all night and checking it this morning it had detached and would not reconnect.

 

[jason1722x]

I was hoping this would fix the problem I was having with UPnP port forwarding and Windows Home Server.  It did not.  WHS will configure the proper port forwarding and claim success.  Router will forget settings within 5 minutes and website will no longer be accessible from the internet.  Back to manual port forwarding...

UPnP and WHS seemed to work fine prior to version 1.31.  Now I am stuck.

I have done a complete reset and have not used any configuration files to setup the router.  I have also tried unchecking UPnP, rebooting the router, and re-checking UPnP, rebooting the router.  Like I said the router allows the UPnP forwarding to take place but then quickly forgets the settings.

Any suggestions from D-Link?

I am using a three or four month old DIR-655 A4 with 1.32NA beta.

Thanks,
CWagz

Just curious if your getting blocked ports in your log for WHS and UPnP?

[Ragsion]

Can 1.32 beta 01 downgrade to ex.1.21 ?

[EddieZ]

nope

[CWagz]

Just curious if your getting blocked ports in your log for WHS and UPnP?

Yes - after using UPnP and WHS forwarding the ports it will work for a few minutes.  Then requests will show up in the log as being blocked.  For example port 443 will be blocked instead of directed to my server's IP address.

Only way to make it work is to manually forward the ports.
CWagz

[TLE]

If anyone is interested (Engineers that is) I have done a packet trace of the WHS UPnP port forwarding failure using WinPCap and Wireshark. Not sure where or who to send it too. I think it was Lycan who was asking for this. It's about 6MB in total.

Thanks

TLE

[Clancy]

TLE, would that same procedure be able to capture what is happening when writing to a USB drive? Do you know how to interpret it? I experience Delayed Write Failures and it brings down everything. I'd be interested to know just to satisfy my own curiosity. I realize that D-Link may never hunt down this ghost, or if it is even on the list, but I keep my fingers crossed. It's either that or find out how to make a headless server.

[Shadow_Fi]

D-Link, give us 3G option back!

[Tsumeone]

Shadow, that probably won't happen.

ATT/Verizon/TMobile/Sprint/ETC probably get irked that D-Link offered a way to share the 3G with more than 1 PC.  Sensing a potential dent in their RIDICULOUS profit margin, they probably whined screamed complained and moaned to D-Link until they removed the 3G function.

[lotacus]

That is probably what happened. More politics than "compatibility"

[Tsumeone]

I really like 1.32.  The only feature that doesn't work for me that I need is UPNP.  Ever since upgrading to 1.32, I've had the same problem the WHS person had, except with EVERY UPNP app I have.  uTorrent for example.  I have it set to automatically open a port with UPNP, but the D-Link firewall log keeps showing packets being blocked to the very port that should be open.  This worked in prior releases.

UPNP hopefully will be fixed in next release!