Hi all, it's great to find this forum, I can tell you!
I did some work for a client in the last week which involved putting in a new server, switches, remote access etc, and aside from the usual techie hiccups it went pretty smoothly, until the last minute when the client informed me the scanner wasn't working on the printer.
Some info;
The old server used to be on 192.168.16.2 address, and the printer/scanner on something like 192.168.16.20.
The new server is 192.168.1.77 and the printer is on 198.168.1.89, and the scanner on 192.168.1.82 - because this machine has two NICs.
I installed the FileUtility on the new server (windows 2008 R2 Server, with Windows Firewall disabled), where the share had been created to receive scans.
I created the 'pointer' to the folder, and clicked on 'start'.
On the printer/scanner interface, this is where it gets a bit weird. I have put in the IP address of the new server which has the FileUtility software on it in the Address book, given it a name etc. However when you go to the 'Scan' function (one of the four buttons on the right hand side), set your document up (that is to be scanned), selected 'Address book' form the destination area (nothing comes up in the destination list by default), select the new server, press 'Add to recipients', and it gives a little 'x' next to it. You then return to the main scanning interafce screen, click on 'Send to PC', and it take a few seconds, then fails.
Upon inspecting the Fileutility software running on the Server, when you click on 'Details' (if I remember correctly), it shows no scanner is communicating with the software.
I RTFM but it wasn't a lot of help to be honest. Is the File utility software meant to automatically direct traffic from the scanner to the folders set in it? How do you get it to pick up/allocate the scanner?
The printer works fine from PCs on the network.
The Printer Web interface is accessable with no problems.
The Scanner Web interface is accessable with no problems.
Cheers all, appreciate any help on this!
Will
I did some work for a client in the last week which involved putting in a new server, switches, remote access etc, and aside from the usual techie hiccups it went pretty smoothly, until the last minute when the client informed me the scanner wasn't working on the printer.
Some info;
The old server used to be on 192.168.16.2 address, and the printer/scanner on something like 192.168.16.20.
The new server is 192.168.1.77 and the printer is on 198.168.1.89, and the scanner on 192.168.1.82 - because this machine has two NICs.
I installed the FileUtility on the new server (windows 2008 R2 Server, with Windows Firewall disabled), where the share had been created to receive scans.
I created the 'pointer' to the folder, and clicked on 'start'.
On the printer/scanner interface, this is where it gets a bit weird. I have put in the IP address of the new server which has the FileUtility software on it in the Address book, given it a name etc. However when you go to the 'Scan' function (one of the four buttons on the right hand side), set your document up (that is to be scanned), selected 'Address book' form the destination area (nothing comes up in the destination list by default), select the new server, press 'Add to recipients', and it gives a little 'x' next to it. You then return to the main scanning interafce screen, click on 'Send to PC', and it take a few seconds, then fails.
Upon inspecting the Fileutility software running on the Server, when you click on 'Details' (if I remember correctly), it shows no scanner is communicating with the software.
I RTFM but it wasn't a lot of help to be honest. Is the File utility software meant to automatically direct traffic from the scanner to the folders set in it? How do you get it to pick up/allocate the scanner?
The printer works fine from PCs on the network.
The Printer Web interface is accessable with no problems.
The Scanner Web interface is accessable with no problems.
Cheers all, appreciate any help on this!
Will
Comment