• February 23, 2025, 12:45:04 PM
  • Welcome, Guest
Please login or register.

Login with username, password and session length
Advanced search  

News:

This Forum Beta is ONLY for registered owners of D-Link products in the USA for which we have created boards at this time.

Pages: 1 [2]

Author Topic: Firmware 1.04 (AND 1.05) causes Desktop Client Reboots  (Read 14028 times)

sowens01

  • Guest
Re: Firmware 1.04 (AND 1.05) causes Desktop Client Reboots
« Reply #15 on: August 06, 2008, 08:51:25 AM »

I removed the drive from the DNS-323 to access it on a linux box as well as through the IFS Drives interface app from within Win XP Pro.  I used Ext2IFS and an external sata2usb drive enclosure.
Logged

fordem

  • Level 10 Member
  • *****
  • Posts: 2168
Re: Firmware 1.04 (AND 1.05) causes Desktop Client Reboots
« Reply #16 on: August 06, 2008, 09:42:20 AM »

I removed the drive from the DNS-323 to access it on a linux box as well as through the IFS Drives interface app from within Win XP Pro.  I used Ext2IFS and an external sata2usb drive enclosure.

I think you're missing the point - the crashing of the OS appears to be related to an incompatability of some sort between - I suspect - the version of Samba being used in fw1.04/1.05 and some as yet unidentified piece of software running on the Windows system.

It has nothing to do with what is on the drives or the drives themselves - so removing the drives and using them with an alternative method of connection does nothing other than provide a way to get access to the data - it is of no diagnostic value.

Since the crash only occurs with some of the systems that the original poster uses, I think it's fairly safe to say the problem is not a pure Samba/Windows incompatibility, but more one of the OS and the drivers and/or application loaded.
Logged
RAID1 is for disk redundancy - NOT data backup - don't confuse the two.

sowens01

  • Guest
Re: Firmware 1.04 (AND 1.05) causes Desktop Client Reboots
« Reply #17 on: August 06, 2008, 09:52:43 AM »

I can accept that, it would not be the first time (or the last) the Microsoft OS has caused problems.
I did put the drive back in the DNS-323 and connected it to the linux box, and had no problems.
Logged
Pages: 1 [2]