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 firstname.lastname@example.org.
I should have checked winsock headers before complaining :-) Anyway Winsock is controlled by MS so they are free to set their own AF_XXX constants. These are not fixed by any RFC AFAIK. As for the main problem, I've just seen the same thing happen on my co-worker's Win2k. When I have time I'll get the sources and try to debug it myself to see what's going on. Seems easier than starting to dismantle my machine :-) Thanks anyway, Eugene "Tony Hoyle" <tmh at nodomain.org> wrote in message news:3df08c58.253111218 at news.cvsnt.org... > On Fri, 06 Dec 2002 11:30:24 GMT, tmh at nodomain.org (Tony Hoyle) wrote: > > >It does seem that something is corrupting the communication between > >client and server. Since it's probably unique to your machine you're > >down to removing stuff until it starts working again. OTOH your OS is > >convinced you have an IRDA adapter so there's something wrong with the > >network setupt anyway. > > > Ahh on Windows it isn't. On Windows address family 23 is INET6 (I > thought these things were supposed to be standard?). That just means > your IPV6 interface isn't working, which is fairly normal (I don['t > think it's configured by default even on XP). > > Tony >