As what security principal are you running the service?
As of XP and 2003 (IIRC), many services run without network credentials,
which *might* mean that it simply cannot contact the DNS?
Thanks for responding. I already figured it out. Winsock somehow requires
DNS client (dnscache) to run, if you run your application as service.
If dnscache is not run, the service will not be able to resolve any
hostname. But the same application running as normal console app
has no problem resolving hostname, even if dnscache is not running.
I always turn off dnscache, and this is wasting me 2 days of debugging
(well, some of the time was spent debugging why neon 0.24.7 crashed
because it can't resolve hostname).
I find it to be really stupid that a socket implementation would behave
totally differently if the app is run as normal console app or as service.
Someone better versed in win api would like to comment on this?
coco
_________________________________________________________________
On the road to retirement? Check out MSN Life Events for advice on how to
get there! http://lifeevents.msn.com/category.aspx?cid=Retirement
_______________________________________________
neon mailing list
[email protected]
http://mailman.webdav.org/mailman/listinfo/neon
