samba - Apr 2001 - Samba v2.2.0 and default hidden shares

OS:  Solaris 8 Sparc

I'm new to this mailing list, so you might have seen the same questions
before.  I have several questions to ask.

First off, Samba v2.0.7, I didn't have problems connecting to
//HOSTNAME/C$ via the smbclient.  On v2.2.0, however, everytime I try to
connect to the hidden share, I get the following error:

session setup failed: ERRDOS - ERRnoaccess (Access denied.)

That happens right after I type the password.  I'm not sure if the new
client is having problems with the username or the password -- maybe,
they're too long?  It works with the older smbclient from v2.0.7,
though.  That's why I am perplexed.

Another question.  Whenever, I try to access an object on my Samba
server, it appears to take quite awhile.  For instance, if I open
Windows Explorer, and go to my Samba server, and right click on a file,
it'll set there for at least 30 seconds, before it gives me the menu to
cut or copy the file.  Then, when I've selected copy, for instance, and
I go to a directory on the Windows box, and paste, it'll sit there for
another 30 seconds or so, before it copies the file.  Once the copy
process gets started, the data is transferred quickly.  This also
happened in v2.0.7.

Thanks in advance!


--
Internet: wfielder@ev1.net


-------------- next part --------------
HTML attachment scrubbed and removed

Wavelen Warren Fielder II wrote:
>Another question.  Whenever, I try to access an object on my Samba
>server, it appears to take quite awhile.  For instance, if I open
>Windows Explorer, and go to my Samba server, and right click on a file,
>it'll set there for at least 30 seconds, before it gives me the menu to
>cut or copy the file.  Then, when I've selected copy, for instance, and
>I go to a directory on the Windows box, and paste, it'll sit there for
>another 30 seconds or so, before it copies the file.  Once the copy
>process gets started, the data is transferred quickly.  This also
>happened in v2.0.7.
If you're using DNS, make sure everything is set up properly, especially
your reverse lookup. I've seen many network delays caused by poorly set
up reverse DNS. Does the same behaviour occur when you telnet, ftp or
ssh to the server? If so, the problem is almost certainly reverse DNS.
What happens is the server is doing a reverse lookup on the IP address
to get a reliable host name for its logs. If there's no reverse DNS set
up, it will time out (about 30 seconds) and then use the IP address in
the logs.

-Bill