Community technical support mailing list was retired 2010 and replaced with a professional technical support team. For assistance please contact: Pre-sales Technical support via email to sales@march-hare.com.
> Presumably there's a DNS server somewhere, unless you have everything in hosts files... > I'm not that familiar with proxy server 2.0 but I expect if it's doing DNS it'll > have a setting for reverse DNS somewhere. AFAIK WINS is used for all our LAN-based networking lookups (NT 4.0 network). We do not run a local DNS - the only DNS that is used is configured on the Internet gateway to lookup internet addresses. I'll have to investigate further but I may leave reverse lookups off for now. Thanks for the help - it's like I'm talking to one of the authors of the program or something ;-) -- Allan Williams "Tony Hoyle" <tmh at nodomain.org> wrote in message news:c3847g$a07$1 at paris.nodomain.org... > Al Williams wrote: > > > > OK - that helps. Can I leave the server set that way (ie: what impact does > > it have) or do I need to resolve the issue further? > > It should be resolved... it's a DNS misconfiguration that'll bite you eventually. > Currently all it does is stop the lockserver from identifying the client that owns the > lock, which is possible to live without I guess. > > > I saw on the website the notes about reverse DNS but am unclear whether it > > is talking about a misconfiguration on the client PC or the server. We do > > not run a DNS server on the NTserver and use MS Proxy 2.0. > > > Presumably there's a DNS server somewhere, unless you have everything in hosts files... > I'm not that familiar with proxy server 2.0 but I expect if it's doing DNS it'll > have a setting for reverse DNS somewhere. > > Tony