I updated all my servers to 3.0.25 early this morning. Everything seems 100% A-OK except for the most surprising thing, all my Windows and Macintosh clients, no problems. But I'm having severe difficulty with the 3.0.25 smbclient. If I use smbclient from 3.0.24 it too can connect to my 3.0.25 servers without issue. Its bizarre. Before I go into it let me say, I've got some 3.0.25 servers in share level security and the 3.0.25 smbclient CAN connect to those just fine. But, I've got other servers using security = domain and those are the ones 3.0.25 smbclient can't connect to, in general. Its very very strange because I've tested with 4 seperate userids. 3 of the userids will not work using 3.0.25 client period, 1 of them always will, I can't put my finger on anything that might be different about that 1 userid but its consistent even to different servers. Again, using 3.0.24 client I can connect to any of the 3.0.25 servers using any of the 4 userids no problem. So, is this a known issue or should I file a bug report, or any suggestions on what to try?? Thankyou, Tom Schaefer
I updated all my servers to 3.0.25 early this morning. Everything seems 100% A-OK except for the most surprising thing, all my Windows and Macintosh clients, no problems. But I'm having severe difficulty with the 3.0.25 smbclient. If I use smbclient from 3.0.24 it too can connect to my 3.0.25 servers without issue. Its bizarre. Before I go into it let me say, I've got some 3.0.25 servers in share level security and the 3.0.25 smbclient CAN connect to those just fine. But, I've got other servers using security = domain and those are the ones 3.0.25 smbclient can't connect to, in general. Its very very strange because I've tested with 4 seperate userids. 3 of the userids will not work using 3.0.25 client period, 1 of them always will, I can't put my finger on anything that might be different about that 1 userid but its consistent even to different servers. Again, using 3.0.24 client I can connect to any of the 3.0.25 servers using any of the 4 userids no problem. So, is this a known issue or should I file a bug report, or any suggestions on what to try?? Thankyou, Tom Schaefer