Circuit TCP-0-51, Unexpected packet type, Adjacent node = 51.10
Packet beginning = 010A1405400202000058020008080908
day. It's not always an "unexpected packet type" error; sometimes it'll just
be a "listener receive timeout" instead.
Not to sound like an AOL'er, but "Me too!" I occasionally see these in the logs, regardless of who the link is to. FRUGAL is running Multinet 5.3.
Fred
Circuit TCP-0-51, Adjacent node = 5.10 (MICRO1)
In this case it was node 51.10 but it's not unique to that machine - I've
seen the same problem from time to time on the other links as well.
It's always a transient problem; the link comes back up on its own in a
minute or so. It seems to come in "clusters" - I'll get a whole bunch of
these errors logged one afternoon, and then everything will be stable for a
day. It's not always an "unexpected packet type" error; sometimes it'll just
be a "listener receive timeout" instead.
Given that Multinet uses UDP it almost looks like UDP packets are getting
lost or trashed sporadically.
So many people are running Multinet links now - does anybody else have
this problem? Has anybody figured out the cause or a fix?
I've seen them quite a few times, but I don't know why or how to cure them.
Chrissie
Circuit TCP-0-51, Adjacent node = 5.10 (MICRO1)
In this case it was node 51.10 but it's not unique to that machine - I've
seen the same problem from time to time on the other links as well.
It's always a transient problem; the link comes back up on its own in a
minute or so. It seems to come in "clusters" - I'll get a whole bunch of
these errors logged one afternoon, and then everything will be stable for a
day. It's not always an "unexpected packet type" error; sometimes it'll just
be a "listener receive timeout" instead.
Given that Multinet uses UDP it almost looks like UDP packets are getting
lost or trashed sporadically.
So many people are running Multinet links now - does anybody else have
this problem? Has anybody figured out the cause or a fix?
Bob
batch printing by automating turning on the printer once a day, clearing
the print queue, and then turning the printer off. I've got the facility
to programmatically turn the power on and off. The printer would be
connected to a DECserver 90M.
Any ideas?
Regards, Mark
