TEMNGT23@ysub.ysu.edu (Lou Anschuetz) (03/10/91)
Since I posted this as a question a while back I thought I ought to post an answer of sorts. If you recall, my problem was that netstat was running for more than 5 minutes. Two things will eliminate the problem (thanks to Jeff at CODAR for getting me to think about that problem). First, don't run with dns and/or anything in resolv.conf. Second, if you are going to run with anything in resolv.conf, make sure that NONE of the nameservers are able to do recursive nameservice. For some reason, even a netstat -i will go out to the nameservers to do it's check (I don't think it should.... but am not an expert). If the nameserver is recursive, it will take it a LONG time to reject some of the networks contained in /etc/hosts, in particular, localhost. Do away with recursive nameservice and voila, netstat completes in about 2 seconds! So, I wasn't nuts, but Wollongong is very consistent. They don't correctly handle MX records from sendmail, probably because it requires a recursive nameserver! and, several other functions therefore fail when exposed to recursion. Hope all that helps some folks - and hopefully will aid NCR in resolving some other problems in the WIN tcp/ip code. Have fun! Lou Anschuetz temngt23@ysub.ysu.edu