Re: SMB "Login Error"
It's not an incorrect username / password. Believe me, I've been thru that scenario in my head 5 times. I have checked and rechecked credentials over and over. If one thing is right, it's the credentials. It's so odd that the copier error log lists the username as "Public", which isn't even close to what I'm using as the username.
I had originally tried to authenticate via the local.machine account. After that, I tried a domain account. I used all caps on everything but the passwords. NTLM is set to v1/v2. I have not tried change this to v2 only.
I can hit the target machine and shared folder from another Windows machine. I have not tried to make a Firewall exception for p139.
This is a leased machine. Is it possible that my organization must pay for SMB to be unlocked? Keep in mind that I am able to configure it via the Admin area. I can see and change all the settings for SMB (and everything else). Unfortunately I was out of the loop during the acquisition, this thing just magically appeared one morning. I'd love to send it back...back to the murky and dysfunctional non-SMB-handling depths from which it came. Our old copier worked fine; progress.... Oh well, at least they plugged in the ethernet cable. *sigh*
Scratch that, it's not leased. Paid in full with all features unlocked.....
It's not an incorrect username / password. Believe me, I've been thru that scenario in my head 5 times. I have checked and rechecked credentials over and over. If one thing is right, it's the credentials. It's so odd that the copier error log lists the username as "Public", which isn't even close to what I'm using as the username.
I had originally tried to authenticate via the local.machine account. After that, I tried a domain account. I used all caps on everything but the passwords. NTLM is set to v1/v2. I have not tried change this to v2 only.
I can hit the target machine and shared folder from another Windows machine. I have not tried to make a Firewall exception for p139.
This is a leased machine. Is it possible that my organization must pay for SMB to be unlocked? Keep in mind that I am able to configure it via the Admin area. I can see and change all the settings for SMB (and everything else). Unfortunately I was out of the loop during the acquisition, this thing just magically appeared one morning. I'd love to send it back...back to the murky and dysfunctional non-SMB-handling depths from which it came. Our old copier worked fine; progress.... Oh well, at least they plugged in the ethernet cable. *sigh*
Scratch that, it's not leased. Paid in full with all features unlocked.....
Comment