Okay, I should have though of that. Now that I foudn the log files, this is
what the error messages look like
atalkd[2541]: zip gnireply from 1.229 (hme0 b2)
atalkd[2541]: zip ignoring gnireply
atalkd[2541]: zip gnireply from 1.229 (hme0 b2)
atalkd[2541]: zip ignoring gnireply
atalkd[2541]: zip gnireply from 1.229 (hme0 b2)
atalkd[2541]: zip ignoring gnireply
Does this mean anything to you?
On Thu, 03 Feb 2000, andrew morgan wrote:
> On Wed, 2 Feb 2000, Prentice Bisbal wrote:
>
> > Today, I started getting this strange message when a mack tries to
> > connect to one of our netatalk servers (this one is running solaris
> > 2.6, I don't know the exact netatalk version running):
> >
> > "The connection to this server has been unexpectedly broken"
> >
> > This error appears as soon as type in my username/password and hit
> > "connect" or whatever the button reads. Has anyone seen this before?
> > More importantly, how can I find debugging information from netatalk
> > to help me track down the cause of this? Does it get logged anywhere?
>
> It should be logged via the syslog mechanism. Look at your
> /etc/syslog.conf file to see where "daemon" messages are sent.
>
> Andy
--
Prentice Bisbal
[EMAIL PROTECTED]
Princeton Plasma Physics Lab
http://www.pppl.gov
