Windows Can't Find samgba

I am using SuSE 9.1/Samba 3.0.2a and have run smbpasswd, and can connect to
a share from UNIX, but not from Windows. I get a message saying "Network
name cannot be found"

Do I need to do anything with xinetd?

Looking for ideas on what to try next. I can ssh into the box with no
problem, which is on a private network.


buck@turf /home/buck$ smbclient //turf/buck -Ubuck%secret
Domain=[TURF] OS=[Unix] Server=[Samba 3.0.2a-SUSE]
smb: \> dir
. D 0 Sun Nov 14 00:30:13 2004
.. D 0 Wed Nov 10 15:21:06 2004
.qt DH 0 Sat Nov 13 08:45:23 2004
bin D 0 Sun Nov 7 10:26:55 2004
.kde DH 0 Sat Nov 13 08:45:18 2004




Load smb config files from /etc/samba/smb.conf
Processing section "[homes]"
Processing section "[users]"
Processing section "[groups]"
Processing section "[pdf]"
Processing section "[printers]"
Processing section "[print$]"
Loaded services file OK.
Server role: ROLE_STANDALONE
Press enter to see a dump of your service definitions

# Global parameters
[global]
workgroup = TUX-NET
server string = Turf SuSE Linux Box
interfaces = 127.0.0.1, eth0
bind interfaces only = Yes
map to guest = Bad User
printer admin = @ntadmin, root, administrator

[homes]
comment = Home Directories
valid users = %S
read only = No
browseable = No

[users]
comment = All users
path = /home
read only = No
inherit permissions = Yes
veto files = /aquota.user/groups/shares/

[groups]
comment = All groups
path = /home/groups
read only = No
inherit permissions = Yes

[pdf]
comment = PDF creator
path = /var/tmp
create mask = 0600
printable = Yes
print command = /usr/bin/smbprngenpdf -J '%J' -c %c -s %s -u '%u' -z
%z

[printers]
comment = All Printers
path = /var/tmp
create mask = 0600
printable = Yes
browseable = No

[print$]
comment = Printer Drivers
path = /var/lib/samba/drivers
write list = @ntadmin, root
force group = ntadmin
create mask = 0664
directory mask = 0775

"Buck Turgidson" <(E-Mail Removed)> wrote in message
news:iTPld.2087$nj.1875@lakeread01...
> I am using SuSE 9.1/Samba 3.0.2a and have run smbpasswd, and can connect
to
> a share from UNIX, but not from Windows. I get a message saying "Network
> name cannot be found"
>
> Do I need to do anything with xinetd?
>
> Looking for ideas on what to try next. I can ssh into the box with no
> problem, which is on a private network.
>
>
> buck@turf /home/buck$ smbclient //turf/buck -Ubuck%secret
> Domain=[TURF] OS=[Unix] Server=[Samba 3.0.2a-SUSE]
> smb: \> dir
> . D 0 Sun Nov 14 00:30:13 2004
> .. D 0 Wed Nov 10 15:21:06 2004
> .qt DH 0 Sat Nov 13 08:45:23 2004
> bin D 0 Sun Nov 7 10:26:55 2004
> .kde DH 0 Sat Nov 13 08:45:18 2004
>
>
>
>
> Load smb config files from /etc/samba/smb.conf
> Processing section "[homes]"
> Processing section "[users]"
> Processing section "[groups]"
> Processing section "[pdf]"
> Processing section "[printers]"
> Processing section "[print$]"
> Loaded services file OK.
> Server role: ROLE_STANDALONE
> Press enter to see a dump of your service definitions
>
> # Global parameters
> [global]
> workgroup = TUX-NET
> server string = Turf SuSE Linux Box
> interfaces = 127.0.0.1, eth0
> bind interfaces only = Yes
> map to guest = Bad User
> printer admin = @ntadmin, root, administrator
>
> [homes]
> comment = Home Directories
> valid users = %S
> read only = No
> browseable = No
>
> [users]
> comment = All users
> path = /home
> read only = No
> inherit permissions = Yes
> veto files = /aquota.user/groups/shares/
>
> [groups]
> comment = All groups
> path = /home/groups
> read only = No
> inherit permissions = Yes
>
> [pdf]
> comment = PDF creator
> path = /var/tmp
> create mask = 0600
> printable = Yes
> print command = /usr/bin/smbprngenpdf -J '%J' -c %c -s %s -u
'%u' -z
> %z
>
> [printers]
> comment = All Printers
> path = /var/tmp
> create mask = 0600
> printable = Yes
> browseable = No
>
> [print$]
> comment = Printer Drivers
> path = /var/lib/samba/drivers
> write list = @ntadmin, root
> force group = ntadmin
> create mask = 0664
> directory mask = 0775
>
>
>
From the information you are giving, your Windows
box is not set up for networking.

> From the information you are giving, your Windows
> box is not set up for networking.
>

What leads you to that conclusion? I have used this Windows XP laptop with
Samba many times. I just can't get this new install to work.

I have established the same user on the Windows and Linux side, so I can't
figure out what could be preventing me from accessing it.

Buck Turgidson wrote:

>> From the information you are giving, your Windows
>> box is not set up for networking.
>>
>
> What leads you to that conclusion? I have used this Windows XP laptop
> with
> Samba many times. I just can't get this new install to work.
>
> I have established the same user on the Windows and Linux side, so I
> can't figure out what could be preventing me from accessing it.

You mention "new install". Is the XP the new install? If so, check that
the Windows Firewall isn't on. If you have Service Pack 2, it is on by
default. Then you need to add your lan as Trusted. Or maybe it's SuSE's
firewall that is on.

Malke
--
"I have a cunning plan..."

>
> You mention "new install". Is the XP the new install? If so, check that
> the Windows Firewall isn't on. If you have Service Pack 2, it is on by
> default. Then you need to add your lan as Trusted. Or maybe it's SuSE's
> firewall that is on.

A new Linux install (re-install of SuSE 9.1). I got a message saying that
the package samba-winbind was not installed, so maybe that was the problem.
I'll try tonight.

"Buck Turgidson" <(E-Mail Removed)> wrote in message
news:0k6n62-(E-Mail Removed)...
> >
> > You mention "new install". Is the XP the new install? If so, check that
> > the Windows Firewall isn't on. If you have Service Pack 2, it is on by
> > default. Then you need to add your lan as Trusted. Or maybe it's SuSE's
> > firewall that is on.
>
> A new Linux install (re-install of SuSE 9.1). I got a message saying that
> the package samba-winbind was not installed, so maybe that was the
problem.
> I'll try tonight.
>
>

That is not the problem.