Unable to see netbios name of linux server
Hi! I just experienced a Suse linux server that wouldn't start. First I thought it was a hardware failure on the system disk, which turned out to be wrong. During my search for the cause of this malfunction, I also ran Knoppix. Eventually a BIOS update was all that was needed. When I got Suse running again, it just won't broadcast it's NetBios name 'SIBMASTER' to the other computers on the network. I can see the router in 'attached devices' on my router, but it is named 'UNKNOWN NAME'. It is also only possible to connect to the server using it's IP-address. We are using the workgroup name SIB. I did a grep -r SIBMASTER * in /etc to see where the name SIBMASTER was located. I found it in the following files with the row it was on: /etc/HOSTNAME SIBMASTER (I've also tried SIBMASTER.SIB here) /etc/hosts 192.168.0.2 SIBMASTER.SIB SIBMASTER etc.. /etc/postfix/main.cf myhostname = SIBMASTER.SIB /etc/samba/smb.cnf netbios name = SIBMASTER So, why isn't the name of the server broadcasted to my router or any other computer on the network? Any tips on what I should look for? Thanks in advance! / Peter
Peter Hartlén wrote:
When I got Suse running again, it just won't broadcast it's NetBios name 'SIBMASTER' to the other computers on the network. I can see the router in 'attached devices' on my router, but it is named 'UNKNOWN NAME'. It is also only possible to connect to the server using it's IP-address.
Is nmbd running? Check the logs!
So, why isn't the name of the server broadcasted to my router or any other computer on the network?
Is nmbd running?
Any tips on what I should look for?
Check the logs! They are the admins best friends when debugging! Sandy -- List replies only please! Please address PMs to: news-reply2 (@) japantest (.) homelinux (.) com
Hi Sandy, thanks for your reply! I ran ps -ax|grep mdb and I couldn't find nmbd in the list of running processes, only 4 instances of smbd. Shouldn't nmbd start when samba is started? I wouldn't mind checking the logs, but honestly, I don't know where to look *blush*. What logs could be of interest here? Anyhow, if I wasn't using samba at all, shouldn't the hostname be found anyway? Regards, Peter -----Original Message----- From: Sandy Drobic [mailto:suse-linux-e@japantest.homelinux.com] Sent: Thursday, December 29, 2005 10:34 AM To: suse-linux-e@suse.com Subject: Re: [SLE] Unable to see netbios name of linux server Peter Hartlén wrote:
When I got Suse running again, it just won't broadcast it's NetBios name 'SIBMASTER' to the other computers on the network. I can see the router in 'attached devices' on my router, but it is named 'UNKNOWN NAME'. It is also only possible to connect to the server using it's IP-address.
Is nmbd running? Check the logs!
So, why isn't the name of the server broadcasted to my router or any other computer on the network?
Is nmbd running?
Any tips on what I should look for?
Check the logs! They are the admins best friends when debugging! Sandy -- List replies only please! Please address PMs to: news-reply2 (@) japantest (.) homelinux (.) com -- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
Peter Hartlén wrote:
Hi Sandy, thanks for your reply!
I ran ps -ax|grep mdb and I couldn't find nmbd in the list of running processes, only 4 instances of smbd. Shouldn't nmbd start when samba is started?
Yes, normally it should start without any need to kick it up manually.
I wouldn't mind checking the logs, but honestly, I don't know where to look *blush*. What logs could be of interest here?
System messages like failed services are usually shown in /var/log/messages and often in the log where the server application logs its events. If you are using the default out-of-the-box samba packages (you still haven't told what version of Suse you used or if you installed a third-party rpm or even compiled your own version), then I would expect the log to be placed in /var/log/samba. I have logs for smb, nmb and winbind (only if the linux server is a member of a windows domain) in our company.
Anyhow, if I wasn't using samba at all, shouldn't the hostname be found anyway?
Sure, if you want to have a dns or host file based resolution. Unfortunately, Windows uses yet another protocol to look up names in a windows workgroup and thus falls flat on the face if nmb isn't playing along. Sandy -- List replies only please! Please address PMs to: news-reply2 (@) japantest (.) homelinux (.) com
Thanks, you're my hero of the day :) In /var/usr/samba/ I checked the log for nmbd and there it was: "Failed to open nmb socket on interface 192.168.1.1 for port 137." The IP of my server is 192.168.0.2 and the router has 192.168.0.1, in smb.conf however, this line was present: Interfaces = 192.168.0.1/24 192.168.1.1/24 I know we previously connected a subdomain using VPN through our router, and this subdomain used 192.168.1, but we are not using this anymore so I believe removing 192.168.1.1/24 would be safe. I did this and restarted samba, I then tried to start nmbd again. I know got a similar error but instead of 192.168.1.1 it said 192.168.0.1. As I honestly don't know what the "Interfaces" setting does (maybe someone want/can explain), I changed it to the IP of the server (instead of router), after some hints on the www. After that, everything works like a charm! What is the Interfaces setting in smb.conf used for? (do I need it) and should it be set to the computer IP or? Thanks, Peter -----Original Message----- From: Sandy Drobic [mailto:suse-linux-e@japantest.homelinux.com] Sent: Thursday, December 29, 2005 12:01 PM To: suse-linux-e@suse.com Subject: Re: [SLE] Unable to see netbios name of linux server Peter Hartlén wrote:
Hi Sandy, thanks for your reply!
I ran ps -ax|grep mdb and I couldn't find nmbd in the list of running processes, only 4 instances of smbd. Shouldn't nmbd start when samba is started?
Yes, normally it should start without any need to kick it up manually.
I wouldn't mind checking the logs, but honestly, I don't know where to look *blush*. What logs could be of interest here?
System messages like failed services are usually shown in /var/log/messages and often in the log where the server application logs its events. If you are using the default out-of-the-box samba packages (you still haven't told what version of Suse you used or if you installed a third-party rpm or even compiled your own version), then I would expect the log to be placed in /var/log/samba. I have logs for smb, nmb and winbind (only if the linux server is a member of a windows domain) in our company.
Anyhow, if I wasn't using samba at all, shouldn't the hostname be found anyway?
Sure, if you want to have a dns or host file based resolution. Unfortunately, Windows uses yet another protocol to look up names in a windows workgroup and thus falls flat on the face if nmb isn't playing along. Sandy -- List replies only please! Please address PMs to: news-reply2 (@) japantest (.) homelinux (.) com -- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
participants (2)
-
Peter Hartlén -
Sandy Drobic