well chris, I have changed my security to user, and encrypt the passwds and path = /etc/smbpasswd and I now connect pretty darn fast. now. but that means that I have disregarded having the samba server authenticate back to the PDC, which, is what I really wanted. but oh well. hey it works right? hahaha Chris Herrmann wrote:> > **discflo is the domain name, I think I either read it in the man pages > for smb.conf or in my samba book. > > If it's not working i'd be cautious of it. Usually you'd specify it by > xxx.xxx.xxx.xxx/subnetmask > > > ; remote browse sync = 192.168.3.25 192.168.5.255 > > ** what are the ip's used here? I know that .255 is the braodcast > address, but what is the other one? > > Not sure - sorry! > > ****** ok regarding broken pipes.....I have alot of those in my > machione.log files > and I have some other errors as follows... I also have log files for > machines that are not set up to log in..... > > [2001/01/22 15:57:17, 0] smbd/process.c:timeout_processing(868) > Reloading services after SIGHUP > [2001/01/22 16:26:06, 0] lib/util_sock.c:read_socket_data(507) > read_socket_data: recv failure for 4. Error = No route to host > > Ok, we get similar problems. It happens because of the order that samba > tries to resolve the name of the client connecting to it - it takes too > long, and the client goes away before samaba can respond which is why you > get a broken pipe. We're trying a couple of things atm: > - dnscache, so that a reverse lookup on an internal IP will work and it > won't need to query an external server for something that doesn't exist... > - edit your hosts file, and add entries for your machines: > xxx.xxx.xxx.xxx netbios.domain.com netbios > > which means that pinging a netbios name should give you both the ip address, > and the fully qualified host name (ie. host + domain). > > Not sure if it works yet though - try and see how you go!!! > > The only other thing I've seen around that may be of assistance to you is a > comment i read somewhere that the password server should be specified as an > IP address, and not a netbios name. Again, I didn't try this, and couldn't > get security = server to work, so good luck!