Problem With Windows Network

OK, so managed to install samba (shouldn't that be in place in sucha large dist as SUSE..(?)
Want to acces a laptop runing WinXP over a wireless MS-network at home.
Followed this great tutorial:
http://www.swerdna.net.au/linhowtola....html#firewall
, and now I can see the winXp-laptop (=KATARINAS) but from there, I can't see the SUSE 10.3-box in the network.
(only after a looong time the XP-computer itself)

When browsing local network in SUSE-konqueror I get the message:
Kan inte hitta överliggande objekt slp:/ i trädet. Internt fel.
(Can't find overlying object slp:/ in the tree. Internal error)
I have stopped the firewalls in both machines and re-booted them several times.

What can be the problem?

Here is the list from kdesu kwrite /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: 2007-12-04
[global]
workgroup = MSHOME
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 = No
idmap gid = 10000-20000
idmap uid = 10000-20000
security = user
add machine script = /usr/sbin/useradd -c Machine -d /var/lib/nobody -s /bin/false %m$
domain logons = Yes
domain master = Yes
netbios name = KATARINAS
passdb backend = smbpasswd
local master = Yes
os level = 65
preferred master = Yes
[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


Frankly speeking, even if 90% of the obstacles are in the windowsXP-mess, shouldn't these things be a bit more intuitive in a dist like SUSE?
The tutorial shows some flaws in Yast and is it really impossible to probe a win-network and help the user in a better way here..
Have spent more than 4 hours now... :unsure:

Not a Samba expert like Swerdna but:

usershare allow guests = No[/b]

should be:

usershare allow guests = Yes

See his Samba share Howto:

Are the workgroups the same in both systems?
Have you run Network Setup Wizard and allowed file and printer sharing in XP?

Hi carlmb
Yes Samba can be a real hair puller.
Few comments:

• I make a link on my Desktop with address smb:/. That avoids the "slp:/" thingy, which is not for Samba.
• Samba is looking in the file lmhosts (located at /etc/samba/lmhosts) for a list of netbios names -vs- IP addresses. That file is empty so that's why it takes so long to find anything in the GUI network browser.
• You might have strayed into the area in Yast with the icon titled "Windows Domain Membership" and associated your workstation with a windows domain. I think you probably want a standard windows workgroup.

I suggest you change the [global] paragraph of the Samba configuration file back close to the default configuration. You can do that with the GUI text editor using copy/paste. Open smb.conf in the text editor with this console command:
kdesu kwrite /etc/samba/smb.conf
Answer root password question and then copy the suggested [global] para below over the existing [global] para. Save and exit and reboot to initialise Samba and cause it to exert influence as a "local master".

Copy over from this line:
[global] to and including this line
preferred master = Yes.
Here's the suggested replacement text:

[global]
workgroup = MSHOME
netbios name = KATARINAS
name resolve order = bcast host lmhosts wins
server string = ""
printing = cups
printcap name = cups
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[/b]

Hope that helps

Swerdna

is that difficult to suggest first:
diagnosis?
pretty simple
smbclient -L IP_address_of_samba_server

usershare allow guests = Yes[/b]

has nothing to do with the fact that shares are not visible

I can't see the SUSE 10.3-box in the network.[/b]

her shares should be visible all right:

[users]
comment = All users
path = /home
..............
..............
[printers]
...................
path = /var/tmp
................
[print$][/b]

setting
usershare allow guests = No
means that share is not accessible for guest, not that share is not visible
invisible share is another thing absolutely not related to ACL.

questions to ask:
is this the same subnet?
if not, configure WINS
is firewall (suse side) configured as needed?
can you ping suse from windows
can you connect to suse from windows command line

few ways of diagnosing your problem:
check smb.conf for errors run from terminal window:
#tesparm -v

test server:
#smbclient -L box_name/or IP address
who is master browser
#nmblookup -M -- -
or
#nmblookup -A IPaddress
if enter server address then and look for the line:
..__MSBROWSE__. <01> - <GROUP> H <ACTIVE>

hostname -f



while samba linux is a little different from smb windows client, from users point of view is no more difficult. Difference is that you "already" know about windows while still learning linux.

suse's samba config is so convoluted that directry editing smb.conf, lmhosts, hosts would be faster than playing with Yast by the way.

setting
usershare allow guests = No
means that share is not accessible for guest, not that share is not visible[/b]

You are correct, I did not pay attention to not being able to see the Linux box at all in the help request. I made a false assumption.

...
suse's samba config is so convoluted that directry editing smb.conf, lmhosts, hosts would be faster than playing with Yast by the way.
[/b]

Agree, the YaST module for Samba is getting worse as the versions are advancing. Not to mention the interaction with Kde> Personal settings>Internet and Network>Samba. That is why I appreciate the work Swerdna has done with his Howtos to help out those of us with not much network experience.

yup,
Swerdna's howto is very nice, very, very useful.

OK, thanks for all help so far.
Maybe I was very unclear about the network.
I started with creating the "home-network" in WinXp.
I named it MSHOME.
The Linx is connected to the Netgear router WGT624 v3 by a network cable whereas the laptop with XPprof is connecting wireless.
Both computers are working fine towards internet.
The laptop-XPcomputer I named KATARINAS, and beleive it or not, I also typed in the same name in the samba config panel under "identity"...
So I guess that the first mistake was to not understanding that the identity shown here in Samba should be the local linux-box.
(Or am I wrong...?)
I now typed in Linux-Soyo for indentity instead, hope it's right.
(These things are very abstract since the samba config panels look very alike the unlogical MS-panels, with it's very unclear meaning of all fields...All that would have been needed in my case was a simple "LOCAL-identity", or similar. The idea here should be to give a much better help than MS gives.)

The global part of smb.conf now looks like:
# 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: 2007-12-04
[global]
workgroup = MSHOME
netbios name = Linux-Soyo
name resolve order = bcast host lmhosts wins
server string = ""
printing = cups
printcap name = cups
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


OK now?

Command:
smbclient -L 192.168.1.2
gives:
Password:
Domain=[LINUX-SOYO] OS=[Unix] Server=[Samba 3.0.26a-3.5-1616-SUSE-SL10.3]

Sharename Type Comment
--------- ---- -------
profiles Disk Network Profiles Service
users Disk All users
groups Disk All groups
print$ Disk Printer Drivers
netlogon Disk Network Logon Service
IPC$ IPC IPC Service ("")
deskjet930c Printer HEWLETT-PACKARD DESKJET 930C
Domain=[LINUX-SOYO] OS=[Unix] Server=[Samba 3.0.26a-3.5-1616-SUSE-SL10.3]

Server Comment
--------- -------

Workgroup Master
--------- -------
MSHOME LINUX-SOYO


Is this OK?
For the XP-laptop:
smbclient -L 192.168.1.3
gives:
timeout connecting to 192.168.1.3:445
timeout connecting to 192.168.1.3:139
Error connecting to 192.168.1.3 (Operationen pågår redan)
Connection to 192.168.1.3 failed (Error NT_STATUS_ACCESS_DENIED)

So here is a problem connecting to XP-box.

Further:
After changing the identity of linux-box to linux-Soyo, this is the only name showing up under MSHOME when I browse smb:/
So, what I saw all the time was only the Linux-box :blush: ,and now with the correct name.
If i click once on "linux-Soyo" ther is 4 folders: groups, netlogon, profiles and users.
regardless which I try to browse, I get the same window:
Error Konqeror:
Timeout on server
Linux-soyo

If i do nothing, after a while I get "Kunde inte ansluta till värddator för smb://mshome/" , and the MSHOME icon dissapears.

Questions from broch:

questions to ask:
is this the same subnet?[/b]

I think so, IP SUBNET mask for both is : 255.255.255.0 according the router settings.

if not, configure WINS
Well, I tried, DHCP is activated in Xp, as well as the Netbios setting "standard":
"use NetBios setting from the DHCP-server"
Nothing else particular checked but standard, (I think)

is firewall (suse side) configured as needed?[/b]

Good question, but both firewals are inactive when i test.

can you ping suse from windows[/b]

Yes, and the also the router.
values for linux:
lowest: 2 ms, Highest: 21 ms average: 7 ms

Tried pinging from linux:
# ping 192.168.1.3
PING 192.168.1.3 (192.168.1.3) 56(84) bytes of data.
...and then nothing more..

can you connect to suse from windows command line[/b]

By ftp ?
ftp 192.168.1.2
gives:
ftp: connect: Unknown error number

Same for the IP of the router: 192.168.1.1

few ways of diagnosing your problem:
check smb.conf for errors run from terminal window:
#tesparm -v[/b]

gives:
# tesparm -v
bash: tesparm: command not found

test server:[/b]

test server:192.168.1.3
gives:
nothing happens

#smbclient -L box_name/or IP address
who is master browser[/b]

smbclient -L 192.168.1.3
gives:
timeout connecting to 192.168.1.3:445
timeout connecting to 192.168.1.3:139
Error connecting to 192.168.1.3 (Operationen pågår redan)
Connection to 192.168.1.3 failed (Error NT_STATUS_ACCESS_DENIED)

smbclient -L 192.168.1.2
gives:
Password:
Domain=[LINUX-SOYO] OS=[Unix] Server=[Samba 3.0.26a-3.5-1616-SUSE-SL10.3]

Sharename Type Comment
--------- ---- -------
profiles Disk Network Profiles Service
users Disk All users
groups Disk All groups
print$ Disk Printer Drivers
netlogon Disk Network Logon Service
IPC$ IPC IPC Service ("")
deskjet930c Printer HEWLETT-PACKARD DESKJET 930C
Domain=[LINUX-SOYO] OS=[Unix] Server=[Samba 3.0.26a-3.5-1616-SUSE-SL10.3]

Server Comment
--------- -------

Workgroup Master
--------- -------
MSHOME LINUX-SOYO

#nmblookup -M -- -
or
#nmblookup -A IPaddress
if enter server address then and look for the line:
..__MSBROWSE__. <01> - <GROUP> H <ACTIVE>

hostname -f[/b]

# nmblookup -A 192.168.1.3 (XP-box)
Looking up status of 192.168.1.3
No reply from 192.168.1.3

# nmblookup -A 192.168.1.1 (The router)
Looking up status of 192.168.1.1
No reply from 192.168.1.1


# nmblookup -M -- -
querying __MSBROWSE__ on 192.168.1.255
name_query failed to find name __MSBROWSE__#01


So here is an error..
How can this be fixed?

while samba linux is a little different from smb windows client, from users point of view is no more difficult. Difference is that you "already" know about windows while still learning linux.

suse's samba config is so convoluted that directry editing smb.conf, lmhosts, hosts would be faster than playing with Yast by the way.[/b]

Well, I agree to the point that I have some real useless knowledge now.
But regarding networks, they where really limited I must admit.
And things seems quite complicated here to...
The Yast should really be a help for a novice in networks (and SUSE/linux) though...

And the desciption in the first place should not be "cant see linuxbox" but "cant see remote box" ..

For the XP-laptop:
smbclient -L 192.168.1.3
gives:
timeout connecting to 192.168.1.3:445
timeout connecting to 192.168.1.3:139
Error connecting to 192.168.1.3 (Operationen pågår redan)
Connection to 192.168.1.3 failed (Error NT_STATUS_ACCESS_DENIED)[/b]

Happens to me if I have a third party firewall on the XP box blocking then network. Turn it off to test if that is the problem.

1)

profiles Disk Network Profiles Service
users Disk All users
groups Disk All groups
print$ Disk Printer Drivers
netlogon Disk Network Logon Service
IPC$ IPC IPC Service ("")
deskjet930c Printer HEWLETT-PACKARD DESKJET 930C
Domain=[LINUX-SOYO] OS=[Unix] Server=[Samba 3.0.26a-3.5-1616-SUSE-SL10.3][/b]

you don't have shares configured

example:
mbclient -L 192.168.1.12
Password:
Domain=[SEQUOIA] OS=[Unix] Server=[Samba 3.0.28]

Sharename Type Comment
--------- ---- -------
users Disk All users
groups Disk All groups
IPC$ IPC IPC Service (Arch Samba Server)
broch Disk Home Directories

basically you need to create share

deskjet930c Printer HEWLETT-PACKARD DESKJET 930C[/b]

means that you can share your printer (it is ready (well almost, with your config you will get access denied) to be connected) from windows box

<div class='quotetop'>QUOTE

questions to ask:
is this the same subnet?[/b]

I think so, IP SUBNET mask for both is : 255.255.255.0 according the router settings.[/b][/quote]
nope, this is subnet mask (which determines which part of the address is the network and which part is the individual node)
all boxes should be within (remembering bcast and router I assume in your case)
192.168.1.0 - 192.168.1.255

#tesparm -v[/b]

sorry for spelling mistake. It should be
#testparm -v

<div class='quotetop'>QUOTE

can you connect to suse from windows command line[/b]

By ftp ?
ftp 192.168.1.2
gives:
ftp: connect: Unknown error number[/b][/quote]

of course. I meant

NET SHARE - to list shares
and
NET USE - to connect to the share

if not, configure WINS
Well, I tried, DHCP is activated in Xp, as well as the Netbios setting "standard":[/b]

WINS is not DHCP. You will need WINS if computers are on different subnets
e.g.
192.168.0.xxx
and
192.168.1.xxx


you need to fix connectivity issue first. forget about GUI and smb:/
unless both machines are pingable, no point of configuring samba