Network Install Guide For Dummies

Not here, however it wouldbe good to have. Seems to me all manufacturers should get on the same wave and have common crtieria for setting all systems on network, whether sca2email, san2folder, LAN fax etc. It'll never happen!

My first thought when I saw this was that it couldn't be done because there are so many unknown variables to take into account in each situation.

But in reality there are just a few problems for each of these that are USUALLY the case.

I don't see how you can be in business without someone to handle these things though.

I agree with Jason, every commercial network is slightly different. Like fingerprints.And its because it was set up by a different IT person with various agenda set by his company and the employer of the network.
I think you might be able to write a guide (and actually there is a "Dummies Guide to Networks")
but you would have to have some knowledge to use the guide for it to be any good.
Router mfgs dont even use the same DHCP IP ranges.
If the network is on a domain, your problems increased 10-fold.
Most companys I work with have a contract IT company that can remote in to solve big or small problems. Other at least have someone who is familiar with their network.
If not, thats why they buy from me and not someone who cant help them.

John:

I understand your pain. As the others have mentioned, there are a lot of variables.

Like you, I'm the "buck stops here" guy for our company. Often a thankless job. A lot of times when things go perfect, nothing is said. However, when you run into a glitch, it's all eyes on you.

You need some "go to" people. Your district sales manager should be able to put you in touch with the person on your team for escalations. I've also had good luck with the presales/connectivity support from RFG 1-800-577-4264. They'll want your Tech ID, but for a month or more I told them I didn't have it and got by with company name, telephone number, etc... I'd still be going this route if I didn't go to Ricoh University (on the web) and uncover my actual ID. Depending on the person you get, the support ranges from someone who is as in the dark as we are to someone who can really make your day a lot easier.

There's no substitute for your demo room. I've learned a lot from just having a color mfp, some curiosity and a little after hours time to play. It seems beneficial to learn what works well for you and guide the customer toward what you want to accomplish. If you give them a large pasture, you'll have trouble coralling them into what you want to do.

For what it's worth, here are some things that have worked well for me:

1. I always play second fiddle to their IT support. Once I get them on my side, they teach me a lot. I let them know who I am, what I want to do and get their buy in. This generates leads as they get comfortable working with me. When I get a lead from them, it's qualified and offers a higher gross profit than a deal where I'm just another guy.
2. If the product has ethernet capability, I recommend always installing this way instead of locally.
3. I give the mfp a static IP address. If possible, I get it from the network administrator. When I can't, I go into the command prompt if a computer on the network and do an ipconfig/all. I look at the IP and if it's 192.168.0.42 for example, I start pinging 192.168.0.43 and up to find an open one. I assign this to the mfp (never use dhcp) and make it static. I connect the product and ping it to make sure it is at that location and can communicate.
4. I resist the temptation to make a pc/server a print server and spend the extra time installing a straight TCP/IP port on each client computer for printing purposes.
5. If installing LAN-fax, I show the customer how it works and send a test page. If they ask about a cover page, I show them the samples and explain if they want custom cover sheets, they can be provided as a professional service on a billable basis.
6. When setting up scanning, 90% of my customers are satisfied with scan to folder. I set up a computer as a "scan server" and create a directory for "company scans". Each user gets their own folder and all scans go there. Each client computer has a shortcut to the appropriate folder. If they are concerned about confidentiallity, I explain that this is the electronic version of their in-bin. Scan stuff there and take it out. I never (I know that's a finite word, but as a rule with rare exceptions) try to scan to multiple computers using SMB, it's a nightmare with all of the login information, people not knowing what their username is, computers being replaced, etc...I tell them how it works and never tell them it's possible. I explain that they have a network for a reason and file sharing is one of the most fundamental. They usually already have a data share of some other area where they all collaborate.
7. If they have a server OS I use it as the scan server. If they use Active Directory, I have them add the scanner as a user and create a password for it (adding it to the administrators group or domain admin group). When the scanner scans to it using SMB, it uses the login credentials of that user. Then, the folders can be shared only for the scanner user and the user whose folder it is, creating more security.
8. In the event they want to use scan to email, or if they're a real estate office or another account where it makes more sense, I try to get their smtp server information (with respect to authentication) before installation and set it up and test before installation. Unless they really need scan to email, I explain that it's more simple to scan to a folder and email from there since the mfp is more tedious for entering subject matter and some mail servers are likely to reject email coming from a somewhat unknown party (the mfp) with an attachment because they see it as potential spam.
9. I work closely with my sales team to make sure they understand what is possible and what is reasonable based on the information they provide, my skill set and the customer's needs. If I'm not strong in an area, I'd rather tell them that and put it on my list to research than be in front of the customer trying to figure it out and having to answer to both of them.

I hope these ideas help you. You may already know most of them. Take the best and leave the rest. Everyone won't agree with what I've said...based on the day, customer and my mood, I won't even agree with some of it in the next installation I do. There's no black & white, if there were, the customers wouldn't need us.

I've rambled more than enough. Good luck.

Realy well done, JS. If I may, I would like to offer one change, I am sure you will agree will prevent call-backs.

quote:

nd if it's 192.168.0.42 for example, I start pinging 192.168.0.43 and up to find an open one. I assign this to the mfp

If the existing range is .43, go all the way up to .200 and ping there. If you assign .43 or something too close, the DHCP server may assign it to a workstation tomorrow that wasn't online today. The same IP for two nodes will render both unusable. Of course if an IT person is there, they can reserve that address for the mfp. But if not I'm sure you dont want to make changes to their server.

Thanks for the help guys. I appreciate all the info and will use. I've been missing in action for a couple of weeks with work and family, but I did want to get back with you and let you know that all the folks here at P4P are an invaluable resource that you can't get anywhere else.

Thanks again!

Yeah, Jomama's right, starting at a higher # will probable reduce the possibility that a PC that is offline today may have the IP assigned to it in the future.

This is why I don't like General Guides

If a customer is using DHCP, simply picking a higher number is not safe.

You (and your contact at the customer) may not be aware of other factors.

There may be a different class of devices (such as servers or printers or whatever) that is placed into a higher DHCP range.

If you want to be perfectly safe when the customer is on DHCP, their IT should provide you with an IP. Of course, I've grabbed a seemingly open IP in order to get he printer working too .

quote:

their IT should provide you with an IP

Of course, if they have an IT person. How many times have I heard "The salesman said you would take care of it all!" (dangling a check over my head)

99% of the time, the IP I pick is fine. If their network is that complex, I should have their IT department involved anyway.

If you pick one and their is a conflict, the product will usually tell you when it happens and it's not that difficult to fix.

If the customer can't give me an IP or know of one that is available, I will use the one that was in the printer/copier that I am replacing. If it is a new install, I will ask their IT what IP to use or have them do it. So far it has not been an issue.

I mention this because I've had two customer's call me saying the IP we put into the machine later caused a conflict. Since they had to pay a contract IT person to come out and fix the issue, they want me to pay that invoice since I caused the problem to begin with.

I'm not saying it's a horrible thing, I'm not saying "OMGZ, don't ever do that" I'm just saying if you do it, be aware you may encounter an issue eventually.