Scan to Folder Problem after MS Update

[PillePalle]

Re: Scan to Folder Problem after MS Update

There is a KB article on Nuance's site about this.

can you drop me over the Link. Because i also got to take care of some major Clients that work with Equitrac. So just in case one them pops up with this issue i`m prepared.

I thank you in advance

[KenB]

Re: Scan to Folder Problem after MS Update

can you drop me over the Link. Because i also got to take care of some major Clients that work with Equitrac. So just in case one them pops up with this issue i`m prepared.

I thank you in advance

Here it is:

https://nuanceimaging.custhelp.com/app/answers/detail/a_id/24127/kw/scanning%20error/session/L3RpbWUvMTQ2ODUyMjU4My9zaWQvVEtWbXh3Vm0%3D

[PillePalle]

Re: Scan to Folder Problem after MS Update

Hi Guys

Got another Document i made where all the Informations are inside. The Key that has to be changed as well as the Domain Name Issue

Scan 2 Folder funktioniert nicht nach MS Update v.1.0.pdf

Don`t get confused by the Title i simply forgot to change the Title to English. Anything inside in English.

[rthonpm]

Re: Scan to Folder Problem after MS Update

Hi All,

Workaround
To avoid this issue, please conduct the following workaround:

- Change the priority port for the SMB client to TCP 445 (Direct Hosting/CIFS) by using telnet.

Change the priority port procedure of the SMB client:
1) Connect to the target device by using telnet from the command prompt and log in as the administrator.
2) Enter the following command:
>smb client port 445


RICOH Maintenance Shell.
User access verification.
login: ***** (enter the Administrator login name)
Password: (enter the password)
User access verification ... OK.
RICOH ********
Network Control Service Ver. 12.78
Copyright (C) 1994-2016 Ricoh Co.,Ltd. All rights reserved.
msh>smb client port 445
msh> smb
Workgroup Name : WORKGROUP
Computer Name :
Comment :
Notification : Off
Protocol : IPv4
Client Port : 445
Client Auth Level : 0
Client WSD Browse : Off
Client Write Mode : Async
msh> logout
Logout Maintenance Shell.
Do you save configuration data? (yes/no/return) > yes
Yes.
Now, Save data.
Or

Long-term this really is the solution for this issue. WINS has been a dying protocol ever since DNS came on the scene, and Microsoft has even deprecated the feature in Server 2012, while it's still available there's no guarantee as to how long it will be supported.

[KenB]

Re: Scan to Folder Problem after MS Update

OK, here's a new wrinkle...

The telnet session displays IP v4. What if the customer is running IP v6?

Or is that a non-issue?

I just had that question come up today.

[rthonpm]

Re: Scan to Folder Problem after MS Update

OK, here's a new wrinkle...

The telnet session displays IP v4. What if the customer is running IP v6?

Or is that a non-issue?

I just had that question come up today.

The setting is global, you'll just have a longer IP to enter to connect.

[KenB]

Re: Scan to Folder Problem after MS Update

The setting is global, you'll just have a longer IP to enter to connect.

I just read that IP v6 does not work with Port 139 for SMB.

Which makes sense, as earlier today we ran the command "net stat -a" ( no space between net and stat...blame my iPad for that), on the 2012 Server, and it did not show Port 139 at all, but a bunch of connections on Port 445.

Thanks, though. We will try telneting to the IP v6 address.