Robert.Bernard@servicedelivery.org.uk
2003-Jun-03 14:45 UTC
[Samba] New samba connection will not work
I'm fairly new to samba but I've spent too long on this - can anyone
help?
This system was previously working on another domain. Now I have tried to
register it on the
production domain (it has been removed from the test domain and I've deleted
the secrets file and
then added it to the live (OASIS) domain and I get
C:\WINNT\SYSTEM32>net use * \\confasr1\midas
System error 53 has occurred.
The network path was not found.
When I added it to the domain I got:
smbpasswd -D3 -j OASIS -r OADC01 -U adminID%password
Initialising global parameters
params.c:pm_process() - Processing configuration file
"/usr/local/samba/lib/smb.conf"
Processing section "[global]"
added interface ip=10.94.50.26 bcast=10.94.255.255 nmask=255.255.0.0
resolve_lmhosts: Attempting lmhosts lookup for name OADC01<0x20>
resolve_hosts: Attempting host lookup for name OADC01<0x20>
Connecting to 10.94.0.181 at port 445
error connecting to 10.94.0.181:445 (Connection refused)
Connecting to 10.94.0.181 at port 139
session setup ok
Domain=[OASIS] OS=[Windows NT 4.0] Server=[NT LAN Manager 4.0]
lsa_io_sec_qos: length c does not match size 8
Joined domain OASIS.
My smb is
# /usr/local/samba/bin/smbd -V
Version 2.2.8a
My smb.conf file is :
( an almost identical smb.conf is used on another server with no problems)
[global]
workgroup = OASIS
netbios name = CONFASR1
security = DOMAIN
# let any NT Server become browsing master ...
os level = 31
log level = 2
encrypt passwords = Yes
password server = OADC01
announce version = 4.0
add user script = /usr/local/samba/lib/logStExuser %u
# root preexec = /usr/local/samba/lib/setUserGroup %u %g %U %G
username map = /usr/local/samba/lib/users.map
# domain group map = /usr/local/samba/lib/groups.mapping
# local group map = /usr/local/samba/lib/groups.mapping
[midas]
comment = For MIDAS VSS only
# ################## ACCESS ...
valid users = tstrw1 , tstrw2 , tstr1, rbernard , mduffy
read list = tstr1
# ################## ... ACCESS
read only = No
nt acl support = yes
path = /cc/repvss1/MIDAS
force group = midvssrw
fake directory create times = yes
# guest ok = Yes
## security
create mask = 0774
# create mask = 0774
force create mode = 0660
directory security mask = 0777
force directory mode = 0770
force directory security mode = 0777
delete readonly = no
and ...
# ls -l /cc/repvss1
total 18
drwxrwxr-x 2 root midvssrw 512 Jun 3 11:02 MIDAS
drwx------ 2 root root 8192 Apr 23 09:32 lost+found
Robert Bernard
> C:\WINNT\SYSTEM32>net use * \\confasr1\midas > System error 53 has occurred. > > The network path was not found.Looks like your client can't resolve the NETBIOS name - did you try a DNS name or dotted decimal address instead of 'confasr1'? And you can always use LMHOSTS on the client if you really want the NETBIOS name. -Mike MacIsaac, IBM mikemac at us.ibm.com (845) 433-7061
Possibly Parallel Threads
- System error 53 has occurred. The network path was not found. After moving working system to a new domain.
- Obtaining Midas and splice index values in onechannelGUI
- [R-pkgs] new package 'midasr'
- Enterprise Database Tier (XA transactions, COBRA and MIDAS)
- Local delivery via deliver fails for 1 user in alias