WINS Server/Browsing help required

[Inaki Sanchez]

It's very strange, indeed. I have never managed a NT wins server... so I don't know what's happening. You could see if this behaviour is the same for a windows client...

Good luck,

---
Inaki Sanchez 
Redes y Comunicaciones 
Universidad de Navarra, Spain    <http://www.unav.es> 
<mailto:isanchez at unav.es>    +34 948425600 




> -----Original Message-----
> From: Ferris, Richard [mailto:Richard.Ferris at softwareag.co.uk]
> Sent: Tuesday, October 16, 2001 1:32 PM
> To: 'isanchez at unav.es'
> Cc: 'samba at lists.samba.org'
> Subject: RE: WINS Server/Browsing help required
> 
> 
> I've set-up a packet sniffer on a mirrored port that the WINS 
> server is
> attached to (local subnet).  Packets are coming through from 
> the remote
> subnet and the computer names are being registered in the 
> WINS database -
> however there are no packets being sent back from the WINS 
> server and I
> notice the same packets are sent through 5 times from the 
> samba server -
> which then seems to correspond with the 5 WINS timeout 
> messages in the log:
> 
> register_name_timeout_response: WINS server at address 
> aa.bb.cc.18 is not
> responding
> 
> I've tested this with clients on the local subnet and the 
> WINS server also
> doesn't send packets back to them?  Could this be a problem 
> with the WINS
> server itself?
> 
> Thanks Again
> 
> Richard
> 
> -----Original Message-----
> From: Inaki Sanchez [mailto:isanchez at unav.es] 
> Sent: 13 October 2001 12:19
> To: 'Ferris, Richard'
> Cc: 'Samba mailing list'
> Subject: RE: WINS Server/Browsing help required
> 
> 
> > Hi there, thanks for the response.  I have added the IP 
> address of the 
> > domain master browser to the lmhosts file - now this seems to have 
> > helped somewhat.  The nmbd log now contains a list of machines from
> > the domain
> > master browser on the aa.bb.cc.* subnet and clients on the 
> > new subnet can
> > now browse everything!
> > 
> > However I still get the message that the WINS server cannot
> > be contacted.
> > The WINS server is the domain master browser, so how come I 
> > can get a browse
> > list but no WINS connection?
> 
> Browsing uses UDP port 138 (and TCP 139 for browse lists 
> syncronizations),
> whereas all WINS stuff and name queries use UDP port 137. 
> Have you checked
> that UDP 137 packets can go from one net to another? It your 
> clients at
> local subnet, where the WINS server is, can register their 
> names, then there
> is probably a network problem.
> 
> > Another problem I have is that
> > clients in the
> > new subnet cannot find the domain controller when they logon 
> > - however this
> > is another issue!
> > 
> > Thanks Again
> > 
> > Richard
> 
> It could be the same problem: if your clients at remote 
> subnet can't access
> its WINS server, they won't be able to find its DC.
> 
> Good luck,
> 
> ---
> Inaki Sanchez 
> Redes y Comunicaciones 
> Universidad de Navarra, Spain    <http://www.unav.es> 
> <mailto:isanchez at unav.es>    +34 948425600 
> 
> 
> -- 
> The content of this e-mail is confidential, may contain 
> privileged material
> and is intended solely for the recipient(s) named above. If 
> you receive this
> in error, please notify Software AG immediately and delete 
> this e-mail.
> 
> Software AG (UK) Limited
> Registered in England & Wales 1310740
> Registered Office: Hudson House, Hudson Way,
> Pride Park, Derby DE24 8HS
>