Re: Weird problem with rmtoutq failing

one possibility,
Have your networks guys look for a flood of traffic on the lan.
With the worms & viruses, or if a local pc is sending tons of mail,
that will do it. The packets timeout in the flood. I've had this with
telnet & lpd on a customer compromised with email relay.
jim
----- Original Message ----- 
From: "Adam Lang" <aalang@xxxxxxxxxxxxxxxxxxxx>
To: <midrange-l@xxxxxxxxxxxx>
Sent: Friday, February 06, 2004 10:21 AM
Subject: Weird problem with rmtoutq failing


> We have an LPD server setup on our Windows print server.  We have several
> remoteqs on the AS/400 that print to them over TCP/IP.  Twice in the last
> week all the writers have just hung on SND status.
>
> First attempt at fixing I restarted the Wi8ndows print server and it still
> didn't clear up.
>
> Second I ENDTCP varied off the ethernet lin and dev and started it all
back
> up and it still would remain hung.
>
> Finally we IPLed the system and when it came back up print would resume.
>
> We have had this setup for years and never a problem, but now we have had
> this twice in one week and there has been no change to our network.
>
> Nothing is in dsplog to use as a lead.  Anyone have any ideas?
>
> Adam Lang
> Systems Engineer
> Rutgers Casualty Insurance Company
> http://www.rutgersinsurance.com
>
> _______________________________________________
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.
>
>