I've heard from KMA that scanning printing via DHCP is not the prefered way to go. I have 2 customers with DHCP environments that both have scanning and neither units work with any sort of consistency. Sometimes the unit connects to a PC, other times it never does. Has anyone else had DHCP hurdles when it comes to scans?

Use host names in place of the IP address when setting up destination/sender folders. It does work well in some environments.
Using a static IP address should work in most environments for printing, but you can also use the host name of the copier/printer as well when setting up the TCP/IP port wizard.

I know how the setup is, it just seems less reliable on DHCP as opposed to IP.

Maybe I'm not getting what you are asking but anyway, when you set up the folders with the web browser and use the IP address of the desktop that is on a DHCP setup as soon as the lease is up the IP address changes and the scanner can no longer find that pc. If the clients are set up on the network for static IP's this does not pose a problem. On the other hand if you set up the folders using the HOST name of the pc that is a constant and DCHP does not have any effect on that.

Unless the IP lease of the desktop is forever, and you can see this in IPCONFIG /all which tell you when the lease expires, it is a sure bet the scanner will not be able to find that pc when the IP address changes.

DHCP and hostname addressing is as reliable as the person who set up the network is good at his/her job.

Sloppy or incomplete DHCP and WINS server settings can cause problems. So can misadministering IP addresses in a static environment.

I once thought it was impossible for a KM-2030 to scan in a DHCP environment, but I have done an install in a location where everything was set up perfectly and correctly. Scan to PC by hostname has not failed there (except during the XP sp2 update period...) and continues to amaze me. I wish I had that net configurator's name - that person is a god-like deity. No other NS-20 system I ever tried that with has been able to handle DHCP.

Honestly, if it's being a problem, the network is set-up sloppy. Doesn't mean you will be able to get it fixed, or that it will be addressed, but that's the facts. Use static IP's if it's possible, but the reality of the current LAN environments is that everybody want's to use DHCP so you are forced to go with the flow.

I think I have a case of what Chris mentioned. These peoples network is a nightmare. There is maybe 12 devices on it, but there are cables everywhere. Two hubs running the place and they look to have about 30 ports, all occupied. I have the scanner set to static IP. The PCs are DHCP so I used hostnames, sometimes though the scanner does not connect. The scanner being IP obviously isnt changing settings so its something deeper.

quote:

Maybe I'm not getting what you are asking but anyway, when you set up the folders with the web browser and use the IP address of the desktop that is on a DHCP setup as soon as the lease is up the IP address changes and the scanner can no longer find that pc. If the clients are set up on the network for static IP's this does not pose a problem. On the other hand if you set up the folders using the HOST name of the pc that is a constant and DCHP does not have any effect on that.

Unless the IP lease of the desktop is forever, and you can see this in IPCONFIG /all which tell you when the lease expires, it is a sure bet the scanner will not be able to find that pc when the IP address changes.

I went through and changed from tcp/ip to host name. Now the three networked scanners alwyas connects when using "scan to pc" Thanks for this tip. It will prevent a few more prematurely grey hairs. No more service calls when the ip address of the scan server changes after thirty days. I'll just have the IT people that set up the networks install the scanner file utilities to every pc.