Canon MF5690DN Scanning to Server Issue
We recently changed the LAN's IP to a different subnet and now the scanner will not scan to the server. I was able to verify that the settings are correct through the GUI and the server can ping to the scanner just fine. I can scan and map to the server so not sure what else it can be.
We made sure that the address book entry has the server's information. Does anyone know what it might be?
We made sure that the address book entry has the server's information. Does anyone know what it might be?
From your comments,
VLAN changed: I'm assuming you changed the IP address on the scanner also.
If the only thing that changed is the ip addresses, that usernames did not change and password did not change. Then check windows firewall or antivirus firewall allowing scanning from the new ip of the scanner.
VLAN changed: I'm assuming you changed the IP address on the scanner also.
If the only thing that changed is the ip addresses, that usernames did not change and password did not change. Then check windows firewall or antivirus firewall allowing scanning from the new ip of the scanner.
ASKER
The scanner is an all-in-one scanner/fax. We changed the IP to be on the same local subnet as the laptop and I can get to it just fine and printing works fine. I am also able to get to the GUI of the printer through http://x.x.x.x. I made sure that there is an entry to the server in the address book.
When printing, nothings shows up in the folder where the files for the scans are supposed to be stored.
When printing, nothings shows up in the folder where the files for the scans are supposed to be stored.
Unfortunately, the information you are providing does not shed light on the issue.
Are you using an ip or a name as the server destination. Double check the name resolves to the new ip and not still referencing the old one.
What does the scan/store log shows on the status?
Are you using an ip or a name as the server destination. Double check the name resolves to the new ip and not still referencing the old one.
What does the scan/store log shows on the status?
ASKER
I can ping by IP and map to the scanner share just fine by name (ie...\\laptop-name\scanne
Not sure if there is a disconnect somewhere with the scanner entries for the Windows SMB share to the laptop. I'll see if there is anything in the log to check. thanks!
Not sure if there is a disconnect somewhere with the scanner entries for the Windows SMB share to the laptop. I'll see if there is anything in the log to check. thanks!
your laptop's IP is likely not static.
What is your network setup?
An option could be to use the scan and store option on the MFC to store it in a local mailbox from which you will retrieve the data.
or initiate the scans from the laptop itself?
What is your network setup?
An option could be to use the scan and store option on the MFC to store it in a local mailbox from which you will retrieve the data.
or initiate the scans from the laptop itself?
ASKER
Network is pretty simple on a /24 network and laptop is static. Say Laptop is on 10.1.11.150 and Scanner is 10.1.11.77. I can manually map and ping to the server just fine.
Let me see if the scans can be initiated from the laptop.
Do let me know if there is any other optoins.
Paula
Let me see if the scans can be initiated from the laptop.
Do let me know if there is any other optoins.
Paula
I am getting confused on your issue.
Mfc printer/copier/scanner
Laptop
What server mapping you keep mentioning?
Does the mfc scan to store to a share in a server and you have the share mapped on the laptop?
Mfc printer/copier/scanner
Laptop
What server mapping you keep mentioning?
Does the mfc scan to store to a share in a server and you have the share mapped on the laptop?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Customer resolved issue with another IT person.
You are not providing details. If this is A vlan change, make sure the rules allow the smb access or NFS depending on your setup.