[Samba] WINS and cross-subnet
neil
neil at box1.staller.sunysb.edu
Tue Apr 23 11:04:03 GMT 2002
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
More information about the samba
mailing list