Ok
so we migrated from a Windows 2008 server to Windows 2012, and our automated build system hudson could no longer copy it's files over to the new server.
using smbclient to create a directory on the fileserver, didn't work after we migrated.
smbclient //server01.corp/dfs_shared/ -U username%password
The old file server could authenticate us, with both the hudson account and our domain admin accounts. The new file server couldn't.
we checked:
firewall rules (hardware)
firewall rules (windows)
local policy (Net lanman auto type -v1/v2)
Eventually,
I figured out this worked.
smbclient //server01.corp/dfs_shared/ -U domain\\username%password
The reason being that we were now authenticating against a file server ONLY. The previous server was also a domain controller (which has no concept of a local account). As the new server was a file server only, when it was authing, it was checking against it's local account, which obviously, doesn't exist.
so we migrated from a Windows 2008 server to Windows 2012, and our automated build system hudson could no longer copy it's files over to the new server.
using smbclient to create a directory on the fileserver, didn't work after we migrated.
smbclient //server01.corp/dfs_shared/ -U username%password
The old file server could authenticate us, with both the hudson account and our domain admin accounts. The new file server couldn't.
we checked:
firewall rules (hardware)
firewall rules (windows)
local policy (Net lanman auto type -v1/v2)
Eventually,
I figured out this worked.
smbclient //server01.corp/dfs_shared/ -U domain\\username%password
The reason being that we were now authenticating against a file server ONLY. The previous server was also a domain controller (which has no concept of a local account). As the new server was a file server only, when it was authing, it was checking against it's local account, which obviously, doesn't exist.
No comments:
Post a Comment