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.
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.
Last edited by dmizer; May 11th, 2009 at 09:46 AM.
1) Samba server howto | 2) mount windows/samba shares with CIFS + unicode | 3) best FTP server howto
4) NFS server/client howto | 5) Easy cross-platform LAN file sharing with FTP
6) Fix samba browsing!!! | 7) Fix Pulse audio
Happy Ubunting!
Here are the results, the same for both laptops:
How can I tell if winbind is running?Code: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
perhaps the easiest way is attempt to restart it with
watch for any messages.Code:sudo /etc/init.d/winbind restart
PC
To get a terminal command to put its output into a file use this format
{terminal command} > {filename}
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?
1) Samba server howto | 2) mount windows/samba shares with CIFS + unicode | 3) best FTP server howto
4) NFS server/client howto | 5) Easy cross-platform LAN file sharing with FTP
6) Fix samba browsing!!! | 7) Fix Pulse audio
Happy Ubunting!
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.
PC
To get a terminal command to put its output into a file use this format
{terminal command} > {filename}
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?
You need to install winbind - thats most probably it.
Code:sudo apt-get install winbind
PC
To get a terminal command to put its output into a file use this format
{terminal command} > {filename}
Yes, that could be a result of a few things.
- Winbind is not actually installed, or is not running on the client.
- WINS is not being queried before DNS.
- 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).
- A firewall is preventing WINS queries.
When using OpenDNS, this is expected behavior for the above problems (for the reasons I explained earlier).
1) Samba server howto | 2) mount windows/samba shares with CIFS + unicode | 3) best FTP server howto
4) NFS server/client howto | 5) Easy cross-platform LAN file sharing with FTP
6) Fix samba browsing!!! | 7) Fix Pulse audio
Happy Ubunting!
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!
There is a workgroup setting in /etc/samba/smb.conf.
Almost first line in the configuration
PC
To get a terminal command to put its output into a file use this format
{terminal command} > {filename}
Bookmarks