Copystar Scan to SMB Issue Resolved

[Gym Teacher]

Sometimes the Copystars don't connect properly to a networked PC when the host name is used. Setting up the host name and login user name in the destination is the way the manual says to do it. But for some reason, this does not work, or stops working after previously working correctly.

Using the IP address has worked for me. The only problem is that this is not the most desirable way to go if your router's DHCP assigns a new ip address to the copier when either the copier or the router is rebooted. If your router stays 'on' all the time (as most do), this should not be a problem.

The solution is to use the IP address of the computer on the network to which you want to send scans. Make sure you have followed all the setup requirements for file sharing. When putting the information in the destination form on the copier, for [Host Name} put in the IP address followed by a colon and the port number 445. For example, 192.168.1.135:445.

You won't find this information in any of the documentation. A Copystar factory tech put me on to this tip.

[bsm2]

smb is port 139 or sometimes you can use port 445

host names can have some problems if dns is not configured
also sometimes you must use the full domain name of the pc

use non static IP address will result in a call back for not scanning

[Jules Winfield]

Scanning to SMB using IP addresses will work fine in a DHCP environment provided you can convince the customer to set up a reserved IP based on the PC's MAC address. This is extremely simple to set up and saves a lot of headaches further down the road.

[Gym Teacher]

Thanks guys for amplifying on the subject of using IP addresses.

Yes, there is the potential problem of call-backs when the IP address changes. One solution is to create static IP addresses where possible.

Another solution is to create a "cheat sheet" that provides the steps to go through to determine the new IP address and then change the address in the destination panel.

Of course none of this would be necessary if Kyocera/Mita would get the bugs out of the software - especially for Vista and now Windows 7.

[Jules Winfield]

Thanks guys for amplifying on the subject of using IP addresses.

Yes, there is the potential problem of call-backs when the IP address changes. One solution is to create static IP addresses where possible.

Another solution is to create a "cheat sheet" that provides the steps to go through to determine the new IP address and then change the address in the destination panel.

Of course none of this would be necessary if Kyocera/Mita would get the bugs out of the software - especially for Vista and now Windows 7.

It's not just bugs in the software that cause problems like this. DNS issues that have nothing to do with the printer or it's software can cause the same types of problems.