`hello
im running aix 6.1 as a lpar
on my aix im running smbd version 3.6.25
I'm experiencing an inability to connect to the server, \ hostname
And only after about 2 minutes, the connection is possible.
A phenomenon similar to stagnation.
Anyone have any ideas?
ths
I haven’t worked on smbd on AIX in years, but it was very finicky. The SMB protocol has all kinds of timeouts (for browsing names on the network, for caching credentials, and so on). Most likely you’re hitting some issue which causes the software to silently fail and then a timeout kicks it back into gear.
Debugging this kind of thing means turning on DEBUG level logging in smb.conf and digging through the output. A fairly deep understanding of the protocol is also needed. (And for some things, I had to resort to packet dumps using tcpdump/wireshark.)
There are some general debugging techniques (like using command line tools to test various components of the setup), but it’s been too long and I don’t remember them offhand. Google probably knows them, though (Google knows everything.)
Can you provide any more detail?? Do you get no error message when you first try to connect? Does it just hang?
After a 2 minute wait it will just immediately connect?
You are on the SMB client. Where is the server? Is it local?
If you ping the server with
ping <hostname>
do you get an immediate response? If not, perhaps there is an issue resolving the name, and that operation (to first DNS server) needs to timeout before it tries the second DNS server.
I'm not an AIX expert but I would suspect slow name resolution amonst other things.
`hello
ive try to connect from my pc station to \hostname\dirname
I'm not getting any error message.
ping command answer me quick.
the client and the server are in the same network , its local
after 2 minutes it will just immediately connect , im not do nothing .
It could have something to do with SMB1 and SMB2. I believe that Samba version 3.6 (from 2012) does not support SMB2 (Win10).
We have found with SCO, which also uses Samba version 3, that connecting using the ip address instead of the network name is more reliable. So: \\192.168.1.100\share, instead of \\servername\share.
Also, if you are using Win10, you can go to programs and features in control panel, and activate SMB1 protocol, and delete the auto SMB1 protocol delete feature.
AIX is wonderful - yeah.
LPAR’s are logical partitions on an even larger physical systems.
They may be shifting in and out of memory - yes ?
While you are short on many things at various times - make sure that this critical
Resource is mostly running -check the running specs of the liar.
It seems that you may have a fairly long timeout - due to lack of resources and the calling
System may have a fairly short timeout - so the initial request from the “outside” is not being serviced (at least while the LPAR gets its act together) and later on it may be serviced.
After a successful connection - you may find that most of the other calls to that SMB on that LPAR will work. However if there has been a quiet period. On the LPAR - you will get the problem.
DOES that happen for your system ?
KInd Regards
Helpful.