Cabling I might believe, and will check on that. Dupe addresses are ruled out.
Kurt On Thu, Jul 18, 2013 at 10:18 AM, Kennedy, Jim <[email protected]> wrote: > Nic/cabling/physical issue sounds like the next place to check....dup IP > address for the printer or the server? > > -----Original Message----- > From: [email protected] [mailto:[email protected]] > On Behalf Of Kurt Buff > Sent: Thursday, July 18, 2013 1:17 PM > To: [email protected] > Subject: Re: [NTSysADM] Odd spooler issue > > On Thu, Jul 18, 2013 at 7:39 AM, Miller Bonnie L. > <[email protected]> wrote: >> Are you able to flop one of the queues to print directly to the printer (no >> spooling) and see if you still get hang-ups? Advanced tab setting. > Good thought. I'll try that. > > I did a run of a little over 800 pings, and got 1% loss - the start of the > run was pretty rough, though it settled down to most ping times of <1ms after > that: > Pinging 192.168.24.73 with 32 bytes of data: > Reply from 192.168.24.73: bytes=32 time=227ms TTL=254 Reply from > 192.168.24.73: bytes=32 time<1ms TTL=254 Reply from 192.168.24.73: bytes=32 > time<1ms TTL=254 Reply from 192.168.24.73: bytes=32 time=185ms TTL=254 Reply > from 192.168.24.73: bytes=32 time<1ms TTL=254 Request timed out. > Request timed out. > Reply from 192.168.24.73: bytes=32 time=168ms TTL=254 Reply from > 192.168.24.73: bytes=32 time=53ms TTL=254 Reply from 192.168.24.73: bytes=32 > time=4ms TTL=254 Request timed out. > Request timed out. > Request timed out. > Reply from 192.168.24.73: bytes=32 time=57ms TTL=254 Reply from > 192.168.24.73: bytes=32 time<1ms TTL=254 Reply from 192.168.24.73: bytes=32 > time=225ms TTL=254 Reply from 192.168.24.73: bytes=32 time=3ms TTL=254 Reply > from 192.168.24.73: bytes=32 time<1ms TTL=254 Reply from 192.168.24.73: > bytes=32 time<1ms TTL=254 Request timed out. > Reply from 192.168.24.73: bytes=32 time=112ms TTL=254 Reply from > 192.168.24.73: bytes=32 time<1ms TTL=254 Reply from 192.168.24.73: bytes=32 > time<1ms TTL=254 Request timed out. > Reply from 192.168.24.73: bytes=32 time=44ms TTL=254 > > What's really weird is that the cmd box didn't update its display as expected > during the above sequence. Up until that last displayed ping return, it would > erratically hold on printing to the screen, and then output several several > lines at once. After the above sequence, it was well behaved, printing out > the ping responses as expected. > > I've been looking at the performance stats for the VM and the host, and don't > see anything out of the ordinary. > > Kurt > >> >> -----Original Message----- >> From: [email protected] >> [mailto:[email protected]] On Behalf Of Kurt Buff >> Sent: Thursday, July 18, 2013 7:24 AM >> To: [email protected] >> Subject: Re: [NTSysADM] Odd spooler issue >> >> On Thu, Jul 18, 2013 at 7:14 AM, Miller Bonnie L. >> <[email protected]> wrote: >>> How is ping time to the printers at the time of hang-up? >> >> I'll check that, but it's probably in the 1-2ms range >> >>> Can you view a web interface at the same time and see what they are doing? >> >> Yup - the printers are fine, AFAICT >> >>> Could be a slowdown on the spool disk, but I would expect it to happen to >>> every queue on that server and not just certain ones. >> >> Agreed, and since the print server is a VM, it should show up across all the >> VMs that use the SAN, and I'm not seeing that. >> >>> You could also open up the folder and see if the files are showing up in a >>> timely manner, growing overly large, etc. >> >> Print jobs are on the order of 1-2k, and often less. >> >> Kurt >> >>> >>> -----Original Message----- >>> From: [email protected] >>> [mailto:[email protected]] On Behalf Of Kurt Buff >>> Sent: Wednesday, July 17, 2013 4:15 PM >>> To: [email protected] >>> Subject: [NTSysADM] Odd spooler issue >>> >>> All, >>> >>> I've got a little head scratcher, and would appreciate any insight folks >>> might have. >>> >>> Printer Server: Win2k8 R2, fully patched VM running on vSphere 5 >>> (recently gone from 5.0 to 5.1, the problem began on the earlier >>> version.) >>> >>> Problem: Print jobs from our installation of Epicor Avante to various >>> printers (an HP 2055 and several models of Zebra printer) hosted on >>> the printer server, will intermittently hang in the print queue. >>> Delay will range anywhere from 1.5 - 2 minutes, and they they'll >>> print. I can see the jobs in queue, just sitting there (they have a >>> status of 'printing', but do nothing.) >>> >>> I am seeing nothing in the event viewer for the printer server that >>> looks relevant, and certainly no warnings or errors. Neither memory >>> nor CPU spike >>> >>> The Avante server is running Win2k3 R2. >>> >>> The problem disappears and reappears a couple of times a week. >>> >>> Thoughts? >>> >>> Kurt >>> >>> >> >> > >
