Can't connect to SAMBA share via Jaunty

[dmizer]

Thanks for the correction dmizer

No problem

Here's more information on the name resolution problem: http://www.backports.ubuntuforums.or...8&postcount=12

If none of that works, a firewall (On the server or on the client) may be interfering.

[Nixie Pixel]

Here are the results, the same for both laptops:

Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
192.168.0.0     *               255.255.255.0   U     2      0        0 wlan0
link-local      *               255.255.0.0     U     1000   0        0 wlan0
default         192.168.0.1     0.0.0.0         UG    0      0        0 wlan0

How can I tell if winbind is running?

[Peter09]

perhaps the easiest way is attempt to restart it with

sudo /etc/init.d/winbind restart

watch for any messages.

[dmizer]

I should note that the only WINS server on the network is the Ubuntu Server where I set wins support to be yes in smb.conf.

In smb.conf, "wins support" should be set to no. This option is only for use when the server is being used as a WINS server across a multi-subnetted network (so names will resolve across different subnets).

Though, this mistake is probably not hurting anything or preventing you from connecting.

Can you post your entire smb.conf file?

[Peter09]

Dmizer,
the thing of interest to me is that when she tries to ping an internal windows machine it goes out to an external DNS server - it seems to come down to name resolution.

[Nixie Pixel]

The client is a vanilla 9.04 Jaunty Jackalope desktop installation. The server was just installed the other day, Ubuntu Server 8.10. Neither have firewalls running, nor have I messed with the IP tables.

Trying to start winbind on the "bad" machine returns:
"sudo: /etc/init.d/winbind: command not found"

I'll post smb.conf in a few minutes, but I thought I could use SAMBA as a WINS server for a single subnet?

[Peter09]

You need to install winbind - thats most probably it.

sudo apt-get install winbind

[dmizer]

Dmizer,
the thing of interest to me is that when she tries to ping an internal windows machine it goes out to an external DNS server - it seems to come down to name resolution.

Yes, that could be a result of a few things.

1. Winbind is not actually installed, or is not running on the client.
2. WINS is not being queried before DNS.
3. The client is not finding the server because the client and server are not members of the same workgroup (Nautilus GVFS cannot search inside workgroups that it is not a member of).
4. A firewall is preventing WINS queries.

When using OpenDNS, this is expected behavior for the above problems (for the reasons I explained earlier).

[Nixie Pixel]

Thanks very much for your help, I appreciate it very much - I installed winbind on the "bad" laptop (it was already on the "good" one) and now I can connect to the server!

Since you mentioned it, how can I set the windows workgroup on an Ubuntu machine?

Thanks again!

[Peter09]

There is a workgroup setting in /etc/samba/smb.conf.
Almost first line in the configuration