Something is very wrong, like conflicting DNS or inability to satisfy samba's name resolution, or a problem with authentication. Samba should be just about as fast as ftp.
There are a couple of different ways to solve the resolution and authentication problems depending on the size (and complexity) of the network and your specific security goals. At 11:00 PM 12/20/2001 Jim Beard <[EMAIL PROTECTED]> wrote: >Hey Folks, > > I saw that recent thread about memory and Samba, and I had a >general Samba usage question that I thought might be appropriate. We >recently migrated our file server at work from a crappy winblows box to >a nice RedHat distro. The RedHat box has RAID up and working so we >thought it would be best to handle the data. Lately we've been having >some usage issues. We made the RAID device available via Samba over the >network and sometimes we notice quite a bit of delay in accessing info. >When someone tries to open a directory it can take anywhere from 30 >seconds to a minute before they response comes back. Obviously this >kind of stuff gets annoying on a daily basis. Anyone had a similar >problem or advice? > >Jim > > >----------------------------------------------------------------------------- >Jim Beard Phone 541.484.9235 >Chief Engineer Fax 541.484.9193 >counterclaim.com http://www.counterclaim.com >----------------------------------------------------------------------------- >
