Lanier LD117 scan uploads are slow when NetBIOS disabled on remote share
-
Well just for laughs, try and ping the MFP by it's name which is obscured.
I'm assuming you can ping by IP address without issue.
-
@DustinB3403 said in Lanier LD117 scan uploads are slow when NetBIOS disabled on remote share:
Well just for laughs, try and ping the MFP by it's name which is obscured.
I'm assuming you can ping by IP address without issue.
I use a web browser to configure it. I took the above shots from the web console for the MFP.
I can ping by IP, but not by hostname. But I don't use the hostname for anything, so that should be fine.Again, the OP is about a slowness issue, not a lack of connectivity issue - I do have connectivity, I just have slowness to the order of 10 times slower.
-
I reached out to my VAR - they want $37/15 min for support. Yeah probably not
-
Is the slowness visible during pinging, or just using the scanner?
-
Did you actually do a full power cycle on the copier? I would guess the netbios setting did not fully apply.
-
@cnewman we need your programming skills!
-
@JaredBusch said in Lanier LD117 scan uploads are slow when NetBIOS disabled on remote share:
Did you actually do a full power cycle on the copier? I would guess the netbios setting did not fully apply.
After making the NetBIOS change, nope, I'll do that now - good idea.
I rebooted it earlier, but not after the NetBIOS change.
-
No change after rebooting.
This is just another larger picture of the window of options from above, no changes.
-
-
Nope, all on the same subnet.
-
You are using IP of the SMB share not the hostname? if if using the hostname make sure it's FQDN not the NetBios hostname it tries WINS lookup before doing DNS and appending the search domain like that which will slow down the lookup. I'd just use IP.
Here we scan to email with our Ricoh's though.
-
When I added DNS entries a week ago to fix the name resolution problem, I changed all the \\servername\sharename\folder into \\servername.FQDN\sharename\foldername
WINS is disabled (there are no IPs listed in the printers settings).
Once the user returned and complained about the slowness, I setup a new connection with just \\servername\sharename\folder and \\IP Address\sharename\folder both of which provided the same delays.
-
I'm about to hit up one of my other machines and see if it's doing the same thing.
This image shows that all three machines, all are LD117 MFPs, have different versions of firmware throughout the gambit of firmwares these machines have.
-
Sounds like it is time for wireshark to see what traffic it is actually sending.
-
OK all three machines have the same slow behavior.
Might try wireshark tomorrow.
-
@Dashrender said in Lanier LD117 scan uploads are slow when NetBIOS disabled on remote share:
OK all three machines have the same slow behavior.
Might try wireshark tomorrow.
Or just try putting it in with the IP first and see if the problem goes away.
\\1.2.3.4\share\path\here -
@JaredBusch said in Lanier LD117 scan uploads are slow when NetBIOS disabled on remote share:
@Dashrender said in Lanier LD117 scan uploads are slow when NetBIOS disabled on remote share:
OK all three machines have the same slow behavior.
Might try wireshark tomorrow.
Or just try putting it in with the IP first and see if the problem goes away.
\\1.2.3.4\share\path\here@Dashrender said in Lanier LD117 scan uploads are slow when NetBIOS disabled on remote share:
Once the user returned and complained about the slowness, I setup a new connection with just
\\servername\sharename\folder
and
\\IP Address\sharename\folder
both of which provided the same delays.Edited for clarification.
-
This is not a NetBIOS issue then..
-
@Jason said in Lanier LD117 scan uploads are slow when NetBIOS disabled on remote share:
This is not a NetBIOS issue then..
While you might have assumed I said that it was, The symptom only showed itself after this change was made. Before the user went on vacation and while she was gone, the only change that was made was that NetBIOS was disabled, and DNS added to the printer along with putting FQDN in the SMB paths for the fileshare location.
