cant start nmbd in SWAT or Samba
 

hi all
I got a problem ....... I cant start nmbd, I can start SMB and I dont know what's wrong ( I'm only a newbe to linux)

below is what is listed in the log.nmbd file in my system


[2003/08/07 00:51:22, 0] nmbd/nmbd.c:main(794)
Netbios nameserver version 2.2.7a-security-rollup-fix started.
Copyright Andrew Tridgell and the Samba Team 1994-2002
[2003/08/07 00:51:22, 0] nmbd/nmbd_subnetdb.c:create_subnets(239)
create_subnets: No local interfaces !
[2003/08/07 00:51:22, 0] nmbd/nmbd.c:main(872)
ERROR: Failed when creating subnet lists. Exiting.


hopefully some one can help as this is driving me nuts

thank U
JC

Re: cant start nmbd in SWAT or Samba
 

Is your NIC configured and working?

What does your smb.conf file look like?

-What happens if you open a terminal window and type tail -f /var/log/message and then open another window and try and start samba ?
(On redhat the correct way to do that is /sbin/service smb start; The difference between /etc/init.d/smb start I won't know.)

-What does your resolv.conf file look like?

-Are you able to comunicate at the IP level with other machines on your network can you ping them ssh into your linux machine from the other machines on your network?

-Do you have any iptables rules ? Is iptables running ?

thanks all for your help ........ regarding My NIC I'm using mandrake 9.1 and im using the wizzard to install and detect the card but I still cant ping it........... I tought linux should auto detect the card and it seems to but it because I can ping the loopback address and the ping seems to work, when I ping my laptop then the It cant get to the laptop ........... any suggestions would be helpfull.

pinging the loopback address means nothing. I was able to picg 127.0.0.1 even though the computer had no NIC at all. The reason that the loopback address still works is that it is an interface by itself, not dependent on any other hardware or drivers. This is nessesary because many Linux applications use the loopback address to communicate within itself. For example the X window system uses a client/server arcitecture, as does the XFS (X Font Server).

From what you've told us i'm guessing that the NIC has not been properly configured. Some NICs work fine with Linux and PnP but others were built with Windows in mind and will never work with Linux. Please post the manufacturer and the model name/number of the NIC that you're trying. And if you can still return it, try getting the Linksys LNE100TX (I've found it's easily compatible with Linux)