[Samba] WINS and cross-subnet

[neil]

well, my previous post below garnered no response, so here is a differnet 
version of my question:

i am on a campus with an existing wins server.
this server is working for windows clients, since they can browse across 
subnets. (or is there another way?)
i am using samba 2.2.1a on redhat linux intel 7.2 kernel 2.4.9-31
my smb.conf includes:
wins server = 192.168.2.138
hosts allow 192.168. 127.

my machine has ports 137, 138, 139 (tcp and udp on all three) unblocked

looking for a known, up, sharing machine with:

smbclient -d 8 -W GROUP -L KNOWN

gives:

added interface ip=192.168.91.97 bcast=192.168.91.255 nmask=255.255.255.0
added interface ip=127.0.0.1 bcast=127.255.255.255 nmask=255.0.0.0
Client started (version 2.2.1a).
resolve_lmhosts: Attempting lmhosts lookup for name KNOWN<0x20>
getlmhostsent: lmhost entry: 127.0.0.1 localhost 
resolve_hosts: Attempting host lookup for name KNOWN<0x20>
resolve_wins: Attempting wins lookup for name KNOWN<0x20>
wins_srv_count: WINS status: 1 servers.
  192.168.2.138 <192.168.2.138>: alive
resolve_wins: WINS server == <192.168.2.138>
bind succeeded on port 0
Sending a packet of len 50 to (192.168.2.138) on port 137
Sending a packet of len 50 to (192.168.2.138) on port 137
Sending a packet of len 50 to (192.168.2.138) on port 137
wins_srv_died(): WINS server 192.168.2.138 appears to be down.
name_resolve_bcast: Attempting broadcast lookup for name KNOWN<0x20>
bind succeeded on port 0
socket option SO_KEEPALIVE = 0
socket option SO_REUSEADDR = 1
socket option SO_BROADCAST = 1
Could not test socket option TCP_NODELAY.
socket option IPTOS_LOWDELAY = 0
socket option IPTOS_THROUGHPUT = 0
socket option SO_SNDBUF = 65535
socket option SO_RCVBUF = 65535
socket option SO_SNDLOWAT = 1
socket option SO_RCVLOWAT = 1
socket option SO_SNDTIMEO = 0
socket option SO_RCVTIMEO = 0
Sending a packet of len 50 to (192.168.91.255) on port 137
Sending a packet of len 50 to (192.168.91.255) on port 137
Sending a packet of len 50 to (192.168.91.255) on port 137
Sending a packet of len 50 to (127.255.255.255) on port 137
Sending a packet of len 50 to (127.255.255.255) on port 137
Sending a packet of len 50 to (127.255.255.255) on port 137
Connection to KNOWN failed

i do not want to resort to lmhosts on all clients.
the wins server is up, but only answers telnet on port 139 not 137
broadcast fails because KNOWN is on a different subnet, 192.168.92.x

if this is in TFM please point me to the right section or site or any 
documentation with specific wins port information et cetera. ive googled 
on it and dont come up with much at all...

i have played with this now and then for a few years, and never have any 
success. i believe i understand samba fairly well, and have used it 
successfully on other (private, isolated) subnets, but never got it 
working on this campus...

any ideas?

-neil

On Tue, 23 Apr 2002, neil wrote:

> hello all,
> 
> samba 2.2.1a on redhat linux 7.2 intel
> questions about WINS:
> i am on a campus with preexisting WINS servers, and so i should like to
> utilize them as their addresses are supplied to DHCP clients. when i tell
> nmbd about this WINS server the log shows nmbd trying to contact it but
> there is no response. using telnet i can only get a connection to
> these wins servers on port 139. shouldnt 137 be open? so my nmbd is
> constantly trying to contact the server and gets no response. can someone
> help me understand the full story here?
> 
> errors are like:
> 
> [2002/04/23 12:59:25, 4]
> nmbd/nmbd_packets.c:retransmit_or_expire_response_records(1664)
>   retransmit_or_expire_response_records: timeout for packet id 3252 to IP
> 192.168.2.138 on subnet UNICAST_SUBNET
> 
> [2002/04/23 12:59:25, 2] 
> nmbd/nmbd_nameregister.c:register_name_timeout_response(200)
>   register_name_timeout_response: WINS server at address 192.168.2.138 is 
> not responding.
> 
> [2002/04/23 12:59:26, 4] 
> nmbd/nmbd_packets.c:retransmit_or_expire_response_records(1664)
>   retransmit_or_expire_response_records: timeout for packet id 3254 to IP 
> 192.168.2.138 on subnet UNICAST_SUBNET
> 
> [2002/04/23 12:59:26, 0] 
> nmbd/nmbd_become_dmb.c:become_domain_master_query_fail(259)
>   become_domain_master_query_fail: Error 0 returned when querying WINS 
> server for name 2030<1b>.
> 
> i dont think there is a real problem with the WINS server, since windows 
> clients are able to browse across subnet boundaires...
> 
> more detail:
> my issue is this- i have machines with static ips in address range say 
> 192.168.91.x and dhcp clients on the same segment get ips of 192.168.92.x 
> i have no control of the dhcp server or wins server. i would like to use 
> samba services on the .91.x machines from .92.x machines, and have found 
> one configuration with which the .92.x machines may 'find' a samba server 
> on .91.x but not by 'browsing'. that is by telling a .91.x samba server to 
> be domain master, preferred master, os level 65, local master. then 
> windows 'find .. computer' can find it and things work, but it does not 
> appear in the 'neighborhood'
> also, it would seem a bad thing to have nmbd constantly sending out these 
> purposless packets...
> 
> any info, pointers, tips appreciated.
> thanks... ;)
> -n