- #BROTHER FIRMWARE UPDATE TOOL CONNECTION FAILURE TCP FULL#
- #BROTHER FIRMWARE UPDATE TOOL CONNECTION FAILURE TCP PASSWORD#
This may fix the issue without effecting the scanning from other machines. Open a telnet connection to the copier and do the following that is in BOLD. A problem getting through the VPN (not at all likely, for the reasons given above), orĢ. Some mystery (my conclusion so far and the reason for posting here). Just to rule out Kerberos issues, I check the time on the scanner, and it is the same date, time (at least within seconds), and time zone as the server.Īll of this works from any computer on the same LAN.
#BROTHER FIRMWARE UPDATE TOOL CONNECTION FAILURE TCP PASSWORD#
Have tried both by leaving name/password blank (presumably defaulting to that above) and explicitly entering domain\username & password
#BROTHER FIRMWARE UPDATE TOOL CONNECTION FAILURE TCP FULL#
SMB User Name in this format: domain\username (this is a domain admin, so I know it has full rights on the server side) Verified that the printer/scanner has the domain controller set as its DNS server (like all workstations).ĭevice Managment → Configuration → File Transfer This rules out any server-side or simple reset issues. This should be irrelevant, given that all workstations at the same remote site can access SMB resources across the VPN, the Ricoh can access the Exchange/SMTP server across the VPN, and we can also print to the Ricoh back through the VPN from computers at the HQ side of the VPN. Rebooted the router (this is at a remote site connected site-to-site via SonicWall hardware VPN. Here is what I have done:Ĭonnect to the server (Windows 2012 R2) hosting the shares using the domain admin account that we are using for scanning.Įnsured I can see the share and copy files to it across the network. I have been through things in as much detail as I can, and I find it very frustrating that cannot find any debug-level logs that can reveal exactly where the breakdown is. None of the SMB scan destinations work, so it would seem to be something on the unit itself. As far as I know, this was working until a couple of weeks ago, but it is definitely not working now.
Printer works fine, as does scan via SMTP (using in-house Exchange/SMTP server), but SMB scanning does not.