Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I have configured successfully samba-2.0.5 package for my redhat 9 system.
I am getting the smbd and nmbd daemons.On my system already samba-2.2.7a is running,i have copied the smbd and nmbd daemons to /usr/bin directory.When i am running "smbd -V" command,i am getting 2.0.5 version.
But when i am running : ./smbd & for background process.And i am checking with "ps -ax" command,i am getting like this:
19998 pts/5 R 0:00 ps -ax
[1]+ Exit 255 ./smbd
I am not able to run smbd and nmbd daemons on my system.
when i am trying with "smbclient",ia m getting the below given message:
smbclient \\\\192.168.1.4\\data
added interface ip=192.168.1.4 bcast=192.168.1.255 nmask=255.255.255.0
error connecting to 192.168.1.4:139 (Connection refused)
Error connecting to 192.168.1.4 (Connection refused)
Connection to 192.168.1.4 failed
[1]+ Exit 255 ./smbd
I have tried with other command also,but getting the same message:
[root@localhost bin]# smbclient '//192.168.1.4//home' -U keerti
added interface ip=192.168.1.4 bcast=192.168.1.255 nmask=255.255.255.0
error connecting to 192.168.1.4:139 (Connection refused)
Error connecting to 192.168.1.4 (Connection refused)
Connection to 192.168.1.4 failed
Stop right there. Why are you running an unsupported ancient version of Red Hat? Your version of Samba is very old as well.
You should upgrade to a newer version of Linux such as the latest Fedora Core or RHEL.
Also, it seems you are running the samba server manually. Use your service dialog or chkconfig to start the service. Also check your firewall settings for ports 445 & 139. If your version of samba uses broadcast based browsing, then you may need ports 137/udp & 138/udp open as well.
Stop right there. Why are you running an unsupported ancient version of Red Hat?
Time and time again I see people on here asking questions about RedHat 9, often saying that they have just installed it. Several times I've asked them why it is that they have just installed a distro that is utterly obsolete and went end of life years ago. No one has yet given a reason.
I could be wrong, but most seem to be based in / around India... Must have been some major CD sharing at some point I guess. Possibly the first serious version of Linux to hit India?
Thanks for your posts.
The reason for using samba-2.0.5,the size of smbd is 745k and nmbd is about 250k.I am going to use that on my Embedded linux device which is having a flash size of 4MB(its onboard).My bootloader size is about 128k and kernel size is about 1.8MB(including the device drivers which i require).The minimal size of filesystem is around 2Mb including the samba daemons which i have got from samba-2.0.5.
Any more clarifications from your side are welcomed.
I am using Fedora 7 and Mandriva 2008 on my systems.For this project itself i am using samba-2.0.5,i know its an older version,but for me the flash size matters most and i know there will be security issues.
Also i have tried the other version of samba-3.0.24,but the size of smbd and nmbd is to bigger that could not fit onto the free space that I have on the flash.
Does anyone have any idea on how to reduce the size of these (smbd,nmbs and smbpasswd) binaries?
Any suggestions about where to strip off unnecessary code in samba that will not be required for a embedded solution?
ravi_chobey: Thank you for your explanation. Since this is an embedded device you are using, it probably has so much stripped off that it isn't even Red Hat any more. I have read several posts about RH9 and they actually tend to be from India. So your post seems to fit a pattern we have seen many times before.
I had thought the it would be because of poor dialup service & a RedHat bible being available in the bookstores. As slow as our service is compared to Japan or Korea, many people are even worse off.
---
Check if your device is firewalling off one of the ports needed. Also, install the samba-doc package on one of your own systems (eg Fedora or Mandriva). IIRC, the Samba 3 HOWTO & Reference guide book provided has a chapter on migrating from Samba 2 to Samba 3 and may indicate what new features are supported.
Does your client depend on such a feature? For example, your clients may be using ports 119 & 445 when your server uses 118-119 broadcasts. Also look at whether NTLMV2 is supported by the Samba 2 device. Some missing features could require changes in how the clients are configured.
---
I have developed my filesystem by configuring buildroot,It takes around 45 minutes to build my root filesytem,the samba which i am getting in that buildroot package is 3.0.24 version and the size of smbd is 850kB.
But i have taken samba-3.0.24 alone,the smbd size was around 3.0 MB.
I am not able to get why is there so much diference between two SMBDs of same samba package.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.