[Samba] Samba / Windows workgroup master browser problem

[Rich Pinder]

  Indeed.... But should samba be sending the packet to an address like 
that (the .255.255), or should it be sending it to the actual ip of the 
designated 'local browser' out there ??

r

richard wrote:

>Hi, I think this   might be the clue?
>***send_netbios_packet: send_packet() to IP 128.125.255.255 port 137
>failed
>regards,
>Richard Coates.
>
>On Fri, 2003-04-11 at 23:46, Rich Pinder wrote:
>  
>
>>I admit theres a LOT about the windows networking I dont understand - 
>>and even though this may NOT be a SAMBA issue per se, I thought I'd post 
>>it here.
>>
>>Have a 400gb samba server thats been working well (am upgrading to 
>>current patches today, btw).
>>I've got 3 Win2k workstations, on two subnets, that have drives mapped, 
>>and connect every morning on startup just fine.  All the machines belong 
>>to one workgroup.
>>
>>The way I have in the past added machines was to do a 'search' for the 
>>computer from the client machine.  After it finds the machine, I log in, 
>>and make the connection persistent for future logins.
>>
>>But recently I can't locate the samba server doing this search. 
>>
>>These messages in the samba log file are suspicious - it looks like no 
>>machine is acting like a local browser for the subnet  (??):
>>
>>[2003/04/10 04:01:08, 0] nmbd/nmbd_packets.c:send_netbios_packet(171)
>>  send_netbios_packet: send_packet() to IP 128.125.255.255 port 137 failed
>>[2003/04/10 04:01:08, 0] nmbd/nmbd_namequery.c:query_name(229)
>>  query_name: Failed to send packet trying to query name TEACHERS<1d>
>>[2003/04/10 04:02:00, 0] nmbd/nmbd.c:sig_hup(92)
>>  Got SIGHUP dumping debug info.
>>[2003/04/10 04:02:00, 0] nmbd/nmbd_workgroupdb.c:dump_workgroups(292)
>>  dump_workgroups()
>>   dump workgroup on subnet  128.125.61.148: netmask=    255.255.0.0:
>>        TEACHERS(1) current master browser = UNKNOWN
>>                ASDFZXCV 40019a03 (California Teachers Study)
>>
>>If anyone has a clue on this, I'd apreciate it !  I tried the following 
>>mods to my conf file, thinking it would force Samba to help out with 
>>defining the workgroup, but no luck:
>>
>>
>>os level = 34
>>local master = yes
>>remote announce = 128.125.61.255/SIMPLE 128.125.152.255/SIMPLE
>>
>>
>>Ok..thanks for the help
>>
>>Rich Pinder
>>USC School of Medicine
>>
>>
>>    
>>
>
>
>  
>