LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware (http://www.linuxquestions.org/questions/slackware-14/)
-   -   Slackware64-C client wont detect Slackware64-C Samba server (http://www.linuxquestions.org/questions/slackware-14/slackware64-c-client-wont-detect-slackware64-c-samba-server-745161/)

slackass 08-04-2009 09:50 PM

Slackware64-C client wont detect Slackware64-C Samba server
 
Fresh install and updated Slack64-Current 08_04_09 non-official build wont detect Slack64 Samba but will detect the Windows XP Samba server.

Server box:
Dual boot
Windows XP home 32 setup as a Samba server on 1 st drive.
Slackware64 setup as Samba server 2nd drive.

Client 1
Slackware64 -Current 08_04_09 non-official build
Will detect Windows Samba only

Bluewhite64-Current RC2
Detects both Slack64 & Windows Samba servers

Slamd64 12.2
Detects both Slack64 & Windows Samba servers

Client 2
This is a old install of Slack64-C that was installed the week the 64-C went public and has not had any updates. I cant update this machine because it's my wife's and she don't know it's a “testing distro” and there will be hell to pay if I screw it up before Slack64 13 comes out.
Detects both Slack64 & Windows Samba servers

Client 3
My Media Box (wireless / wicd)
This is a old install of Slack64-C that was installed the week the 64-C went public and is kept completely updated.
Detects both Slack64 & Windows Samba servers

Also, Debian Live DVD detects the Slack64 Samba server.
I tried a reinstall – no luck.
Bug maybe, that will get fixed before 13 comes out?

Alien Bob 08-05-2009 02:42 AM

You have to be more precise than this. What commands/programs do you use to test this? What are the errors? How was the Samba server configured?

And what does "08_04_09 non-official build" mean?

Eric

slackass 08-05-2009 11:29 AM

Hi Eric!
Thanks for the response.
The server was setup using your “Excellent” guide.
I don't think there's anything wrong with it because every box in the house can find it with the exception of “new” Slack-Current installs. (32 and 64)
Earlier Slack64 installs connect to the Linux Samba just fine.

The clients had no special setup because they all connected automatically with dolphin or konqueror with just a “point & click” and then enter user name & password.


"08_04_09 non-official build" refers to the .iso I downloaded @:
ftp://ftp.slackware.no/pub/linux/ISO...ent-ISO-build/


The error code I get is:
Timeout on server Mygroup

I should also mention that both Slamd64 12.2 as well as Slamd64 -C also connect to the server automatically with dolphin or konqueror with just a “point & click” and then enter user name & password.

Also:
There's no big panic on my end to fix this because I have no real use for Samba other than an old dog learning new tricks.
I was just looking for something to learn one night and found your Samba guide which worked perfect for me.
Thanks for all of your guides btw!

The only reason I posted this was I thought maybe the Slack-Team might be unaware of this. I completely realize that this is a “testing distro” and some things won't work as expected.

Alien Bob 08-05-2009 03:21 PM

I just tried to connect to my old Samba server (running on Slackware 10) using dolphin on Slackware64 (a -current install of about three weeks old - up to and including the updates from "Sat Jul 11 18:31:32 CDT 2009" which means I still run a 2.6.29.5 kernel).

I could browse to a share that needs authentication. I got the dialog asking for name/password, entered those and could then browse the content of that share without any problems.

Perhaps yoour Samba server has a setting that is not, or no longer, compatible with modern-day Samba clients? Or the cifs module in the 2.6.29.6 kernel is different, but I really doubt that.

Eric

slackass 08-05-2009 04:22 PM

Quote:

Originally Posted by Alien Bob (Post 3632696)
I just tried to connect to my old Samba server (running on Slackware 10) using dolphin on Slackware64 (a -current install of about three weeks old - up to and including the updates from "Sat Jul 11 18:31:32 CDT 2009" which means I still run a 2.6.29.5 kernel).

I could browse to a share that needs authentication. I got the dialog asking for name/password, entered those and could then browse the content of that share without any problems.

Perhaps yoour Samba server has a setting that is not, or no longer, compatible with modern-day Samba clients? Or the cifs module in the 2.6.29.6 kernel is different, but I really doubt that.

Eric

That makes sense.
I'll do a hose & reload on the server tonight and setup samba anew and see if I can learn something.
Thanks!

slackass 08-08-2009 12:23 AM

Ok, I found the bug, it was me.
I was using a host name that was also on another box. :-(


All times are GMT -5. The time now is 07:34 AM.