I have a mix of Win2K machines Win98 and WinME in my backend connecting to SAMBA. The Win2K boxes connecting to SAMBA intermitently (usually first thing in the morning) get an error connecting to SAMBA after coming up from a Cold Boot state. After the boxes have booted in the Morning they can usually be powered down and brought back up throughout the day and NOT get the error. The error normally appears only FIRST thing in the Morning. ???wierd??? Here is the Error the Win2K boxes experience: An Error Occured Reconnecting e: to \\192.168.1.10\homes Microsoft Windows Network: The Semaphore Timeout Period has Expired Question: is this a Samba configuration error or a Win2K configuration error. The 98 and ME connect just fine to SAMBA. SMB.CONF file contents: [root@ourfaircity /root]# cat /etc/samba/smb.conf # Samba config file created using SWAT # from localhost.localdomain (127.0.0.1) # Date: 2001/09/16 21:47:45 # Global parameters [global] netbios name = OURFAIRCITY server string = Samba Server interfaces = localhost 192.168.1.10/24 security = DOMAIN encrypt passwords = Yes map to guest = Bad User null passwords = Yes ssl CA certFile = /usr/share/ssl/certs/ca-bundle.crt debug level = 3 syslog = 3 log file = /var/log/samba/%m.log max log size = 0 socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192 dns proxy = No guest account = pcguest hosts allow = 192.168.1. [homes] comment = Home Directories path = /usr/pub writeable = Yes hosts allow = 192.168.1. -------------- next part -------------- HTML attachment scrubbed and removed