I just need to be able to to access my Windows PC from openSUSE 11.3. Does anyone know where to start???
Thanks
I wrote an article you might find useful. I am intending on doing an update for openSUSE 11.3 and for other things that have since been determined, but none the less, you may find this helpful to you.
Samba SMB file sharing in openSUSE 11.2
Thank You,
This might be useful: HowTo Setup Windows 7 for Network Sharing with Samba and openSUSE That should fix the windows 7 side of things.
Of course, you need Samba to work in openSUSE and if you have trouble with jdmcdaniel3’s tutorial while it is under revision, this might be useful: HowTo set up Samba on a Small Office or Home LAN (openSUSE Versions 11.x)
I enter the only user names and passwords I know in both my Windows PC and newly established Linux box openSUSE 11.3. Can someone please explain what the deal is with the passwords when trying to access the other computer.
The more I use Linux the more I like it and now I find openSUSE is a very good choice. With a little help from the community, before too long there could be another fully converted Linux user free from the chains of corporate MS!
Thanks!
On Mon August 16 2010 04:06 pm, ozzy24 wrote:
>
> I enter the only user names and passwords I know in both my Windows PC
> and newly established Linux box openSUSE 11.3. Can someone please
> explain what the deal is with the passwords when trying to access the
> other computer.
>
> The more I use Linux the more I like it and now I find openSUSE is a
> very good choice. With a little help from the community, before too long
> there could be another fully converted Linux user free from the chains
> of corporate MS!
>
> Thanks!
>
>
ozzy24;
First, you need to configure Samba. I would suggest you follow this HowTo:
http://opensuse.swerdna.org/suselanprimer.html
Be sure to create Samba users with:
su
smbpasswd -a <username>
The username above must be a valid Linux user, but the password need not be
their login password. If you have Windows7 machines there is some
adjustments to Windows you need to make. See:
http://opensuse.swerdna.org/susesambawin7.html
This should get you going. Post back if you run into more problems.
P. V.
“We’re all in this together, I’m pulling for you.” Red Green
Sorry for the multiple posts guys. I didn’t get any email notifications as to any replies. If an admin sees this, you might delete it. Thanks.
At a rough guess I would say that it depends how you set up the file sharing on the vista pc.
You need to allow all users access rights in vista.
I’ve run into this even when no username and password were required on windows shares. I was able to just put in any username/password and make it work.
Microsoft followed Linux to a degree when implementing vista by making the access to shares more secure. In windows 7 they made it even more secure. They have introduced global permissions (just like Samba), folder permissions based on local access permissions (just like Linux) and folder access permissions based on network permissions (just like Samba).
So the access difficulties you are having are designed into the vista and windows 7 networking. There are three areas in vista and windows 7 where you need to adjust permissions in order to avoid and/or conquer the windows password issues.
One is the Network and Sharing center → Advanced Sharing Settings
Another is Folder Security
The third is Folder Sharing Permissions
(something like that)
The full rigmarole is laid out here:
On Wed August 18 2010 12:06 am, rodhuffaker wrote:
>
> I’ve run into this even when no username and password were required on
> windows shares. I was able to just put in any username/password and
> make it work.
>
>
You can use guest with a blank password. However Win7 generally requires a
valid Win7 user and their password.
P. V.
“We’re all in this together, I’m pulling for you.” Red Green
@ozzy24, I’ll roll the threads together, please stay in the combined thread
venzkep,
I followed the tutorial down to “Setting up the Samba Client” and now I get the message “the file or folder smb://workgroup/ does not exsist”. I’m going to the kickoff > computer > network > samba shares > workgroup and after that last click is when I get the message. Whereas before I could make it all the way to the actual Windows PC and see my 3 hdd’s but never was able to access those drives due to the authorization dialog and I did add a user using smbpasswd.
venzkep,
I followed the tutorial down to “Setting up the Samba Client” and now I get the message “the file or folder smb://workgroup/ does not exsist”. I’m going to the kickoff > computer > network > samba shares > workgroup and after that last click is when I get the message. Whereas before I could make it all the way to the actual Windows PC and see my 3 hdd’s but never was able to access those drives due to the authorization dialog and I did add a user using smbpasswd.
So the location “smb://workgroup/” is a URL which can be opened using Dolphin. the name “workgroup” is the name you specified for your workgroup name in samba under [global] as in “workgroup = workgroup”. If this statement is missing or workgroup is not the name you picked then this will not work. Further, your Firewall settings must be correct for this to work. I don’t wish to confuse you with yet another tutorial, but I do have one and since this is not working for you yet, I would look at it as well.
Samba SMB file sharing in openSUSE 11.2
Thank You,
On Wed August 18 2010 04:36 pm, ozzy24 wrote:
>
> venzkep,
> I followed the tutorial down to “Setting up the Samba Client” and now I
> get the message “the file or folder smb://workgroup/ does not exsist”.
> I’m going to the kickoff > computer > network > samba shares > workgroup
> and after that last click is when I get the message. Whereas before I
> could make it all the way to the actual Windows PC and see my 3 hdd’s
> but never was able to access those drives due to the authorization
> dialog and I did add a user using smbpasswd.
>
>
ozzy24;
- Can you please post the contents of /etc/samba/smb.conf?
- What flavor of Windows is on the other machine (XP, VISTA, WIN7, or…)?
- Is the Windows workgroup the same as the name of the workgroup in your
smb.conf. - What happens if you enter smb://<netbios name of Windows machine>/ in the
browser. - Make sure nmb and smb are both started.
ps -A|grep [s,n]mbd
- Make sure you have allowed both the Samba server and Netbios server in the
firewall.
–
P. V.
“We’re all in this together, I’m pulling for you.” Red Green
venzkep,
- I would have put it in a “code box” like you got but I don’t know how.
- Vista
- Workgroups are the same but I’ll double check for typos
- It goes nowhere
- What does this mean?
linux-fgyr:/home/adam # ps -A|grep [s,n]mbd
2506 ? 00:00:00 smbd
2520 ? 00:00:00 smbd
3284 ? 00:00:00 nmbd
6358 ? 00:00:00 smbd
smb.conf is the main Samba configuration file. You find a full commented
version at /usr/share/doc/packages/samba/examples/smb.conf.SUSE if the
samba-doc package is installed.
Date: 2010-07-05
[global]
workgroup = WORKGROUP
passdb backend = tdbsam
printing = cups
printcap name = cups
printcap cache time = 750
cups options = raw
map to guest = Bad User
include = /etc/samba/dhcp.conf
logon path = \%L\profiles.msprofile
logon home = \%L%U.9xprofile
logon drive = P:
usershare allow guests = Yes
add machine script = /usr/sbin/useradd -c Machine -d /var/lib/nobody -s /bin/false %m$
domain logons = Yes
domain master = Yes
local master = Yes
netbios name = Adam-PC
os level = 65
preferred master = Yes
security = user
wins server =
wins support = No
[homes]
comment = Home Directories
valid users = %S, %D%w%S
browseable = No
read only = No
inherit acls = Yes
[profiles]
comment = Network Profiles Service
path = %H
read only = No
store dos attributes = Yes
create mask = 0600
directory mask = 0700
[users]
comment = All users
path = /home
read only = No
inherit acls = Yes
veto files = /aquota.user/groups/shares/
[groups]
comment = All groups
path = /home/groups
read only = No
inherit acls = Yes
[printers]
comment = All Printers
path = /var/tmp
printable = Yes
create mask = 0600
browseable = No
[print$]
comment = Printer Drivers
path = /var/lib/samba/drivers
write list = @ntadmin root
force group = ntadmin
create mask = 0664
directory mask = 0775
[netlogon]
comment = Network Logon Service
path = /var/lib/samba/netlogon
write list = root
ozzy24 says:
- I would have put it in a “code box” like you got but I don’t know how.
- Vista
- Workgroups are the same but I’ll double check for typos
- It goes nowhere
- What does this mean?
-
To place a portion of text, such as your smb.conf file, copy and paste into your message, just as you did, but then highlight (select) only this text and press the pound (#) editor option, which creates a code block.
-
You have “workgroup = WORKGROUP” set. I am not sure but you may need to use smb://WINDOWSNT/ since you have it all capitals. I don’t see anything wrong with this un-inventive name, but make sure it is the same on all machines.
-
Now if you read my Samba example, one of the things you must do is to start the required services in YaST / System / System Services (Runlevel). You have got to read this information through as it is the details that kill you.
Thank You,
On Thu August 19 2010 11:36 am, ozzy24 wrote:
>
> venzkep,
> 1. I would have put it in a “code box” like you got but I don’t know
> how.
> 2. Vista
> 3. Workgroups are the same but I’ll double check for typos
> 4. It goes nowhere
> 5. What does this mean?
> linux-fgyr:/home/adam # ps -A|grep [s,n]mbd
> 2506 ? 00:00:00 smbd
> 2520 ? 00:00:00 smbd
> 3284 ? 00:00:00 nmbd
> 6358 ? 00:00:00 smbd
>
>
> # smb.conf is the main Samba configuration file. You find a full
> commented
> # version at /usr/share/doc/packages/samba/examples/smb.conf.SUSE if
> the
> # samba-doc package is installed.
> # Date: 2010-07-05
> [global]
> workgroup = WORKGROUP
> passdb backend = tdbsam
> printing = cups
> printcap name = cups
> printcap cache time = 750
> cups options = raw
> map to guest = Bad User
> include = /etc/samba/dhcp.conf
> logon path = \%L\profiles.msprofile
> logon home = \%L%U.9xprofile
> logon drive = P:
> usershare allow guests = Yes
> add machine script = /usr/sbin/useradd -c Machine -d /var/lib/nobody
> -s /bin/false %m$
> domain logons = Yes
> domain master = Yes
> local master = Yes
> netbios name = Adam-PC
> os level = 65
> preferred master = Yes
> security = user
> wins server =
> wins support = No
<snip>
ozzy24;
You have Samba set up as a domain controler. Is this what you intend?
A) Have you joined the Vista machine to the domain?
B) Have you joined the PDC to its own domain?
su
net rpc join PDC -U root%<rootpasswd>
I would suggest you first set up a simple workgroup model using Swerdna’s
Howto. Once you get that going you can setup a domain if you really need to.
With only one client, IMHO a domain is a bit of overkill.
–
P. V.
“We’re all in this together, I’m pulling for you.” Red Green
On Thu August 19 2010 05:39 pm, PV wrote:
> On Thu August 19 2010 11:36 am, ozzy24 wrote:
>
>>
>> venzkep,
>> 1. I would have put it in a “code box” like you got but I don’t know
>> how.
>> 2. Vista
>> 3. Workgroups are the same but I’ll double check for typos
>> 4. It goes nowhere
>> 5. What does this mean?
>> linux-fgyr:/home/adam # ps -A|grep [s,n]mbd
>> 2506 ? 00:00:00 smbd
>> 2520 ? 00:00:00 smbd
>> 3284 ? 00:00:00 nmbd
>> 6358 ? 00:00:00 smbd
>>
>>
>> # smb.conf is the main Samba configuration file. You find a full
>> commented
>> # version at /usr/share/doc/packages/samba/examples/smb.conf.SUSE if
>> the
>> # samba-doc package is installed.
>> # Date: 2010-07-05
>> [global]
>> workgroup = WORKGROUP
>> passdb backend = tdbsam
>> printing = cups
>> printcap name = cups
>> printcap cache time = 750
>> cups options = raw
>> map to guest = Bad User
>> include = /etc/samba/dhcp.conf
>> logon path = \%L\profiles.msprofile
>> logon home = \%L%U.9xprofile
>> logon drive = P:
>> usershare allow guests = Yes
>> add machine script = /usr/sbin/useradd -c Machine -d /var/lib/nobody
>> -s /bin/false %m$
>> domain logons = Yes
>> domain master = Yes
>> local master = Yes
>> netbios name = Adam-PC
>> os level = 65
>> preferred master = Yes
>> security = user
>> wins server =
>> wins support = No
> <snip>
> ozzy24;
>
> You have Samba set up as a domain controler. Is this what you intend?
> A) Have you joined the Vista machine to the domain?
> B) Have you joined the PDC to its own domain?
>
> su
> net rpc join PDC -U root%<rootpasswd>
>
I would suggest you first set up a simple workgroup model using Swerdna’s
Howto. Once you get that going you can setup a domain if you really need
to.
With only one client, IMHO a domain is a bit of overkill.
In addition to the above, even if setting up a PDC you should set the name
resolve parameter in your smb.conf. The default order has broadcast last, it
first tries lmhosts, then hosts, thirdly wins and finally bcast. Unless you
have set up the lmhosts file name resolution will fail long before it tries
bcast. Add this to your smb.conf:
name resolve order = bcast lmhosts host wins
Alternatively set up a wins server and point your VISTA to the wins server
wins support = yes
name resolve order = wins bcast
Broadcast works well, so unless your machines are on different subnets just
let it use broadcasts . In any event, domain or workgroup model you need to
set the name resolve order.
P. V.
“We’re all in this together, I’m pulling for you.” Red Green
Well, I’ll keep at it and thanks so far.
On Thu August 19 2010 09:36 pm, ozzy24 wrote:
>
> Well, I’ll keep at it and thanks so far.
>
>
ozzy24;
Keep us posted on your progress. If you need to post back be sure to post the
current contents of your /etc/samba/smb.conf if it has changed.
P. V.
“We’re all in this together, I’m pulling for you.” Red Green