I think so although I’m still not really sure what I’m doing when I create a share. Have fun on your trip while I enjoy Mardi Gras in New Orleans. I’ll keep studying the tutorials and see if I can’t get some deeper understanding of LAN Linux/Windows principles.
I’m back – much refreshed:
OK after Pic F and then click apply and OK in the final instance of Pic B I do not get Pic G. Ever.
I can only add that I get the flawed behaviour you describe if I forget the tick in Pic E, or take it out at the wrong time. It’s possible my instructions were ambiguous. I’ve re-written them. Try it again.
I tried it again this morning in Dolphin and Konqueror and still am getting same results.
Also, in Konqueror>Network Folders>Samba Shares>MYBROSCOMPUTER>mybroscomputer it still is asking for “please enter authentication information for mybroscomputer”. I enter my smb user name and password and the same screen keeps popping back up indicating that is not recognizing my smb user name and password. Am I doing the correct thing at this step?
Some additional and current info:
# pdbedit -L
dwight:1000:Dwight Paige
ben:1002:Ben Paige
# rcSuSEfirewall2 stop
Shutting down the Firewall done
# rcnmb restart && rcsmb restart
Shutting down Samba NMB daemon done
Starting Samba NMB daemon done
Shutting down Samba SMB daemon done
Starting Samba SMB daemon
and current ‘/etc/samba/smb.conf’:
# 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: 2009-01-08
[global]
workgroup = MYBROSCOMPUTER
netbios name = mybroscomputer
name resolve order = bcast host lmhosts wins
server string = ""
printing = cups
printcap name = cups
load printers = yes
printcap cache time = 750
cups options = raw
use client driver = yes
map to guest = Bad User
local master = yes
preferred master = yes
os level = 65
usershare allow guests = Yes
usershare max shares = 100
usershare owner only = False
[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
Here’s some more:
# ping 192.168.0.xxx
PING 192.168.0.102 (192.168.0.102) 56(84) bytes of data.
64 bytes from 192.168.0.102: icmp_seq=1 ttl=128 time=0.384 ms
64 bytes from 192.168.0.102: icmp_seq=2 ttl=128 time=0.351 ms
64 bytes from 192.168.0.102: icmp_seq=3 ttl=128 time=0.351 ms
64 bytes from 192.168.0.102: icmp_seq=4 ttl=128 time=0.360 ms
64 bytes from 192.168.0.102: icmp_seq=5 ttl=128 time=0.387 ms
64 bytes from 192.168.0.102: icmp_seq=6 ttl=128 time=0.353 ms
64 bytes from 192.168.0.102: icmp_seq=7 ttl=128 time=0.386 ms
64 bytes from 192.168.0.102: icmp_seq=8 ttl=128 time=0.351 ms
64 bytes from 192.168.0.102: icmp_seq=9 ttl=128 time=0.357 ms
64 bytes from 192.168.0.102: icmp_seq=10 ttl=128 time=0.386 ms
64 bytes from 192.168.0.102: icmp_seq=11 ttl=128 time=0.377 ms
64 bytes from 192.168.0.102: icmp_seq=12 ttl=128 time=1.18 ms
64 bytes from 192.168.0.102: icmp_seq=13 ttl=128 time=0.375 ms
64 bytes from 192.168.0.102: icmp_seq=14 ttl=128 time=0.376 ms
^C
--- 192.168.0.102 ping statistics ---
14 packets transmitted, 14 received, 0% packet loss, time 13002ms
rtt min/avg/max/mdev = 0.351/0.427/1.188/0.212 ms
# smbclient -L 192.168.0.xxx -U dwight
Enter dwight's password:
session setup failed: NT_STATUS_LOGON_FAILURE
Where 192.168.0.xxx is the IP address of mybroscomputer.
On Sun February 22 2009 09:56 am, dwightpaige79 wrote:
>
> Some additional and current info:
>
>
> Code:
> --------------------
> # pdbedit -L
> dwight:1000:Dwight Paige
> ben:1002:Ben Paige
> # rcSuSEfirewall2 stop
> Shutting down the Firewall
> done
> # rcnmb restart && rcsmb restart
> Shutting down Samba NMB daemon
> done
> Starting Samba NMB daemon
> done
> Shutting down Samba SMB daemon
> done Starting Samba SMB daemon
>
> --------------------
>
>
> and current ‘/etc/samba/smb.conf’:
>
>
> Code:
> --------------------
> # 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: 2009-01-08
> [global]
> workgroup = MYBROSCOMPUTER
> netbios name = mybroscomputer
> name resolve order = bcast host lmhosts wins
<snip>
The workgroup and netbios name should be different. All the computers should
have the same workgroup name, and each computer should have a unique netbios
name. On XP, right click on mycomputer, choose properies, then the computer
name tag. Here you will see the workgroup used by XP, make yours above the
same. You will also see the netbios name (Full computer name). Choose
something different for your netbios name.
–
P. V.
“We’re all in this together, I’m pulling for you.” Red Green
Regarding the smbpasswd database. That’s for access to the Suse machine. To access the XP machine you only send a username that exists as a login name on the xp machine. But I can’t manage to simulate on my LAN the situation where it asks for authentication.
I’ve looked over your various posts and can’t find anything wrong. At this point I would turn off all firewalls so they didn’t restart at boot, check the Samba packages samba & samba-client same release number, restart all the electrical devices (modems, routers, computers), check same workgroup name on both computers, check permissions on windows shares were “allow users to modify files”.
An afterthought: you don’t access the $shares, you make a folder e.g. on brother’s desktop and share that.*
Then part of the problem is that I’m doing it wrong. I’ll get on my brother’s computer and see if I can create a share there. I do have an account on his computer. Will also check same workgroup name on both computers, check permissions on windows shares were “allow users to modify files”.
Here’s what I don’t understand. My openSUSE box is visible on my brothers Windows XP box in “My Network Connections”, My brothers Windows XP box is visible on my openSUSE box in Dolphin>Network>Samba Shares>WORKGROUP. Exactly how do I connect from my openSUSE box to my brothers Windows XP box to share files and very importantly use his printer?
FWIW I just set up the printer on mybrotherscomputer using “Setting up a Linux client to print using LPD protocol (alternative to Samba)” from:
Printer Sharing: Windows Print Server for Suse/openSUSE Linux Clients [Samba and LPD]
so my problem with file sharing is probably brain lock or something preventing me from understanding how to use Samba/smb-client.
# smbclient -L 192.168.0.xxx -U dwight
Enter dwight's password:
session setup failed: NT_STATUS_LOGON_FAILURE
smbclient -L \\192.168.0.x\ -U name
That works for me, and I can use any name even fictitious names and then any password, even fictitious passwords. In other words, for me I don’t need a username or a password to get the listing.
If I don’t put in the four \\ and then the two \, I get this error message:
Not enough '' characters in service
But I don’t get
session setup failed: NT_STATUS_LOGON_FAILURE
Create a folder on your desktop in windows, call it abcde (whatever). Right-click it and select Properties –> Sharing. If it says danger and so on but share it anyway, choose to share it anyway. On the other hand it might just share it straight away with no questions. Get to the sharinbg screen. Click “Share this folder on the network” and click “Allow net users to change files”. Reboot windows.
Return to Susebox. Open Nautilus (or you can use Konqueror if you prefer). Enter the address smb://. Click icon for the workgroup, then icon for the windows computer, then icon for abcde. Don’t click any icons starting with $, they’re not accessible.
It still asks for authentication which still doesn’t work. Using Konqueror by the way. I’m going to remove some packages [32 bit] and see what that does. Is this a possible permissions issue on my openSUSE box? Or a possible permissions issue on ‘mybrotherscomputer’?
Ok, that is working differently here. From my openSUSE box to Brother’s Windows XP box:
> smbclient -L \\\\192.168.0.x\\ -U mybrotherscomputer
Enter mybrotherscomputer password:
Anonymous login successful
Domain=[MYBROTHERSWORKGROUP] OS=[Windows 5.1] Server=[Windows 2000 LAN Manager]
Sharename Type Comment
--------- ---- -------
Error returning browse list: NT_STATUS_ACCESS_DENIED
session request to 192.168.0.x failed (Called name not present)
session request to 192 failed (Called name not present)
Anonymous login successful
Domain=[MYBROTHERSWORKGROUP] OS=[Windows 5.1] Server=[Windows 2000 LAN Manager]
Server Comment
--------- -------
Workgroup Master
--------- -------
On my computer it only works this way, It does not work using my own account on the Windows computer or using other or fictitious usernames. It seems something needs to change regarding permissions??? I just don’t understand [yet] where or how…
Also why is ‘mybrotherscomputer’ listed as ‘Windows 2000 LAN Manager’ instead of Windows XP? Don’t know if that even matters?
At any rate progress has been made. All be it in halting, slow steps. And I am understanding more with exception of permissions.
FWIW: My brother has ‘mybrotherscomputer’ account set to no password. That is what results in the results posted in
here. ie. entering his username and hitting enter for ‘Enter mybrotherscomputer password:’.
So far I haven’t removed any packages. All are 64 bit:
# zypper se samba*
Loading repository data...
Reading installed packages...
S | Name | Summary | Type
--+---------------------+-------------------------------------------------------------------+-----------
i | samba | A SMB/CIFS File, Print, and Authentication Server | package
| samba | A SMB/CIFS File, Print, and Authentication Server | srcpackage
i | samba-32bit | A SMB/CIFS File, Print, and Authentication Server | package
i | samba-client | Samba Client Utilities | package
i | samba-client-32bit | Samba Client Utilities | package
i | samba-devel | Libraries and Header Files to Develop Programs with Samba Support | package
i | samba-doc | Samba Documentation | package
i | samba-krb-printing | Wrapper binary for kerberized printing | package
i | samba-vscan | On-Access Virus Scanning with Samba | package
i | samba-winbind | Winbind Daemon and Tool | package
i | samba-winbind-32bit | Winbind Daemon and Tool | package
# zypper if samba-32bit samba-client-32bit samba-winbind-32bit
Loading repository data...
Reading installed packages...
Information for package samba-32bit:
Repository: @System
Name: samba-32bit
Version: 3.2.6-0.3.1
Arch: x86_64
Vendor: openSUSE
Installed: Yes
Status: up-to-date
Installed Size: 1.4 M
Summary: A SMB/CIFS File, Print, and Authentication Server
Description:
Samba is a suite of programs that allows SMB/CIFS clients to use the
Unix file space, printers, and authentication subsystem.
The package named samba contains all programs that are needed to act as
a server. The binaries expect the configuration file to be found in
/etc/samba/smb.conf
For a more detailed description of Samba, check the samba-doc package
or the Samba.org Web page at http://www.Samba.org/
Please check http://en.openSUSE.org/Samba for general information on
Samba as part of SUSE Linux Enterprise or openSUSE products, links to
binary packages of the most current Samba version, and a bug reporting
how to.
Information for package samba-client-32bit:
Repository: @System
Name: samba-client-32bit
Version: 3.2.6-0.3.1
Arch: x86_64
Vendor: openSUSE
Installed: Yes
Status: up-to-date
Installed Size: 1.9 M
Summary: Samba Client Utilities
Description:
Samba is a suite of programs that allows SMB/CIFS clients to use the
Unix file space, printers, and authentication subsystem.
The package named samba-client contains all programs that are needed to
act as a Samba client. The binaries expect the configuration file to
be found in /etc/samba/smb.conf
For a more detailed description of Samba, check the samba-doc package
or the Samba.org Web page at http://www.Samba.org/
Please check http://en.openSUSE.org/Samba for general information on
Samba as part of SUSE Linux Enterprise or openSUSE products, links to
binary packages of the most current Samba version, and a bug reporting
how to.
Information for package samba-winbind-32bit:
Repository: @System
Name: samba-winbind-32bit
Version: 3.2.6-0.3.1
Arch: x86_64
Vendor: openSUSE
Installed: Yes
Status: up-to-date
Installed Size: 68.0 K
Summary: Winbind Daemon and Tool
Description:
This is the winbind-daemon and the wbinfo-tool.
I honestly don’t know if I have to many or redundant packages installed. I’m thinking to post to either the ‘Applications’ or ‘Hardware>64-bit’ forum and seeing if some who knows 64 bit better can advise.
I checked on mine – same thing – so forget it.
FWIW: My brother has ‘mybrotherscomputer’ account set to no password. That is what results in the results posted in here. ie. entering his username and hitting enter for ‘Enter mybrotherscomputer password:’.
I set up a similar thing and tested it. It doesn’t make my setup fail like yours.
I’m favouring some setting changed in xp’s networking or firewalls, but can’t think what. Thinking…
Well I’ve just found this quote on this link: http://www.informit.com/articles/article.aspx?p=349040
Blank Passwords. By default, Windows XP workstations that are not part of a domain prevent users with blank passwords from logging on over the network. This is especially helpful for preventing unauthorized access to home workstations connected to the Internet. All blank password access is restricted to local logons only.
Maybe that explains what’s happening to you. Perhaps put a password on your windows account ant then try to connect to a share that you’ve created in your territory on the xp box.
And another possibility. You need the xp box set for “simple file sharing”. It should be like that by default. Check in Control Panel → Folder Options → View Tab → scroll to: “Use simple file sharing (recommended)”. Make sure there is a tick beside it. Did it have the tick?
Yes, it was already ticked.
I do have my own user account on the Windows box and it is set up with a password. I can’t access it from the openSUSE box:
:~> smbclient -L \\\\192.168.0.x\\ -U it'sasecret
Enter it'sasecret password:
session setup failed: NT_STATUS_LOGON_FAILURE
:~> smbclient -L \\\\192.168.0.x\\ -U dwight
Enter dwight's password:
session setup failed: NT_STATUS_LOGON_FAILURE
I now have 2 user accounts on the windows box with unique and secure passwords. The above is what results when I try to login from the openSUSE box. It does seem to be an issue either on the windows side or with the router.
Also, how do I connect to a share on the windows box from the SUSE box? If I can’t even login? Don’t I first have to connect to the windows box then access the shares. And there are shared files. I just can’t get to them from the openSUSE box.