Scan to Network Share - fails - wrong port - wrong SMB
My Ricoh Scanner seems to be trying to send SMB scans over the wrong port.
We use SBS 2011 and want to have our new Ricoh printer/scanners to scan to shares on the server.
Our server has SMB and it receives scans to shares on the server through port 445.
However, the new scanners only have the old NetBIos port 138 and 139 ports.
I don't know how to make the scanners connect properly to the server, nor how to make the server accept the ports that the scanner uses.
I have the sense that even if were to add the scanners ports 138 &139 to the SMB protocol on the server, that it would still not work because the new Ricoh scanners are trying to use an outmoded NetBT protocol.
Does anyone know how to make this work?
RicohPDFSMBPortsCapture.PNG
netstatANO27FEB.txt
We use SBS 2011 and want to have our new Ricoh printer/scanners to scan to shares on the server.
Our server has SMB and it receives scans to shares on the server through port 445.
However, the new scanners only have the old NetBIos port 138 and 139 ports.
I don't know how to make the scanners connect properly to the server, nor how to make the server accept the ports that the scanner uses.
I have the sense that even if were to add the scanners ports 138 &139 to the SMB protocol on the server, that it would still not work because the new Ricoh scanners are trying to use an outmoded NetBT protocol.
Does anyone know how to make this work?
RicohPDFSMBPortsCapture.PNG
netstatANO27FEB.txt
ASKER
Rich, Thanks for the info and for the link. That is helpful.
So, what about SMB v2. Is it also something that I cannot use on my server? Can I use it and assign it both 445 and 139? Ricoh's list seems to indicate that they can use SMB v2 with port 139. Can I enable that on my server? (I am asking, but you can treat it as a rhetorical question if you wish.)
Thanks again, B.
So, what about SMB v2. Is it also something that I cannot use on my server? Can I use it and assign it both 445 and 139? Ricoh's list seems to indicate that they can use SMB v2 with port 139. Can I enable that on my server? (I am asking, but you can treat it as a rhetorical question if you wish.)
Thanks again, B.
SMBv2 should automagically use either 445 or 139 depending on whether it decides to use direct tcp, or the older NetBIOS after negotiation. Unfortunately, to tell the truth, since things so rarely breaks with SMB... it's not something I've done a lot of research on. I know a little working with some linux administrators in the past, that some SaMBa implementations don't negotiate the connection the way I'd expect (RedHat, for example was negotiating with a strong preference for SMBv1.)
As I recall, SBS 2011 uses Windows Server 2008 R2 under the hood, which supported SMBv1 and SMBv2. You shouldn't have to do anything else to enable SMBv2 on the server... I strongly suspect that's what is being used.
As I recall, SBS 2011 uses Windows Server 2008 R2 under the hood, which supported SMBv1 and SMBv2. You shouldn't have to do anything else to enable SMBv2 on the server... I strongly suspect that's what is being used.
What the Ricoh number. I.e. 2852
ASKER
It is a Ricoh SP C262SFNW Sorry about the delay. I added SMB v2 to the server and rebooted the server, but it did not help.
Out of curiosity, what did you do to add SMB v2 to the server?
(Were you able to confirm SMB v1 wasn't disabled on the server?)
(Were you able to confirm SMB v1 wasn't disabled on the server?)
Did you tried other ways to scan, like ftp or scan to email?
ASKER
Rich,
It was a PS
Set-ItemProperty -Path “HKLM:\SYSTEM\CurrentContr
Then reboot
That seemed to do the trick because before, the DWord did not exist, and before, the netstat -ano did not show the server listening on port 139, now, after the reboot, the DWord exists in its right state, and the netstat shows the server listening on TCP 139
In terms of gaining SMB communication between the Ricoh and the server though, we still get the same failure.
It was a PS
Set-ItemProperty -Path “HKLM:\SYSTEM\CurrentContr
Then reboot
That seemed to do the trick because before, the DWord did not exist, and before, the netstat -ano did not show the server listening on port 139, now, after the reboot, the DWord exists in its right state, and the netstat shows the server listening on TCP 139
In terms of gaining SMB communication between the Ricoh and the server though, we still get the same failure.
ASKER
I worked on this problem for quite awhile and hadn't found any better solutions than were given here. Eventually, the one's I've tagged as Best and Assisted were the most helpful and most useful. If you delete this some poor IT somewhere looking for a solution to a similar problem will be deprived of helpful information.
NOTE: This may not be secure anymore to do, but in Local Security Policy, Local Policies, Security Options, Network Security: LAN Manager auth level : set to LM & NTLM responses and then test the NTLMv2 only and see what works. By default this policy is not defined in 2008/7.
Older NAS devices needed this for 2008/7 as well as the old copiers that I have worked on years ago.
Older NAS devices needed this for 2008/7 as well as the old copiers that I have worked on years ago.
This question needs an answer!
Become an EE member today
7 DAY FREE TRIALMembers can start a 7-Day Free trial then enjoy unlimited access to the platform.
View membership options
or
Learn why we charge membership fees
We get it - no one likes a content blocker. Take one extra minute and find out why we block content.
Ricoh has a list of their various devices, and recommended solutions. You may be lucky, and your specific model may only need a firmware update.