How to get Snap Server to recognise Windows password?

[dgoodrich]

I got my 2000 working, thanks to help on this board, but I am having trouble with setting up permissions. I have a little experience with NT server, so I'm not a complete newb.

I have created a share, and it is visible in "My Network Places" (XP Home). I have created a user that shares my Windows username and password, and have made that user part of the Admin group. I have also created a username and password for my wife, and a group called "musiclisteners," and made her a member of that group. I set the share access permissions for the music share to allow full access for the Administrator group, and read-only access for the "musiclisteners" group.

The problem I am having is that the server doesn't authenticate the new username and password I created for myself. The "active users" screen shows this username under the HTTP network type but under the Microsoft network type, it shows a username that no longer exists (but that existed when I first set up the server). I may have confused it by changing my Windows username while I was still logged-in to the Snap. So now, it is still using the old username for Windows networking, and that user is a guest.

How do I get it to use my new Windows username and password for Windows networking on the Snap?

Do I need to somehow clear the old username out before it will use the new one? If so, how do I do that?

Thanks,
Dave

[dgoodrich]

Well, I got it to work, but only with a workaround.

In the original post, I indicated that the old user showing up on the server's active user list didn't exist anymore. Actually, thats not quite true, and that is the root of the problem I was having. I had changed the username in Windows, but is was actually still the same user account. For some reason, when I connected to the server through Windows networking, it was still passing the old user name to the server, instead of the new name I had changed it to. Since there was no matching name on the server, I was authenticated as a guest. I changed my Windows username back, and it authenticates properly.

So it seems that you can't change your windows username and just change the Snap username to match and expect it to work.

[blue68f100]

Permission can be tricky.
1st. MS networks use the name of the user (XP Display Name) as the login name & password.
2nd. I have found it easier to create share folders using windows explorer, then login as admin and set the permisions to the folder.

If you have mapped the drive to an old user you must delete it and create a new. Their is also an option on networks shares to "Login AS".

Note: eveyone must have read access to the shares root. Then restrict user access to the folders that are private. If you have 2 shares this is easy.

The help system on the snap is pretty good in explaining user access rights and how the tree structure works.

[dgoodrich]

1st. MS networks use the name of the user (XP Display Name) as the login name & password.


This is the strange thing. I changed the XP Display Name, but it still passed the old name to the Snap. I even tried adding a new XP user with the old name (Dave), but the Snap saw it as something like "Dave-2."

Oh well, its working now.

Thanks,

[blue68f100]

I fould it was better to reboot after making changes to permissions. This way it clears the cache and reloads current. This seams to be so with v3.4.803, Haven't noticed having to do it with v4.

[re3dyb0y]

Easiest way is to create a user on the snap with the same user and pass

For example to make file access easier, on my server, the administrator accont i use has the same password as my snap, and ive created a sam account, but ive recenetly added a password, so i need to check if i still get easy access

It is just usually the web admin that needs a manualloy adding user and password

If you had a network with a domain and therefore a server, you could use the AD and the snap can pulll users and passwords from there