Mailing List Message #15547
From: NetHead <>
Subject: Re: SIMS won't send for device (was Re: Ping list (sorry but have seen nothing for days))
Date: Mon, 24 Sep 2007 10:14:10 -0500
To: SIMS Discussions <>
X-Mailer: Claris Emailer 2.0v3, January 22, 1998
Okay, I'll go you one better. I can send through a different SMTP server.
I had a technician for the device in question (a Kycera-Mita copier, just
in case you were curious) come on site to try and resolve the problem. He
runs a very simple SMTP program on his laptop. We changed the settings on
the KM copier to send SMTP via his laptop's ip and the transmissions went
through flawlessly. But when I switched back to the IP of the SIMS
server, they failed again. So I don't think the problem is hardware
related. And I don't think the copier is simply "dropping" the
connection... why would it do it to SIMS and not some other SMTP server?

So, all that said, I'm back to square one.

If you have any more ideas, I'm willing to listen. Or if I missed
something in my explanation above, let me know.

Doug Starkey
Network Administrator
Pecan Deluxe Candy Company

Wasn't it SIMS Discussions who once said...

>Date: Sat, 22 Sep 2007 12:41:03 -0700
>From: Joe Wagner <>
>Subject: Re: Ping list (sorry but have seen nothing for days)
>>I have tested sending via a different server and that verifies that
>>the device is capable of sending;
>         Just curious have you tried swapping intervening the
>ethernet cords/ethernet router? Using different ethernet ports; if
>it's not possible on the device, then on the SIMS mac? I keep around
>an old SCSI to ethernet adaptor just to swap in for testes with old OS9 macs.
>         I once had a Windows server that spontaneously after years
>of service stopped connecting to a Dell laptop but would to a
>powerbook and other machines.  I could not figured out the problem
>and presumed in the end that something odd (no surprise) was going
>with the Windows laptop. A while later, the powerbook began having
>problems connecting. I replaced the server's ethernet card with an
>identical card (a spare from the same ten pack) and while the rest of
>the server's hardware and software never noticed the replacement,
>suddenly everything was rock solid. So what I mean with my rambled
>anecdote is that while test connecting with other machines is a good
>test, flaky network connects cause by hardware sometimes feels like
>tracing a ground fault or cold solder joint on a big circuit board
>where just moving your hand with the probe near problem can change or
>hide the symptoms.
Subscribe (FEED) Subscribe (DIGEST) Subscribe (INDEX) Unsubscribe Mail to Listmaster