Hi all, I used to run Samba 2.2.9 on Debian Woody. Yesterday I upgraded it (with all necessary packages) to 3.0.7. Since then, Samba on that server do not respond to netbios queries, only to direct access via IP. Also, when I try to resolv its name using nmblookup, I cannot find it. When I access to server via IP address everything works fine. Any idea ? TIA -- Eng. Dusan Djordjevic (RHCE)
> When I access to server via IP address everything works fine.Maybe nmbd doesn't get started?
Dusan Djordjevic wrote:>Hi all, > >I used to run Samba 2.2.9 on Debian Woody. Yesterday I upgraded it (with >all necessary packages) to 3.0.7. Since then, Samba on that server do >not respond to netbios queries, only to direct access via IP. Also, >when I try to resolv its name using nmblookup, I cannot find it. > >When I access to server via IP address everything works fine. > >Any idea ? >TIA > >That problem almost drive me wild. I had a problem with White Box EL 3 (RHEL3 in fact) when I upgraded it to 3.0.6, the problem was about kerberos tickets. The enviroment was a 2000 SP2 hybird PDC and linux machine was just a member. I tried recently with version 3.0.7 wich the RPM package from samba.org, what was suposed to solve that problem, but still failed. Solution, Downgrade to original distro samba version. 3.0.0. Now everything working right. If you don't want a downgrade, and the PDC is working in hybrid mode, just try RPC join to the domain, not ADS. Good luck, and better if you provide more info about your enviroment and your samba configuration. Greetings, David Ferreira
Good Morning Dusan, This sounds similar to a problem I had earlier when upgrading a server and it involved WINS registration. Here is what I did to fix my problem: http://lists.samba.org/archive/samba/2004-September/092466.html Hope this helps, Stuart ----- Original Message ----- From: "Dusan Djordjevic" <dj.dule@beotel.yu> To: <samba@lists.samba.org> Sent: Friday, October 01, 2004 8:34 AM Subject: [Samba] Server not responding after Samba upgrade> Hi all, > > I used to run Samba 2.2.9 on Debian Woody. Yesterday I upgraded it (with > all necessary packages) to 3.0.7. Since then, Samba on that server do > not respond to netbios queries, only to direct access via IP. Also, > when I try to resolv its name using nmblookup, I cannot find it. > > When I access to server via IP address everything works fine. > > Any idea ? > TIA > -- > Eng. Dusan Djordjevic (RHCE) > -- > To unsubscribe from this list go to the following URL and read the > instructions: http://lists.samba.org/mailman/listinfo/samba
On Friday 01 October 2004 06:19, Stuart Highlander wrote:> Good Morning Dusan, > > This sounds similar to a problem I had earlier when upgrading a server and > it involved WINS registration. > > Here is what I did to fix my problem: > > http://lists.samba.org/archive/samba/2004-September/092466.htmlI just checked this reference. Please note that it is nmbd that maintains the wins.dat and browse.dat files - NOT smbd. - John T.> > Hope this helps, > > Stuart > > ----- Original Message ----- > From: "Dusan Djordjevic" <dj.dule@beotel.yu> > To: <samba@lists.samba.org> > Sent: Friday, October 01, 2004 8:34 AM > Subject: [Samba] Server not responding after Samba upgrade > > > Hi all, > > > > I used to run Samba 2.2.9 on Debian Woody. Yesterday I upgraded it (with > > all necessary packages) to 3.0.7. Since then, Samba on that server do > > not respond to netbios queries, only to direct access via IP. Also, > > when I try to resolv its name using nmblookup, I cannot find it. > > > > When I access to server via IP address everything works fine. > > > > Any idea ? > > TIA > > -- > > Eng. Dusan Djordjevic (RHCE) > > -- > > To unsubscribe from this list go to the following URL and read the > > instructions: http://lists.samba.org/mailman/listinfo/samba-- John H Terpstra Samba-Team Member Phone: +1 (650) 580-8668 Author: The Official Samba-3 HOWTO & Reference Guide, ISBN: 0131453556 Samba-3 by Example, ISBN: 0131472216 Hardening Linux, ISBN: 0072254971 OpenLDAP by Example, ISBN: 0131488732 Other books in production.
> I used to run Samba 2.2.9 on Debian Woody. Yesterday I upgraded it > (with all necessary packages) to 3.0.7. Since then, Samba on that > server do not respond to netbios queries, only to direct access via > IP. Also, when I try to resolv its name using nmblookup, I cannot > find it. > > When I access to server via IP address everything works fine.Hi again, Yet I did not solved problem. I noticed one thing. Although nmbd is running (it exists as process), swat says it is not running. So most probably problem is with nmbd, but i do not know what to try. -- Eng. Dusan Djordjevic (RHCE)
Dusan Djordjevic wrote:>>I used to run Samba 2.2.9 on Debian Woody. Yesterday I upgraded it >>(with all necessary packages) to 3.0.7. Since then, Samba on that >>server do not respond to netbios queries, only to direct access via >>IP. Also, when I try to resolv its name using nmblookup, I cannot >>find it. >> >>When I access to server via IP address everything works fine. >> >> > >Hi again, > >Yet I did not solved problem. I noticed one thing. Although nmbd is >running (it exists as process), swat says it is not running. So most >probably problem is with nmbd, but i do not know what to try. > > >Did you tried to startup manually from command prompt? Just try to run as root nmbd -D and see what happen. Good Luck. David Ferreira
On Monday 04 October 2004 09:54, David Ferreira wrote:> Dusan Djordjevic wrote: > >>I used to run Samba 2.2.9 on Debian Woody. Yesterday I upgraded it > >>(with all necessary packages) to 3.0.7. Since then, Samba on that > >>server do not respond to netbios queries, only to direct access via > >>IP. Also, when I try to resolv its name using nmblookup, I cannot > >>find it. > >> > >>When I access to server via IP address everything works fine. > > > >Hi again, > > > >Yet I did not solved problem. I noticed one thing. Although nmbd is > >running (it exists as process), swat says it is not running. So most > >probably problem is with nmbd, but i do not know what to try. > > Did you tried to startup manually from command prompt? Just try to > run as root nmbd -D and see what happen.Yes, it starts in that case also. Problem is that, although process exists, it is not working properly. -- Eng. Dusan Djordjevic (RHCE)
Dusan Djordjevic wrote:>>did you have on your smb.conf any of this parameters? >>dns proxy >>wins proxy >>wins server >>wins support >> >> > >I have plain workgroup. For testing purposes, I have samba on >problematic server and only one Win XP client (not SP2). I also use my >laptop with linux for testing. > >Logs do not show anything problematic. Everything works fine. When I try >to resolve some other machine name from that problematic server, it >works. No firewalls or anything similar. Nothing of that settings up >there. In browse list, in /var/cache/samba/browse.dat nmbd writes name >of workgroup and server itself, but it cannot resolve its own name. >winbind is not running, i do not need it in workgroup. > >Have you tried adding "use sendfile = no" in your smb.conf? have you added wins in /etc/nsswitch.conf in section "hosts:"?
On Monday 04 October 2004 16:10, David Ferreira wrote:> Dusan Djordjevic wrote: > >>did you have on your smb.conf any of this parameters? > >>dns proxy > >>wins proxy > >>wins server > >>wins support > > > >I have plain workgroup. For testing purposes, I have samba on > >problematic server and only one Win XP client (not SP2). I also use > > my laptop with linux for testing. > > > >Logs do not show anything problematic. Everything works fine. When I > > try to resolve some other machine name from that problematic > > server, it works. No firewalls or anything similar. Nothing of that > > settings up there. In browse list, in /var/cache/samba/browse.dat > > nmbd writes name of workgroup and server itself, but it cannot > > resolve its own name. winbind is not running, i do not need it in > > workgroup. > > Have you tried adding "use sendfile = no" in your smb.conf? have you > added wins in /etc/nsswitch.conf in section "hosts:"?I think i found a problem. Since I run samba on virtual interface, i use options: interfaces = 192.168.0.50 127.0.0.1 bind interfaces only = Yes socket address = 192.168.0.50 When I disable socket address, everything works normally. -- Eng. Dusan Djordjevic (RHCE)