Date: Tue, 16 Jan 2001 09:07:46 -0500 From: Bill Moran <wmoran@mail.iowna.com> To: cjclark@alum.mit.edu Cc: Cliff Sarginson <cliff@raggedclown.net>, questions@FreeBSD.ORG Subject: Re: natd & failed to write packet back Message-ID: <3A6455B2.F797877F@mail.iowna.com> References: <E14IQZ0-0005bR-00@post.mail.nl.demon.net> <20010115234039.L97980@rfx-64-6-211-149.users.reflexco>
next in thread | previous in thread | raw e-mail | index | archive | help
"Crist J. Clark" wrote: > > In a similar vain, what does the above message indicate but accompanied > > by a "permission denied" as the reason ? > > Doh! Thanks for catching that. I described what 'permission denied' > means. When it says 'host is down,' well... it means that the host the > packet is destined for is down. It must be a host on the local network > to get that message. Well, this helps & not. So, apparently a host on the local (you mean internal, private ips?) network is down. Howerver, it started communicating before it went down. I wouldn't worry, but the fact that it's happening so much. It would be nice if it would tell me _which_ host is down. I guess it could have to do with the Macs going into sleep mode. These folks have a tendency to leave programs running (even after they leave for the day) If a browser were looking at something and went into sleep mode before the exchange completed, this could happen. But that's really pretty far-fetched and it's just a theory. Hmmm ... the mystery continues. Any hints on how to diagnose this? It'd be difficult to isolate the packets that are causing it when there's no indication of IP or port #. -Bill To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3A6455B2.F797877F>