DNS resolution and samba shares...

Issues Related to Networking (Wired and Wireless)

Moderator: Moderators

DNS resolution and samba shares...

Postby dirtsandwich » Wed Feb 10, 2010 19:32

Hi I've been having an issue with DNS resolution on my laptop, but it looks like (to me) this is causing network share issues. Please correct me if I'm wrong.

On multiple networks - all DHCP - I can't ever dynamically pull the DNS server info so I've just manually added it to the resolv.conf up to this point. Whatever is causing this I believe is causing an issue in browsing to network shares.

Here's the symptoms:
-I setup samba on my laptop but I cannot browse to it without it prompting for a username and password. On other machines I can browse to the samba share on my laptop without the prompt.
-On my laptop I cannot browse to any network share without it prompting for a username and password. Here is the smb.conf from the open network share.

Code: Select all
# This is the main Samba configuration file. You should read the
# smb.conf(5) manual page in order to understand the options listed
# here. Samba has a huge number of configurable options (perhaps too
# many!) most of which are not shown in this example
#
# For a step to step guide on installing, configuring and using samba,
# read the Samba-HOWTO-Collection. This may be obtained from:
#  http://www.samba.org/samba/docs/Samba-HOWTO-Collection.pdf
#
# Many working examples of smb.conf files can be found in the
# Samba-Guide which is generated daily and can be downloaded from:
#  http://www.samba.org/samba/docs/Samba-Guide.pdf
#
# Any line which starts with a ; (semi-colon) or a # (hash)
# is a comment and is ignored. In this example we will use a #
# for commentry and a ; for parts of the config file that you
# may wish to enable
#
# NOTE: Whenever you modify this file you should run the command "testparm"
# to check that you have not made any basic syntactic errors.
#
#======================= Global Settings =====================================
[global]

# 1. Server Naming Options:
# workgroup = NT-Domain-Name or Workgroup-Name


# netbios name is the name you will see in "Network Neighbourhood",
# but defaults to your hostname
netbios name = networkshare

# server string is the equivalent of the NT Description field
server string = networkshare

# 2. Printing Options:
# CHANGES TO ENABLE PRINTING ON ALL CUPS PRINTERS IN THE NETWORK
# if you want to automatically load your printer list rather
# than setting them up individually then you'll need this
#   printcap name = cups
#   load printers = yes

# It should not be necessary to spell out the print system type unless
# yours is non-standard. Currently supported print systems include:
# bsd, sysv, plp, lprng, aix, hpux, qnx, cups
#   printing = cups

# 3. Logging Options:
# this tells Samba to use a separate log file for each machine
# that connects
log file = /var/log/samba/log.%m

# Put a capping on the size of the log files (in Kb).
max log size = 50

# Set the log (verbosity) level (0 <= log level <= 10)
; log level = 3

# 4. Security and Domain Membership Options:
# This option is important for security. It allows you to restrict
# connections to machines which are on your local network. The
# following example restricts access to two C class networks and
# the "loopback" interface. For more examples of the syntax see
# the smb.conf man page. Do not enable this if (tcp/ip) name resolution does
# not work for all the hosts in your network.
;   hosts allow = 192.168.1. 192.168.2. 127.

# Uncomment this if you want a guest account, you must add this to /etc/passwd
# otherwise the user "nobody" is used
guest account = nobody
# Allow users to map to guest:
map to guest = Bad User

# Security mode. Most people will want user level security. See
# security_level.txt for details.
security = share
# Use password server option only with security = server or security = domain
# When using security = domain, you should use password server = *
;   password server = <NT-Server-Name>
;   password server = *

# Password Level allows matching of _n_ characters of the password for
# all combinations of upper and lower case.
;  password level = 8
;  username level = 8

# You may wish to use password encryption. Please read
# ENCRYPTION.txt, Win95.txt and WinNT.txt in the Samba documentation.
# Do not enable this option unless you have read those documents
# Encrypted passwords are required for any use of samba in a Windows NT domain
# The smbpasswd file is only required by a server doing authentication, thus
# members of a domain do not need one.
encrypt passwords = yes

# The following are needed to allow password changing from Windows to
# also update the Linux system password.
# NOTE: Use these with 'encrypt passwords' and 'smb passwd file' above.
# NOTE2: You do NOT need these to allow workstations to change only
#        the encrypted SMB passwords. They allow the Unix password
#        to be kept in sync with the SMB password.
;  unix password sync = Yes
# You either need to setup a passwd program and passwd chat, or
# enable pam password change
;  pam password change = yes
;  passwd program = /usr/bin/passwd %u
;  passwd chat = *New*UNIX*password* %n\n *Re*ype*new*UNIX*password* %n\n ;*passwd:*all*authentication*tokens*updated*successfully*

# Unix users can map to different SMB User names
;  username map = /etc/samba/smbusers

# Using the following line enables you to customise your configuration
# on a per machine basis. The %m gets replaced with the netbios name
# of the machine that is connecting
;   include = /etc/samba/smb.conf.%m

# Options for using winbind. Winbind allows you to do all account and
# authentication from a Windows or samba domain controller, creating
# accounts on the fly, and maintaining a mapping of Windows RIDs to unix uid's
# and gid's. idmap uid and idmap gid are the only required parameters.
#
# winbind separator is the character a user must use between their domain
# name and username, defaults to "\"
;  winbind separator = +
#
# winbind use default domain allows you to have winbind return usernames
# in the form user instead of DOMAIN+user for the domain listed in the
# workgroup parameter.
;  winbind use default domain = yes
#
# template homedir determines the home directory for winbind users, with
# %D expanding to their domain name and %U expanding to their username:
;  template homedir = /home/%D/%U

# When using winbind, you may want to have samba create home directories
# on the fly for authenticated users. Ensure that /etc/pam.d/samba is
# using 'service=system-auth-winbind' in pam_stack modules, and then
# enable obedience of pam restrictions below:
;  obey pam restrictions = yes

#
# template shell determines the shell users authenticated by winbind get
;  template shell = /bin/bash

# 5. Browser Control and Networking Options:
# Most people will find that this option gives better performance.
# See speed.txt and the manual pages for details
socket options = TCP_NODELAY SO_SNDBUF=8192 SO_RCVBUF=8192

# Configure Samba to use multiple interfaces
# If you have multiple network interfaces then you must list them
# here. See the man page for details.
#   interfaces = 192.168.1.100/24

# Configure remote browse list synchronisation here
#  request announcement to, or browse list sync from:
#       a specific host or from / to a whole subnet (see below)
;   remote browse sync = 192.168.3.25 192.168.5.255
# Cause this host to announce itself to local subnets here
;   remote announce = 192.168.1.255 192.168.2.44

# set local master to no if you don't want Samba to become a master
# browser on your network. Otherwise the normal election rules apply
local master = yes

# OS Level determines the precedence of this server in master browser
# elections. The default value should be reasonable
;   os level = 33

# Domain Master specifies Samba to be the Domain Master Browser. This
# allows Samba to collate browse lists between subnets. Don't use this
# if you already have a Windows NT domain controller doing this job
;   domain master = yes

# Preferred Master causes Samba to force a local browser election on startup
# and gives it a slightly higher chance of winning the election
preferred master = yes

# 6. Domain Control Options:
# Enable this if you want Samba to be a domain logon server for
# Windows95 workstations or Primary Domain Controller for WinNT and Win2k
;   domain logons = yes

# if you enable domain logons then you may want a per-machine or
# per user logon script
# run a specific logon batch file per workstation (machine)
;   logon script = %m.bat
# run a specific logon batch file per username
;   logon script = %U.bat

# Where to store roaming profiles for WinNT and Win2k
#        %L substitutes for this servers netbios name, %U is username
#        You must uncomment the [Profiles] share below
;   logon path = \\%L\Profiles\%U

# Where to store roaming profiles for Win9x. Be careful with this as it also
# impacts where Win2k finds it's /HOME share
; logon home = \\%L\%U\.profile


# The add user script is used by a domain member to add local user accounts
# that have been authenticated by the domain controller, or when adding
# users via the Windows NT Tools (ie User Manager for Domains).

# Scripts for file (passwd, smbpasswd) backend:
; add user script = /usr/sbin/useradd -s /bin/false '%u'
; delete user script = /usr/sbin/userdel '%s'
; add user to group script = /usr/bin/gpasswd -a '%u' '%g'
; delete user from group script = /usr/bin/gpasswd -d '%u' '%g'
; set primary group script = /usr/sbin/usermod -g '%g' '%u'
; add group script = /usr/sbin/groupadd %g && getent group '%g'|awk -F: '{print $3}'
; delete group script = /usr/sbin/groupdel '%g'

# Scripts for LDAP backend (assumes nss_ldap is in use on the domain controller.
# Needs IDEALX scripts, and configuration in smbldap_conf.pm.
# This assumes you've installed the IDEALX scripts into /usr/share/samba/scripts...
; add user script = /usr/share/samba/scripts/smbldap-useradd.pl '%u'
; delete user script = /usr/share/samba/scripts/smbldap-userdel.pl '%u'
; add user to group script = /usr/share/samba/scripts/smbldap-groupmod.pl -m '%u' '%g'
; delete user from group script = /usr/share/samba/scripts/smbldap-groupmod.pl -x '%u' '%g'
; set primary group script = /usr/share/samba/scripts/smbldap-usermod.pl -g '%g' '%u'
; add group script = /usr/share/samba/scripts/smbldap-groupadd.pl '%g' && /usr/share/samba/scripts/smbldap-groupshow.pl %g|awk '/^gidNumber:/ {print $2}'
; delete group script = /usr/share/samba/scripts/smbldap-userdel.pl '%g'


# The add machine script is use by a samba server configured as a domain
# controller to add local machine accounts when adding machines to the domain.
# The script must work from the command line when replacing the macros,
# or the operation will fail. Check that groups exist if forcing a group.
# Script for domain controller for adding machines:
; add machine script = /usr/sbin/useradd -d /dev/null -g machines -c 'Machine Account' -s /bin/false '%u'
# Script for domain controller with LDAP backend for adding machines (You need
# the IDEALX scripts, and to configure the smbldap_conf.pm first):
; add machine script = /usr/share/samba/scripts/smbldap-useradd.pl -w -d /dev/null -g machines -c 'Machine Account' -s /bin/false '%u'

# Domain groups:
# Domain groups are now configured by using the 'net groupmap' tool

# Samba Password Database configuration:
# Samba now has runtime-configurable password database backends.
# smbpasswd is for backwards compatibility only Default (not recommended),
# new installations should use tdbsam or ldap.
; passdb backend = smbpasswd
# TDB backend
; passdb backend = tdbsam
# LDAP with fallback to smbpasswd guest
# Enable SSL by using an ldaps url, or enable tls with 'ldap ssl' below.
; passdb backend = ldapsam:ldaps://ldap.mydomain.com
# Use the samba2 LDAP schema:
; passdb backend = ldapsam_compat:ldaps://ldap.mydomain.com

# idmap uid account range:
# This is a range of unix user-id's that samba will map non-unix RIDs to,
# such as when using Winbind
; idmap uid = 10000-20000
; idmap gid = 10000-20000

# LDAP configuration for Domain Controlling:
# The account (dn) that samba uses to access the LDAP server
# This account needs to have write access to the LDAP tree
# You will need to give samba the password for this dn, by
# running 'smbpasswd -w mypassword'
; ldap admin dn = cn=root,dc=mydomain,dc=com
; ldap ssl = start_tls
# start_tls should run on 389, but samba defaults incorrectly to 636
; ldap port = 389
; ldap suffix = dc=mydomain,dc=com
; ldap server = ldap.mydomain.com
# Seperate suffixes are available for machines, users, groups, and idmap, if
# ldap suffix appears first, it is appended to the specific suffix.
# Example for a unix-ish directory layout:
; ldap machine suffix = ou=Hosts
; ldap user suffix = ou=People
; ldap group suffix = ou=Group
; ldap idmap suffix = ou=Idmap
# Example for AD-ish layout:
; ldap machine suffix = cn=Computers
; ldap user suffix = cn=Users
; ldap group suffix = cn=Groups
; ldap idmap suffix = cn=Idmap


# 7. Name Resolution Options:
# All NetBIOS names must be resolved to IP Addresses
# 'Name Resolve Order' allows the named resolution mechanism to be specified
# the default order is "host lmhosts wins bcast". "host" means use the unix
# system gethostbyname() function call that will use either /etc/hosts OR
# DNS or NIS depending on the settings of /etc/host.config, /etc/nsswitch.conf
# and the /etc/resolv.conf file. "host" therefore is system configuration
# dependant. This parameter is most often of use to prevent DNS lookups
# in order to resolve NetBIOS names to IP Addresses. Use with care!
# The example below excludes use of name resolution for machines that are NOT
# on the local network segment
# - OR - are not deliberately to be known via lmhosts or via WINS.
; name resolve order = wins host lmhosts bcast

# Windows Internet Name Serving Support Section:
# WINS Support - Tells the NMBD component of Samba to enable it's WINS Server
wins support = no

# WINS Server - Tells the NMBD components of Samba to be a WINS Client
#       Note: Samba can be either a WINS Server, or a WINS Client, but NOT both
;   wins server = w.x.y.z

# WINS Proxy - Tells Samba to answer name resolution queries on
# behalf of a non WINS capable client, for this to work there must be
# at least one  WINS Server on the network. The default is NO.
;   wins proxy = yes

# DNS Proxy - tells Samba whether or not to try to resolve NetBIOS names
# via DNS nslookups. The built-in default for versions 1.9.17 is yes,
# this has been changed in version 1.9.18 to no.
dns proxy = no
restrict anonymous = no
domain master = no
max protocol = NT
acl compatibility = winnt
ldap ssl = No
server signing = Auto


# 8. File Naming Options:
# Case Preservation can be handy - system default is _no_
# NOTE: These can be set on a per share basis
;  preserve case = no
;  short preserve case = no
# Default case is normally upper case for all DOS files
;  default case = lower
# Be very careful with case sensitivity - it can break things!
;  case sensitive = no

# Enabling internationalization:
# you can match a Windows code page with a UNIX character set.
# Windows: 437 (US), 737 (GREEK), 850 (Latin1 - Western European),
# 852 (Czech), 861 (???), 932 (Japanese),
# 936 (Simplified Chin.), 949 (Korean Hangul),
# 950 (Trad. Chin.).
# More detail about code page is in
# "http://www.microsoft.com/globaldev/reference/oslocversion.mspx"
# UNIX: ISO8859-1 (Western European), ISO8859-2 (Eastern Eu.),
# ISO8859-5 (Russian Cyrillic), KOI8-R (Alt-Russ. Cyril.)
# This is an example for french users:
;   dos charset = 850
;   unix charset = ISO8859-1


#============================ Share Definitions ==============================
[homes]
comment = Home Directories
browseable = no
read only = no
# You can enable VFS recycle bin on a per share basis:
# Uncomment the next 2 lines (make sure you create a
# .recycle folder in the base of the share and ensure
# all users will have write access to it. See
# examples/VFS/recycle/REAME in the samba docs for details
;   vfs object = /usr/lib/samba/vfs/recycle.so

# Un-comment the following and create the netlogon directory for Domain Logons
; [netlogon]
;   comment = Network Logon Service
;   path = /var/lib/samba/netlogon
;   guest ok = yes
;   writable = no

# Un-comment the following to provide a specific roving profile share
# the default is to use the user's home directory
;[Profiles]
;    path = /var/lib/samba/profiles
;    browseable = no
;    guest ok = yes
# This script can be enabled to create profile directories on the fly
# You may want to turn off guest acces if you enable this, as it
# hasn't been thoroughly tested.
;root preexec = PROFILE=/var/lib/samba/profiles/%u; if [ ! -e $PROFILE ]; ;                then mkdir -pm700 $PROFILE; chown %u:%g $PROFILE;fi

# NOTE: If you have a CUPS print system there is no need to
# specifically define each individual printer.
# You must configure the samba printers with the appropriate Windows
# drivers on your Windows clients. On the Samba server no filtering is
# done. If you wish that the server provides the driver and the clients
# send PostScript ("Generic PostScript Printer" under Windows), you have
# to swap the 'print command' line below with the commented one.
[printers]
comment = All Printers
path = /var/spool/samba
browseable = no
# set to yes to allow user 'guest account' to print.
guest ok = no
printable = yes

# This share is used for Windows NT-style point-and-print support.
# To be able to install drivers, you need to be either root, or listed
# in the printer admin parameter above. Note that you also need write access
# to the directory and share definition to be able to upload the drivers.
# For more information on this, please see the Printing Support Section of
# /usr/share/doc/samba-<version>/Samba-HOWTO-Collection.pdf
[print$]
path = /var/lib/samba/printers
write list = @adm root
guest ok = yes

# This one is useful for people to share files
;[tmp]
;   comment = Temporary file space
;   path = /tmp
;   read only = no
;   public = yes

# A publicly accessible directory, but read only, except for people in
# the "staff" group
;[public]
;   comment = Public Stuff
;   path = /home/samba/public
;   public = yes
;   writable = no
;   write list = @staff
# Audited directory through experimental VFS audit.so module:
# Uncomment next line.
;   vfs object = /usr/lib/samba/vfs/audit.so

# Other examples.
#
# A private printer, usable only by Fred. Spool data will be placed in Fred's
# home directory. Note that fred must have write access to the spool directory,
# wherever it is.
;[fredsprn]
;   comment = Fred's Printer
;   valid users = fred
;   path = /homes/fred
;   printer = freds_printer
;   public = no
;   writable = no
;   printable = yes

# A private directory, usable only by Fred. Note that Fred requires write
# access to the directory.
;[fredsdir]
;   comment = Fred's Service
;   path = /usr/somewhere/private
;   valid users = fred
;   public = no
;   writable = yes
;   printable = no

# a service which has a different directory for each machine that connects
# this allows you to tailor configurations to incoming machines. You could
# also use the %u option to tailor it by user name.
# The %m gets replaced with the machine name that is connecting.
;[pchome]
;  comment = PC Directories
;  path = /usr/pc/%m
;  public = no
;  writable = yes
# A publicly accessible directory, read/write to all users. Note that all files
# created in the directory by users will be owned by the default user, so
# any user with access can delete any other user's files. Obviously this
# directory must be writable by the default user. Another user could of course
# be specified, in which case all files would be owned by that user instead.
;[public]
;   path = /usr/somewhere/else/public
;   public = yes
;   only guest = yes
;   writable = yes
;   printable = no

# The following two entries demonstrate how to share a directory so that two
# users can place files there that will be owned by the specific users. In this
# setup, the directory should be writable by both users and should have the
# sticky bit set on it to prevent abuse. Obviously this could be extended to
# as many users as required.
;[myshare]
;   comment = Mary's and Fred's stuff
;   path = /usr/somewhere/shared
;   valid users = mary fred
;   public = no
;   writable = yes
;   printable = no
;   create mask = 0765

[networkshare]
comment = Mutual
path = /home/fileserver/mnt/raid/
guest ok = yes
read only = no
writeable = yes


my nsswitch.conf

Code: Select all
# /etc/nsswitch.conf:
# $Header: /var/cvsroot/gentoo/src/patchsets/glibc/extra/etc/nsswitch.conf,v 1.1 2006/09/29 23:52:23 vapier Exp $

passwd:      compat
shadow:      compat
group:       compat

# passwd:    db files nis
# shadow:    db files nis
# group:     db files nis

hosts:       files mdns4_minimal dns mdns4
networks:    files dns

services:    db files
protocols:   db files
rpc:         db files
ethers:      db files
netmasks:    files
netgroup:    files
bootparams:  files

automount:   files
aliases:     files


I appreciate the help.
dirtsandwich
Baby Hen
 
Posts: 14
Joined: Wed Mar 04, 2009 21:08

Re: DNS resolution and samba shares...

Postby xlnagla » Sat Feb 20, 2010 1:50

to start, I'm really not sure that your DNS issues and your samba issues are related; however I may be able to help with the DNS issues.

first, what are you using to configure your network? Are you wired or wireless? Are you a NetworkManager or WiCD user?

~xlnagla
xlnagla
Sagely Hen
 
Posts: 1078
Joined: Mon May 28, 2007 2:44

Re: DNS resolution and samba shares...

Postby dirtsandwich » Sat Feb 20, 2010 2:46

Thanks for your reply, I am using wicd wireless.

it may be they are unrelated. I forgot to add this - hope it's helpful. This all started after doing a bunch of updates and one was a kernel upgrade. The first sign was that it had renamed my wlan0 to eth1. Not a big deal, changed wicd to look at eth1 not wlan0.

Then CUPS was unable to see a networked printer that I had been using on previous installations. I have a buddy that swears by HPLIP so I installed it. HPLIP would see the printer but couldn't ever connect. When I finally launched it from terminal and pointed to the IP of the printer (something like 'hplip 192.168.100.x') it installed fine and I could print to it.

anyway... I got ticked so I decided I would reinstall and change from x86 to the AMD 64.

Fresh install with no updates using Network Manager same thing happened. Still prompts for username and password on samba shares. Went home that night - did all my updates and the kernel upgrade - same thing.

I started reading http://forum.sabayonlinux.org/viewtopic ... 52&t=18289 hoping it was related but it doesn't look it it really is. Strange thing is when I look at /etc/conf.d/net it says
Code: Select all
config_pan0=" netmask "
dns_domain_pan0="localdomain"
nis_domain_pan0="localdomain"
config_wmaster0=" netmask "
dns_domain_wmaster0="localdomain"
nis_domain_wmaster0="localdomain"
config_wlan0=" netmask "
dns_domain_wlan0="localdomain"
nis_domain_wlan0="localdomain"
config_eth0=" netmask "
dns_domain_eth0="localdomain"
nis_domain_eth0="localdomain"
gateway="/"
iface_lo="dhcp127.0.0.1 netmask 255.0.0.0"
iface_wlan0="dhcp192.168.0.70 netmask 255.255.255.0"
iface_eth0="dhcp"


so there is no eth1 (which is my wireless card). Should I add
Code: Select all
modules="dhcpcd"
config_eth1="dhcp"


dhcpcd isn't set at default runlevel...

Code: Select all
dirtlap dirtsandwich # rc-update -v | grep dhc
                dhcpd |
             dhcrelay |
               dhcpcd |
               dhcdbd |
dirtlap dirtsandwich #

should I add it and restart dhcpcd?
dirtsandwich
Baby Hen
 
Posts: 14
Joined: Wed Mar 04, 2009 21:08

Re: DNS resolution and samba shares...

Postby xlnagla » Sat Feb 20, 2010 3:33

if you're using wicd you need dhcdbd; if you're using NM you don't. you shouldn't have to edit /etc/resolv.conf for anything; both wicd and NM auto-generate it.

~xlnagla
xlnagla
Sagely Hen
 
Posts: 1078
Joined: Mon May 28, 2007 2:44

Re: DNS resolution and samba shares...

Postby dirtsandwich » Sat Feb 20, 2010 4:59

I added dhcdbd to default and restarted. still won't resolve DNS

Code: Select all
dirtlap dirtsandwich # rc-update -v | grep dhc
                dhcpd |
             dhcrelay |
               dhcpcd |
               dhcdbd |           default
dirtsandwich
Baby Hen
 
Posts: 14
Joined: Wed Mar 04, 2009 21:08

Re: DNS resolution and samba shares...

Postby dirtsandwich » Sat Feb 20, 2010 6:51

this is interesting... from /var/log/messages

Code: Select all
Feb 19 22:43:08 dirtlap dhcpcd: dhcpcd not running
Feb 19 22:43:08 dirtlap dhcpcd: dhcpcd not running
Feb 19 22:43:08 dirtlap kernel: [ 6643.488647] forcedeth 0000:00:0a.0: irq 27 for MSI/MSI-X
Feb 19 22:43:08 dirtlap kernel: [ 6643.488846] eth0: no link during initialization.
Feb 19 22:43:08 dirtlap kernel: [ 6643.489632] ADDRCONF(NETDEV_UP): eth0: link is not ready
Feb 19 22:43:08 dirtlap dhcpcd: dhcpcd not running
Feb 19 22:43:19 dirtlap kernel: [ 6654.446036] eth1: no IPv6 routers present
Feb 19 22:43:22 dirtlap dhcpcd: version 5.1.4 starting
Feb 19 22:43:22 dirtlap dhcpcd: eth1: broadcasting for a lease
Feb 19 22:43:22 dirtlap dhcpcd: eth1: offered 192.168.0.95 from 192.168.0.1
Feb 19 22:43:23 dirtlap dhcpcd: eth1: acknowledged 192.168.0.95 from 192.168.0.1
Feb 19 22:43:23 dirtlap dhcpcd: eth1: checking for 192.168.0.95
Feb 19 22:43:28 dirtlap dhcpcd: eth1: leased 192.168.0.95 for 86400 seconds
Feb 19 22:43:28 dirtlap dhcpcd: forking to background


Does this mean wicd is trying to use dhcpcd?
dirtsandwich
Baby Hen
 
Posts: 14
Joined: Wed Mar 04, 2009 21:08

Re: DNS resolution and samba shares...

Postby xlnagla » Sat Feb 20, 2010 18:46

I believe so.
xlnagla
Sagely Hen
 
Posts: 1078
Joined: Mon May 28, 2007 2:44

Re: DNS resolution and samba shares...

Postby Fitzcarraldo » Sat Feb 20, 2010 19:04

Don't use Wicd myself but, for information, the ebuild for the latest version of Wicd in Entropy (wicd-1.7.0) shows that wicd depends on dhcpcd.

Google throws up some Jan. and Feb. 2010 bug reports for Wicd, so perhaps the latest version of Wicd has a bug?

NetworkManager 0.7.2 is working perfectly for me with WiFi (unencrypted, WEP and WPA-PSK), Ethernet (static and dynamic IP addressing) and mobile broadband, so if you're desperate to get a connection you could try using NetworkManager (plus KNetworkManager if you're using KDE, or NM-Applet if you're using GNOME) to see if that works for you, at least until someone can solve your problem with Wicd if you prefer to use Wicd.
User avatar
Fitzcarraldo
Sagely Hen
 
Posts: 7977
Joined: Sat Mar 10, 2007 5:40
Location: United Kingdom

Re: DNS resolution and samba shares...

Postby Fitzcarraldo » Mon Mar 08, 2010 12:45

dirtsandwich, did you ever solve your problem? The smb.conf file you posted doesn't appear to have the workgroup specified. And is that really your PC's NetBIOS name in there?

Separately from your DNS resolution problem, for Samba share browsing have a look at the thread smb problem after KDE 4.3.2 update: Sabayon 5.0 KDE [Solved].
User avatar
Fitzcarraldo
Sagely Hen
 
Posts: 7977
Joined: Sat Mar 10, 2007 5:40
Location: United Kingdom


Return to Networking and Wireless

Who is online

Users browsing this forum: No registered users and 1 guest

cron