Print

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

[jolley]

I think I've managed it now by using the reset button on the back of the unit. I notice that setting the NTP server to any valid NTP server produces a message which says it can't connect to the server - but it actually does because the time is updated.

I agree 1.08b08 worked better in my experience when changing settings.

[Rich012]

With ISP's blocking port 25 - Would it be possble to get a destination port Entry along with Auth type on the Email Alerts setup screen

[jaapf]

Running the 1.09B9 from the UK site.

Under windows XP the DNS323 is not found in the network until settings are reloaded and the unit is rebooted.

My Ubuntu server does find it right away. Looks like Windows network settings are lost by power down?

[gunrunnerjohn]

Guess maybe you shouldn't have been in a hurry to load that UK version.

[jamieburchell]

I still don't even know if this new v8 UK version is actually an official release and they haven't updated the filename, or what. Dlink don't usually publish beta firmwares on their product support download page. No stickies about the new firmware, nothing on "Latest technical alerts". No replies on here. I'm in the UK, it was put on the official support area so I downloaded and installed it.

[theonlybabyface]

Running the 1.09B9 from the UK site.

Under windows XP the DNS323 is not found in the network until settings are reloaded and the unit is rebooted.

My Ubuntu server does find it right away. Looks like Windows network settings are lost by power down?

Working great for me...

[gunrunnerjohn]

When you look in the archive, it's clearly labeled as a beta.

[jaapf]

This morning it came up by itself without reloading the settings. I did read about putting back defaults and dit try that. First time it was not succesfull, but now it looks ok. Keep fingers crossed.

@gunrunnerjohn: Yes beta, so what? First make a good, checked back up before using it. The only things to be lost then is time. And this is the betacode section right?

If nobody tests beta (and I am a small private programmer myself) no bugs are ever gonna be found and repaired. The same applies when people do test but don't report them

[jamieburchell]

When you look in the archive, it's clearly labeled as a beta.

Since when do dlink release beta firmware on their official support download page? Unless you look at the end of the filename nothing else indicates it's beta.

This page lists it just like the others... http://www.dlink.co.uk/cs/Satellite?c=TechSupport_C&childpagename=DLinkEurope-GB%2FDLTechProduct&cid=1197319419183&p=1197318962293&packedargs=OuickLinksParentID%3D1197319419183%26locale%3D1195806691854%26packedargs%3Df9ffeaf4e83ab6d0166b8cc93b23ebbc3d83540f46ceb58f26706558f9479c4ec3df1411a95e2d40b8161bf516969212f4b253493c501653965d4b39148b4c34&pagename=DLinkEurope-GB%2FDLWrapper

[gunrunnerjohn]

I was a bit surprised to see it on the standard download page, but the file name in the archive gives it away.  The release notes also mention beta.

It's interesting that 1.07b1 is represented as a beta in the title, but the 1.08b9 doesn't say beta on the page.

They must run a loose ship over there in the UK.

[jaapf]

I agree with you. Beta in the filename should be enough to warn for possible problems.

And they did add a changelist to the zip-file  which also tells it's beta.

[jamieburchell]

All download support pages ive ever seen clearly segregate beta from release and labour the point to prevent joe public who doesn't know what beta is from running in to problems. Nothing says the word beta until you download it. I'm not going to list a page of examples and I won't keep on saying it- it's not obvious enough.

[gunrunnerjohn]

I'm not really disagreeing with you here, it should be at least labeled as a beta on the link before you download it.

[SnapperNZ]

What happened to the sharing and security - I have a mac and it all worked before going to 1.08.  My existing shares seem to work, except I had a Time Machine backup going to one share, and that now asks for authentication when I try and connect using Time Machine.  I can connect normally to the share - so that would suggest perhaps the smb or sharing method has changed?

SMB has appeared as a share type - strangely, as it's not like there is an option to have any other type.

The users/groups option never worked for me using a mac anyway, now it seems to work, but I can't work out how and can no longer connect properly.  I tried using 'connect as' and I can't get any credentials working - I've tried server\username etc - no go.

Frustrating.  Might have to go back to 1.07, which is a shame as there look to be some nice new tweaks to 1.08.

[gunrunnerjohn]

The new firmware doesn't allow anonymous shares and password protected shares to coexist as they could in earlier versions.