tuens out that the first log file was causing the problem. Elconv would just hang 
on trying to convert it. renamed it, reran elconv, reload service and 2.51 elogd 
and all was working as it should.


> Have a working copy of 1.35 running on NT4 server.
> Went to upgrade to latest version.
> Stopped service, installed the 2.52 version, restarted service and when 
> trying to connect get nothing but server not found, dns errors, etc.
> Copy back the 1.35 elogd.exe and everything is fine - I can connect and add 
> entries to log.
> Copy 2.52 elogd.exe and nothing.
> 
> So being the bright boy, I unistalled E-log, went through the registry and 
> yanked everything out that referenced ELOGD, rebooted, installed 2.52, made 
> the necessary registry changes, started service and nothing. 
> 
> Stopped service and copied 1.35 Elogd.exe back into folder, started service, 
> and everything works.
> 
> Any ideas on why 1.35 works like a charm but 2.52 won't? I've tried stepping 
> back to 2.10 version before giving up.
> 
> This is a server that is patched to latest and runs quite well with 1.35.