OS2 World.Com Forum

Subject  :  New Samba Issue
Author  :  GrandPa gene.poole@fds.com
Date  :  02 Nov, 2005 on 22:41
I've a box running Fedora Core 3 with Samba 3.0.x and I could connect to the samba shares from both my WinXP and eCS 1.00 boxes.
I upgraded the eCS box to the latest fixes and patches (1.05). All the latest fixpaks, patches, fixes, etc.
Now I can no longer connect to the samba shares (the WinXP box works fine) from the eCS box.
Does anyone have any ideas?

Gene


Subject  :  Re:New Samba Issue
Author  :  Pete losepete@ntlworld.com
Date  :  03 Nov, 2005 on 16:28

GrandPa (02 Nov, 2005 22:41):
I've a box running Fedora Core 3 with Samba 3.0.x and I could connect to the samba shares from both my WinXP and eCS 1.00 boxes.
I upgraded the eCS box to the latest fixes and patches (1.05). All the latest fixpaks, patches, fixes, etc.
Now I can no longer connect to the samba shares (the WinXP box works fine) from the eCS box.
Does anyone have any ideas?

Gene



Hi

Just a couple of thpughts..


I have a Linksys NSLU2 - attaches a usb drive to the network, makes it network accessible storage - which uses an embedded linux with samba installed.

It used to connect fine to my eCS systems - 1.04,1.14,1.25 - but then Linksys released a new firmware that resolved lots of other issues but also updated the (working) samba v2.x.x to 3.0.11.

Now it is not possible to connect to the NSLU2 using File and Print Client graphical interface.

It is still possibe to access the device via a command line and applications can still use mapped drives - just not through the F&P graphical interface.

The answer I seem to have come up with after some emails with samba.org and newsgroup postings is that early samba 3 does not pay any attention to EAs.

The problem was resolved in samba 3.016 - current samba is 3.0.20 which respondents in eCS and OS/2 newsgroups confirm works.


I am a bit surprised that it was working OK before applying eCS updates if the samba you have installed is somewhere in versions 3.0.1 to 3.0.15 inclusive...


So, while I am coming at this from the other end I suspect the problem is the same and that 3.0.20, or whatever the current build now is, should resolve it.


I guess there is the possibility that you already have a later samba installed in which case I guess I would sart looking at users, shares and access rights etc as it is possible that the eCS update may have mangled something.

Hope something above helps

Pete


Subject  :  Re:New Samba Issue
Author  :  GrandPa gene.poole@fds.com
Date  :  04 Nov, 2005 on 17:01
Thanks, I'll look into upgrading the Samba on the Linux box.
Gene

Subject  :  Re:New Samba Issue
Author  :  GrandPa gene.poole@fds.com
Date  :  21 Nov, 2005 on 19:57
Check this! It wasn't a Linux, Samba, or Warp issue. It was a bad NDIS driver for the LinkSys LNE100TX NIC. I found a updated driver and now all is well.

Powered by UltraBoard 2000 <www.ub2k.com>