[ add comment ] | permalink |
( 2.8 / 23 )Ideally, you should install print drivers on each computer that you work on but there are cases where you need to install print drivers on a server and share it out. If you start having problems from the server where the copier starts mixing print jobs... instead of printing them one after the other then you need to set the driver to spool and if that doesn't work... try different drivers that are compatible until you get the desired results...
[ add comment ] | permalink |
( 2.9 / 59 )When you need to get a copier operational. Start by cleaning up the copier. After you get it as clean as possible, then do a visual inspection. Look for obvious damage on the document processor, the main body, the finisher, the paper trays and any side doors that you can open.
After this is done, your next step is to test if the copier can make internal copies. Run a status report and check the colors. See if there are any lines, burnt smells or paperjams. Try resolving them if possible.
Then run copies from the plate glass. Try and get it to the best quality possible. Not getting there probably means you have to see if the laser is ok.
Next test the trays... see if you can make copies from each one. If you cannot then make a note and work on it later.
Test your document feeder, test your duplex unit and then try testing your finisher.
Next test if your copier can print and scan. If it cannot this might mean that it needs a firmware update. Try updating everything then try again. If this doesn't work then you got bad parts... try removing your scanner and then printing... or try removing your printer and then scanning...
make doubly sure that you have no ip conflicts...
write up a report with meter reads, how many times assemblies have been changed, condition of assemblies, recommendations on what needs to be done.
You can give this to your service manager or if you are doing this for yourself then make a log book and put this information in there for future reference.
[ add comment ] | permalink |
( 2.9 / 34 )| Lets setup a basic network. You are a copy technician. Why should you know how to setup a network? A basic network is the beginnning of a complex network. If you know how a basic network works then you can apply the concepts learned to a large network. | ||
|
||
[ add comment ] | permalink |
( 2.6 / 8 )MANY OF THESE PROCEDURES WILL NOT WORK ANY MORE...
INTERNET EMAIL SECURITY HAS INCREASED GREATLY
In many copiers you can scan to email. This means that a scan goes in and is transmitted by your copier via an smtp server to the desired email address. This provides portability to your data. In otherwords, you are not restricted by a pc or a folder its in your email and reachable from many places. Most scans can be made in tiff or pdf. TIFF for engineering and PDF for business. As always the case something always goes wrong and its necessary to rule out the smtp server.
This one is for windows via telnet or commandline. With this you can test an smtp server that is on the internet.
This is a complete sample smtp session you can memorize and use it to test smtp reliability on client’s network:
Session START================================
//You begin by typing in telnet and the IP address of the smtp server followed by the port in this case the IP is 207.132.221.51 and your port is 25
telnet 207.132.221.51 25
helo
mail from: <email address>
rcpt to: <email address>
data
subject: test from telnet
from: <email address>
to: <email address>
this is a test
bye
.
Session END====================================
Now lets do the same thing but with an exchange server
1. Telnet into Exchange server hosting IMS service using TCP port 25.
Command is telnet <servername> 25
2. Turn on local echo on your telnet client so that you can see what you are typing.
On Win 9x and NT 3.5/4.0 Telnet client this done by selecting the "preferences" from the "terminal" pull down menu, and checking the local echo radio button. For Windows 2000 telnet client, issue command "set local_echo", from the telnet command prompt.
3. Issue the following smtp command sequence
helo <your domain name><enter>
response should be as follows
250 OK
mail from: <your Email Address><enter>
response should be as follows
250 OK - mail from <your Email address>
rcpt to: <recipient address><enter>
response should be as follows
250 OK - Recipient <recipient address>
data<enter>
response should be as follows
354 Send data. End with CRLF.CRLF
To: <recipient's display name><enter>
From: <your display name><enter>
Subject: <Subject field of Email message><enter>
<Enter you body text><enter><enter> . <enter>
response should be as follows
250 OK
quit<enter>
Now lets do the same test for linux
The HELO command (SMTP commands are case insensitive) provides the remote server with your hostname or domain name.
mail from:<mick@dogpeople.org>
The MAIL command is used to specify your email's "from:" address. Again, this is usually taken at face value.
rcpt to:<groucho@hackenbush.com>
Use the RCPT command to specify your email's "to:" address. This address may or may not be validated: a well-configured SMTP host will reject nonlocal destination addresses for incoming mail to prevent unauthorized mail relaying.
data
DATA means "and now, here's the message." To specify an optional Subject line, make the first word of the first line of your message "Subject:", followed immediately by your subject string. You can specify other SMTP headers too, each on its own line; if you want, you can even make headers up — e.g., "X-Slartibartfast: Whee!"
When your message is complete, type a period on an empty line, and press RETURN.
quit
QUIT closes the SMTP session.
My own procedure to test any SMTP server I set up is first to deliver a message this way from the server to itself — i.e., telnet localhost 25. If that succeeds, I then try the same thing from a remote system.
This technique doesn't work for advanced setups like SMTP over TLS (covered later in this chapter), but it's a fast, simple, and reliable test for basic SMTP server configurations, especially when you need to verify that antirelaying and other controls have been set correctly.
[ add comment ] | permalink |
( 2.9 / 34 )
Calendar
