gl-1020 scan to file issue with Win2003 domain

[bmusgrove]

I have a problem with scanning to a file using a GL-1020 on a windows 2003 server domain (win2000 native mode). This worked fine before the upgrade form NT4 domain to Win2003. I understand the GL-1020 cannot digitally sign SMB, so that has been turned off on the domain controllers using GPO.

It is definitely a authentication issue. I took a domain pc and set up a share on it. I created a local user, gave the local user and a domain user access to the share. Using the local user in the scan template, the scan worked fine. Using the domain user, the scan failed each time with a

"Specified \\\\pcname\\scan path is invalid. Check destination path"

error. The user name and password was the only thing changed in the scan template. I have tried several different naming conventions for the domain user includung

username
domain\username
username@dominname (fully qualified as yyy.zzz.org)

In the hopes that may work. No joy.

Suggestions?

[oeshuron]

I have a problem with scanning to a file using a GL-1020 on a windows 2003 server domain (win2000 native mode). This worked fine before the upgrade form NT4 domain to Win2003. I understand the GL-1020 cannot digitally sign SMB, so that has been turned off on the domain controllers using GPO.

It is definitely a authentication issue. I took a domain pc and set up a share on it. I created a local user, gave the local user and a domain user access to the share. Using the local user in the scan template, the scan worked fine. Using the domain user, the scan failed each time with a

"Specified \\pcname\scan path is invalid. Check destination path"

error. The user name and password was the only thing changed in the scan template. I have tried several different naming conventions for the domain user includung

username
domainusername
username@dominname (fully qualified as yyy.zzz.org)

In the hopes that may work. No joy.

Suggestions?

We are having the same issue. Will not scan to folder on a domain user.

[jreed]

I had this exact problem. I am trying to remember, but I think we had to add a "\" to the end of the path. So, it would end up being \\pcname\\scan\

I would verify this, but our controller on our 550 has crashed again, for the 5th time in 3 months. So, I dont have access to it at this point.

[oeshuron]

I had this exact problem. I am trying to remember, but I think we had to add a "" to the end of the path. So, it would end up being \pcname\scan

I would verify this, but our controller on our 550 has crashed again, for the 5th time in 3 months. So, I dont have access to it at this point.

If this works, I'm going to feel sooooooo stupid for not trying it.

[oeshuron]

I haven't had a chance to try that yet, but if anyone has the discs (I believe there are 4) I would really appreciate it if you could contact me via PM. Or see my thread about them in the For Sale/Wanted Section.

[oeshuron]

If this works, I'm going to feel sooooooo stupid for not trying it.

This didn't work. Always destination not found type message. Is this a domain problem? Too old of a controller? Someone HELP please

[DallasTech]

If you are scanning successfully to a non-server 2003 computer and having problems with authentication, you want to make sure SMB signing is turned off. The easy way to check this is by looking at the registry Start->Run->type "regedit"

Both of the following registry entries need to be disabled.

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\LanManServer\Parameters

Value Name: EnableSecuritySignature
Data Type: REG_DWORD
Data: 0 (disable), 1 (enable)

Note The default value in Windows Server 2003 domain controllers and Windows 2000 domain controllers is 1 (enabled). The default value in Windows NT 4.0 domain controllers is 0 (disabled).

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\LanManServer\Parameters

Value Name: RequireSecuritySignature
Data Type: REG_DWORD
Data: 0 (disable), 1 (enable)

Note The default value in Windows Server 2003 domain controllers and Windows 2000 domain controllers is 1 (required). The default value in Windows NT 4.0 domain controllers is 0 (not required).

[Arative]

If you are scanning successfully to a non-server 2003 computer and having problems with authentication, you want to make sure SMB signing is turned off. The easy way to check this is by looking at the registry Start->Run->type "regedit"

Both of the following registry entries need to be disabled.

HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServicesL anManServerParameters

Value Name: EnableSecuritySignature
Data Type: REG_DWORD
Data: 0 (disable), 1 (enable)

Note The default value in Windows Server 2003 domain controllers and Windows 2000 domain controllers is 1 (enabled). The default value in Windows NT 4.0 domain controllers is 0 (disabled).

HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServicesL anManServerParameters

Value Name: RequireSecuritySignature
Data Type: REG_DWORD
Data: 0 (disable), 1 (enable)

Note The default value in Windows Server 2003 domain controllers and Windows 2000 domain controllers is 1 (required). The default value in Windows NT 4.0 domain controllers is 0 (not required).

I'm having the same problem. Checked the SMB and it was disabled. Any suggestions?

[Humedss]

These controllers do not log into Domain controllers, if you have problems scanning with the name of the computer..... use the IP. \\10.10.10.10\file\etc instead of \\server\file\etc.