Windows 7 samba login problem

Anyway, thanks for your reply and it is appreciated any further suggestions. BTW, my samba server not as PDC in my network, it just joins to our windows domain and uses windows server for authentication. Office Office Exchange Server.

Not an IT pro? Windows Client. Sign in. United States English. Ask a question. Quick access. Search related threads. Remove From My Forums. The shares are owned by "cameron" and group "www-data". They have the following permissions: rwxrwxr-- but when I attempt to create a file I get a "You need permission to perform this action" dialog.

The reason for the map file was because the case was different and I was not sure if Linux is case-sensitive to usernames. Just removed the read-only lines and it appears to work now. I'm a little confused as I thought that adding my user to the write list would override this setting. BjAnderson BjAnderson 21 1 1 bronze badge. Then restart samba and you should be able to login.

I think the reason it's not in the above config is because it's the default for Samba hence why swat has left it out. It's the same with encrypt passwords. Both are defaults. Do I need to logout and then back in again for Windows to attempt to authenticate?

Krzysztof Tomaszewski Krzysztof Tomaszewski 1 1 bronze badge. Sign up or log in Sign up using Google. Sign up using Facebook.

Sign up using Email and Password. Post as a guest Name. Email Required, but never shown. The Overflow Blog. Stack Gives Back Safety in numbers: crowdsourcing data on nefarious IP addresses. Featured on Meta. New post summary designs on greatest hits now, everywhere else eventually. The situation you are facing is like this: You have successfully used Samba sharing in Linux to access Windows XP shares on your local network.

You could open the shares and write to them. Since migrating to Windows 7, you are seeing a weird problem. Your Samba sharing no longer works. In Nautilus, you get a very generic error that says: failed to access share.

You are not a clueless user and you know all about permissions, firewall and all that. To make the situation worse, the sharing might work on some Windows 7 boxes, but not on others. So you feel worried and think what to do next. You hit the Internet and get advice on how to add wins to your nsswitch. Not necessarily what you want to do. I've got a better idea. Read on.

This happened to me. I have two new Windows 7 boxes in my LAN, one the high-end gaming computer I've written about last year, and another, almost identical machine recently added to the arsenal. So you might assume, two identical machines, the same operating system, what could go wrong? The answer is, something. XP access was fine, Windows 7 is not, for some reason - on only one machine.

What do you do next? The answer is - you do not blindly follow advice written in forums, because every single problem is oh-so-slightly different than yours, so you end up doing things that will change your system beyond repair and confuse you even more. It is important not to be tempted to try to resolve things quickly but smartly, and figure out what you should do. There's no reason for you to play with the Samba configuration.

Because the Samba configuration is relevant for your own shares, not the ones you are trying to access on another computer. Besides, it worked in the past. On the network level, you are just fine.