DSM-G600, DNS-3xx and NSA-220 Hack Forum

You have three options:

1. Leave the security setting to "SHARE" and provide your credentials in advance before trying to connect. In the connection window of Windows there should be an option "Connect as different user" or something like this. I have a german Windows system so I don't know what the english version looks like. Anyway the link is right below the checkbox "Reconnect at logon".

2. Backup your modified /etc/samba/smb.conf to somewhere safe and use a script to restore it after system start and restart the samba daemon afterwards.

3. Use your own samba server (there is one included in fonz packages) and configure this one to your needs. Using this option you lose the possibility to configure samba via the web interface of the DNS.

A couple of solutions -- the first one works for sure. Make a batch file (open notepad and paste this code in, save it as a .bat file).

net use X: \\servername(D-LINK)\sharename /USER:username password

where
X: = the local drive letter you want associated with the network share (optional)
servername = the name of the DNS-323
share = the name of the share folder
username = the username required to access that folder
password = the password (if any)

Then, either run that .bat file every time you want to get to the drive, or drag it to your startup folder in the start menu and it will run every time windows starts. I use the startup method, personally. The next fix only works if you have XP Professional (as opposed to XP Home). This one requires that you manually type in your login and password every time you want to access it. It will use that same login prompt that you're getting, but the username will not be greyed out.

Open any folder (my documents, for example). Click Tools>Folder Options. In the "View" tab, scroll down to the very bottom of the list and uncheck "Use simple file sharing". That should work... It's been a while since I've used that method, but I believe it will work. The .bat file is a much better option, IMO!

I don't understand the problem then... Make it so Volume_1 requires a valid username and password, and delete all the other shares. Use the net use command to gain access via username/password. Then run the NTBACKUP.

Did I miss something?

Connect as different user I do not have this!

I have an problem now with scheduled tasks and mapped drive, the ntbackup does not see the mapped drive, so I must use UNC like \\servername\backup folder. Is there any way to disable the guest logon windows and use user permanently. Using windows server 2003, the issue is like this http://forums.techarena.in/windows-serv … /21209.htm

I can use UNC with the NAS. Of course I need a valid user to access the box.

The Windows task scheduler runs as a system account and therefore has no access to your NAS.

So what shall I do now, is create on my domain controller the same user/password as in the nas, give it the backup operator privilegies and permissions to backup the folders and then run the schedule task using that account? Shall test tomorrow and report!

blahsome wrote:

I simply mirror the same user/password settings in my Windows boxes and on the DNS-323. This way the DNS-323 has never prompted me for a user name or password because Windows has already passed it the current user credentials. This scheme works on both XP (SP3) and Vista (SP1).

Am I missing something here?

No, you're missing nothing. I do the same here and it is quite convenient. When I want to change my password in Windows I can change it on the NAS as well using the same dialog in Windows. I just need to select the NAS box as "log into". There is no need to log into the NAS with ssh and change the sambe password there.
Only for accounts not on the NAS I am prompted for credentials. I use the "security = user" setting.

frogman wrote:

I created the sam account on my DC and scheduled the backup using that account and it works now fine.

Thanks everyone!

That's good to hear.

The problem with services needing access to network resources is still quite common. Windows services usually run as the "system account" and that doesn't have the privileges to access other servers. That's what "run service as" is for.

I use the samba package from fonz packages. This is much newer than the one in vanilla CH3SNAS. The biggest advantage for me is that I can configure samba as I like it and I'm not hampered by the NAS web interface and its basic set of features.

I'm not sure if I understand your question.

Samba is not part of the standard fonz 0.5 package. It is an extra package which you can find here.
It uses /ffp/etc/samba/smb.conf as configuration file.