I've been running Samba3.0.21a on two AIX5.3 servers for several weeks
with no major problems. Today, one of the servers stopped working. I
received the following message from Windows when I tried to access one of
the share drives:
An error occurred while reconnecting T: to \\wara01\TSMreports
Microsoft Windows Network: This local device name is already in use
This connection has not been restored
I received this error a couple of times before. But when I cleared out
the logs and refreshed the inetd daemon the problem was resolved. However,
that did not work today. I went through all the troubleshooting steps
and have concluded the following:
- Networking software is working
- TCP with FTP is working
- Samba daemons (nmbd & smbd) are running
- The daemons are bound to ports (netstat -a )
- inetd.conf lines are correct
netbios-ssn stream tcp nowait root
/opt/Samba/3.0.21a/sbin/smbd smbd
netbios-ns dgram udp wait root
/opt/Samba/3.0.21a/sbin/nmbd nmbd
- smbd works with telnet
- testparm shows no error messages
The following is where I encountered problems :
/opt/Samba/3.0.21a/bin > ./smbclient -L localhost -U%
Domain=[NA2] OS=[Unix] Server=[Samba 3.0.21a]
tree connect failed: Call timed out: server did not respond after
20000 milliseconds
/opt/Samba/3.0.21a/bin > ./smbclient '\\wara01\root'
session request to WARA01 failed (Call timed out: server did not
respond after 20000 milliseconds)
Password:
Domain=[NA2] OS=[Unix] Server=[Samba 3.0.21a]
tree connect failed: Call timed out: server did not respond after
20000 milliseconds
C:\>net use \\wara01\root
System error 121 has occurred.
The semaphore timeout period has expired.
C:\>net view \\wara01
System error 121 has occurred.
The semaphore timeout period has expired.
I can't find any help for these particular error messages in
ch12.html#samba webpage. I would appreciate any advice anyone has to
offer.
Thanks
Earl
On Thu, 16 Feb 2006, earl.rose@us.aonwarranty.com wrote:> I've been running Samba3.0.21a on two AIX5.3 servers for several weeks > with no major problems. Today, one of the servers stopped working. I > received the following message from Windows when I tried to access one of > the share drives: >What does "oslevel -r" report?
On Thu, 16 Feb 2006, earl.rose@us.aonwarranty.com wrote:> > An error occurred while reconnecting T: to \\wara01\TSMreports > Microsoft Windows Network: This local device name is already in use > This connection has not been restored > > I received this error a couple of times before. But when I cleared out > the logs and refreshed the inetd daemon the problem was resolved. However, > that did not work today. I went through all the troubleshooting steps > and have concluded the following: > - Networking software is working > - TCP with FTP is working > - Samba daemons (nmbd & smbd) are running > - The daemons are bound to ports (netstat -a ) > - inetd.conf lines are correct > netbios-ssn stream tcp nowait root > /opt/Samba/3.0.21a/sbin/smbd smbd > netbios-ns dgram udp wait root > /opt/Samba/3.0.21a/sbin/nmbd nmbd > - smbd works with telnet > - testparm shows no error messages >I've not had a log of success with inetd controlling access to Samba. You should either script the nmbd and smbd startup or use swat. smbd will fork children as necessary. You may also want to look at 3.0.21b based on the release note entries alone. Cheers, Bill