I am trying to set up a LAN for a charity. But am having difficulty networking on a wireless Kodak Printer.
The Hub is a BT Business BB Router. I have set up 7 computers on the LAN and am trying to get them to all print using the KODAK C3100 Printer.
The first one installed from the Install Disc. The second one stated there was a fire wall block, Port 5353. The third has a fault of 106-1606 so even though it shows the printer available but when I try to install it states no printer found.
Do I need to re-set up the network as public or pivate. The 3 pcs next to the printer are running Vista, three others are running Win7, I am not setting these up to the printer, and the router is controlled by an old pc running XP.
I have not hard wired any computers to the printer but have downloaded a firmware update.
I thought this would be a simple, quick Saturday morning job.
The last Kodak printer I set up on a BT HomeHub was a similar nightmare. Solved by setting the Printer wireless configuration using the printer's settings and WLAN manually to join the router. (Using the encryption key on the router)
Then using the disk to add each computer so that the Kodak software was installed on every machine. (There were only 2 in this instance) No need to use a USB cable and using the wizard simply joined the network and searched for the printer on it.
thanks. I have installed the printer from it's settings to the WiFi network. All the PC's can see it but the printer wizards can not find the drivers online. I then run the Kodak disc installation but then get the two faults. The one with the socket 5353 firewall issue has still installed the driver so I can print from the desktop icon and it appears in the Ctrl P option. The one with the Windows fault code, whcih is not recognised by the windows fault look up does not install the printer icon onto the tool bar.
Sorry fault code 101-1606, (Wrongly said 106) MSi error. I have run the Microsoft FiXIt but nothing found. It is just one machine. I was looking to see if there is available a Microsoft Installer Cleaner that I can run?
or even a generic installer cleaner.