Unable to Print

[andymbody]

I wont be able to view the picture until tomorrow when the moderators approve it.

But the DOS screen is what you want. If you were able to run the Command Prompt (black DOS screen) as admin, you should be able to type the command that I gave you (you have already done those steps earlier, just not as admin). The DOS screen will look the same, but it will act differently - it will allow that command to be run without giving you the "access denied" error.

What I'm asking you to do is nothing more than you did earlier today, With the exception of the "run as administrator" portion.

How do you feel about a phone call to walk thru this? If you are in the US.

Andy

[garycardinale]

I do not have the same screen.  I have the dos window.  See picture.

[andymbody]

1. Type cmd in windows search bar

2. Right-click on Command Prompt at top of menu

3. Left-click on Run as administrator

4. Click "Yes" when prompted by User Account Control

5. This will open the command prompt where you can type the command

[andymbody]

Were you able to view the video that i posted a link for? It should have shown how to use the command prompt in admin mode.

Andy

[garycardinale]

it said access is denied.  I have no idea in dos how to change to adminstrator access.  Gary

[andymbody]

I was on my phone when I sent the last post, but it messed up the formatting of the command. I kept trying to edit it and repost, but it got worse. I finally used my computer and was able to get it to post correctly.

Please read the previous post above for my repost. It has all the details and the correct command.

Here is a video explaining how to run command prompt as admin

Run as admin 

[garycardinale]

not sure how to run at administrator.  I haven't used dos in a couple of decades.  Gary

[garycardinale]

This command does not work.  It says it could not find the host.  I typed in:

ping 192.168.50.98. -t c:\pingtest.txt

[andymbody]

As an alternate, use the command below to redirect the ping messages to a file that you can inspect later. If you do it this way, you won't have to stare at the screen watching the ping messages (which may not even look like they are updating over a period of time - but they are).

First, you must run command prompt as admin (so you can save to root of c). This will allow you to record the ping test to a text file for later viewing or so you can upload here for inspection.

While running command prompt as admin, type this at command prompt, then press enter.

ping   192.168.50.98   -t   >>   c:\pingtest.txt

(There are single spaces between the different parts (where you see gaps) of this command, make sure you use single spaces to separate the parts).

After 5-10 minutes, use Ctrl+C (with command prompt window active) to stop the ping test. Then goto your C drive root directory and open the pingtest.txt file to view it. A 10 minute run should create a file about 30K in size and have about 700 ping responses.

Run as admin 

Andy

[andymbody]

I just looked at the ping screenshot that you posted. The number of pings on that screen are not near long enough to get an accurate idea of how reliable the connectivity is between the computer and printer. And there are delays in the communication that is show there. Notice the 14ms lines. I know this does not sound like a lot but it's 14 times longer than normal. That would mean that some packets are taking 14 times longer to either reach the printer or for a reply to reach your computer. And this is just in this short test. There may be even longer delays that a longer ping test will reveal.

Run this test for more than 5 minutes and watch the screen. Watch how many times the ping takes longer than 1ms. Chances are you will see a lot. I see this type of thing cause printing issues all the time.

This data is being sent via TCP which means the computer must wait for the printer to acknowledge that a packet has arrived before it can send more data. If there are delays, then at best, the print job will take longer than expected to print. And if the communication takes too long due to these delays or packets get dropped, then the job may never print. All of the data must get to the printer, not just some.

Is this the problem? I'm not sure but it's worth exploring based on the symptoms we are seeing.

To answer your next question... why is this only happening with your computer? Because we are more than likely dealing with a layer 1 issue which would be different than the layer 1 on other devices on your network.

Please run the ping test again but for at least 5 minutes, 10 minutes would be better. Grab some coffee and watch the screen while the test runs. If you don't have time to do this, do it when you have time.