Also try disabling one of the network cards. Find it in network and dial up connections, right mouse click and choose disable.

There is something there that you are not seeing.

OK I have been trying the exact same thing as you hak, here's my setup:

2k Server SP3 -PDC,DNS,WINS, Citrix Metaframe XPe
XP Pro
embedded NT 4.0 SP2 thin client
2000 Pro SP3 laptop
Red Hat9

[COLOR-RED]If Im hijakking here, then please accept my apologies[/COLOR=RED]

All of my machines can access Samba shares, but I get prompted with a user/pass for which nothing works. Here's my smb.conf:

[global]

# workgroup = NT-Domain-Name or Workgroup-Name
workgroup = homenet

# server string is the equivalent of the NT Description field
server string = rojo-sombrero

# 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
; hosts allow = 192.168.1. 192.168.2. 127.

# if you want to automatically load your printer list rather
# than setting them up individually then you'll need this
printcap name = /etc/printcap
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

# Uncomment this if you want a guest account, you must add this to /etc/passwd
# otherwise the user "nobody" is used
; guest account = pcguest

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

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

# Security mode. Most people will want user level security. See
# security_level.txt for details.

# Use password server option only with security = server
# The argument list may include:
password server = void [void] [void]
# or to auto-locate the domain controller/s
# password server = *
; password server = <NT-Server-Name>

# 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
encrypt passwords = yes
smb passwd file = /etc/samba/smbpasswd

# The following is needed to keep smbclient from spouting spurious errors
# when Samba is built with support for SSL.
; ssl CA certFile = /usr/share/ssl/certs/ca-bundle.crt

# The following are needed to allow password changing from Windows to
# update the Linux system password also.
# 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
passwd program = /usr/bin/passwd %u
passwd chat = *New*password* %n\n *Retype*new*password* %n\n *passwd:*all*authentication*tokens*updated*successfully*

# You can use PAM's password change control flag for Samba. If
# enabled, then PAM will be used for password changes when requested
# by an SMB client instead of the program listed in passwd program.
# It should be possible to enable this without changing your passwd
# chat parameter for most setups.

pam password change = yes

# 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

# This parameter will control whether or not Samba should obey PAM's
# account and session management directives. The default behavior is
# to use PAM for clear text authentication only and to ignore any
# account or session management. Note that Samba always ignores PAM
# for authentication in the case of encrypt passwords = yes

obey pam restrictions = yes

# Most people will find that this option gives better performance.
# See speed.txt and the manual pages for details
socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=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 = 10.0.0.7/24-10.0.0.6/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

# Browser Control Options:
# 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 = no

# 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 = no

# 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 = no

# Enable this if you want Samba to be a domain logon server for
# Windows95 workstations.
domain logons = no

# 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 roving profiles (only for Win95 and WinNT)
# %L substitutes for this servers netbios name, %U is username
# You must uncomment the [Profiles] share below
; logon path = \\%L\Profiles\%U

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

# 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 = 10.0.0.3

# 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.
security = DOMAIN
dns proxy = no

# 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

# seperate domain and username with '+', like DOMAIN+username
winbind separator = +
#use uids from 10000 to 20000 for domain users
winbind uid = 10000-20000
#use gids from 10000 ro 20000 for domain groups
winbind gid = 10000-20000
#allow enumeration of winbind users and groups
#might need to disable these next two for performance
#reasons on the winbindd host
winbind enum users = yes
winbind enum groups = yes
#give winbind users a real shell (olny needed if they have telnet/sshd, etc)
template homedir = /home/winnt/%D/%U
guest ok = yes
template shell = /bin/bash
#============================ Share Definitions ==============================
[homes]
comment = Home Directories
browseable = yes
writeable = yes
valid users = %S
create mode = 0664
directory mode = 0775
# If you want users samba doesn't recognize to be mapped to a guest user
; map to guest = bad user


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


# Un-comment the following to provide a specific roving profile share
# the default is to use the user's home directory
;[Profiles]
; path = /usr/local/samba/profiles
; browseable = no
; guest ok = yes


# NOTE: If you have a BSD-style print system there is no need to
# specifically define each individual printer
[printers]
comment = All Printers
path = /var/spool/samba
browseable = no
# Set public = yes to allow user 'guest account' to print
printable = 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 = yes
; writable = yes
; printable = no
; write list = @staff

# 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 = /home/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/local/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

[bhart]
path = /home/bhart
writeable = yes
guest ok = yes

[ben]
path = /home/ben
writeable = yes
guest ok = yes

# 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
#
# 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]
protocol = NT1
log file = /var/log/samba/%m.log
load printers = yes
smb passwd file = /etc/samba/smbpasswd
passwd chat = *New*password* %n\n *Retype*new*password* %n\n *passwd:*all*authentication*tokens*updated*successfully*
obey pam restrictions = yes
socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192
encrypt passwords = yes
passwd program = /usr/bin/passwd %u
dns proxy = yes
wins support = no
wins server = 192.168.1.253
wins proxy = no
netbios name = hcci-linux
netbios aliases = hcci-linux
server string = Samba 2.27a
printing = cups
unix password sync = Yes
workgroup = HCCI
os level = 20
printcap name = /etc/printcap
security = user
local master = no
domain master = no
domain controller = hcci-server #has two nics, linux can ping net bios
preferred master = no
max log size = 0
pam password change = yes

[serverbackup]
writeable = yes
create mode = 777
public = yes
path = /root/serverbackup
directory mode = 777

log file = /var/log/samba/%m.log


Samba creates a log file for each machine that tries to access it. The file is located in the /var/log/samba/ directory and uses the name of the machine and the .log extension. Please review and let us know if there are any messages there.

Please answer the other questions.

both cards are on the same sub, just 192.168.1.253 192.168.1.254

no log file for the hcci-server..

log.smbd
[2003/07/09 06:44:22, 0] smbd/server.c:main(707)
smbd version 2.2.7a-security-rollup-fix started.
Copyright Andrew Tridgell and the Samba Team 1992-2002
[2003/07/09 06:44:22, 0] param/loadparm.c:map_parameter(2077)
Unknown parameter encountered: "domain controller"
[2003/07/09 06:44:22, 0] param/loadparm.c:lp_do_parameter(2752)
Ignoring unknown parameter "domain controller"

log.nmbd
[2003/07/09 06:44:22, 0] nmbd/nmbd.c:main(794)
Netbios nameserver version 2.2.7a-security-rollup-fix started.
Copyright Andrew Tridgell and the Samba Team 1994-2002
[2003/07/09 06:44:22, 0] param/loadparm.c:map_parameter(2077)
Unknown parameter encountered: "domain controller"
[2003/07/09 06:44:22, 0] param/loadparm.c:lp_do_parameter(2752)
Ignoring unknown parameter "domain controller"
[2003/07/09 06:44:26, 0] nmbd/nmbd_responserecordsdb.c:find_response_record(235)
find_response_record: response packet id 6809 received with no matching record.
[2003/07/09 06:44:26, 0] nmbd/nmbd_responserecordsdb.c:find_response_record(235)
find_response_record: response packet id 6810 received with no matching record.

If you are trying to log into stuff and it is on an AD network you may want to change it to:

security=DOMAIN

instead of security=user like you have it.

Also, have you added it to the domain?
I don't mean by simply giving it a computer account.

Like in NT for you have to do like:
smbpasswd -j DOMAIN -r DOMAINPDC

Plus...you never answered any of my earlier questions so I can help you more

cockblocker

That is the longest goofyest smb.conf I've ever seen.

Wow.....throw that away

no crap... its like taking up space in the thread, PLEASE EDIT /remove it from your post man.. jeez

if ya check the above threads, i already disjoined it and rejoined it, thats not a 'true' smb.conf cause ive fucked with it so much in so many settings. but thats the basic, and setting it to share works fine, setting it to user, adding a user, loging in as the user on the share :user pass: screen gets in.

But all the while, the win2k server STILL cannot access the samba in any way shape or form, it cant get past the 'network path is not found'

Also im noticing that the win2k server isn't even showing up in the logs, its as if it never actually connects, but pings, ftp, http, https work between them, no firewalls no filters

Hmm...

More to come later. Still thinking...

And yes...

Would a mod please delete the "F" word in hakcenter's post above?

Would a mod also mind deleting cockblockers huge long hijacking post? It takes up WAY too much space and this thread doesn't need his post. He is not helpling in anyway.

Thanks

Solution as I read in alt.os.linux.mandrake - it should work in any distro that is using Shorewall as a Firewall - problem is that Shorewall is actually doing its job correctly !!

--------- extract ------------

Paul wrote:

> Hi
> had samba working perfectly and the I tried to enable Internet Connection
> sharing, Well needles to say something nuked samba. Just cannot get it to
> work again. I tired by stopping a few of the services that was running,
> shorewall, etc but that did not work..any sugestions? I really dont feel
> like reinstalling
> cheers
> paul
Put this in /etc/shorewall/rules

#samba rules
ACCEPT fw masq udp 1024: 137
ACCEPT masq fw udp 22,137:139,445
ACCEPT masq fw tcp 22,137:139,445
ACCEPT masq fw udp 1024: 137

That will do it !.

This is directly from the www.shorewall.net site, if you care to read.

MP

---------------------------------

Hope that helps you - it fixed it for me ?? You have to ensure that you have the correct things setup in /etc/samba/smb.conf as well - but with out the above in the /ect/shorewall/rules you will never be able to local network connect - if - you have internet connection sharing and shorewall as your firewall

Cockblocker,

I would recommend doing a clean install of Samba and following the IBM tutorial below. The other tutorial provides good backup material.

It is a good idea to backup the default smb.conf file and create a new one from scratch using a text editor such as vi. You can search google for vi and get tutorials on how to use it. The default has a lot of stuff that makes it hard to trouble shoot. Many people have used the IBM tutorial to set up Samba successfully.


http://www-1.ibm.com/servers/esdd/tu...mba/index.html


http://networking.earthweb.com/netos...le.php/1144701

http://networking.earthweb.com/netos...le.php/1151091


Remember to include the

domain logons = yes

command in your smb.conf file. This is required for Windows 2000/XP logons even though the literature suggests otherwise.

Does the server have the same problems as XP
were you need to change some settings in the registry.

reg or no reg, still dont work

This thread is turning into mashed potatoes