Greetings,
I've spent a long time trying to figure this out and am left with nothing but stress. It is kind of embarrassing, but here goes:
I'm consulting to a company with:
- Win 2k8 R1 32bit Server (Jack of all trades- DC, DNS, DHCP, File, Print)
- Win 7 Pro 64 bit clients
The network is fine and we're all fat dumb and happy.
I'm trying to access a shared folder on the server with my Linux (openSuSE 11.4) laptop. This computer is not part of the domain, nor does it want to be. I connect to the VPN to get to the network.
From what I can tell (and I've done this with other networks) I should be able to get to the share via:
However, when I do so, I get
I figure this has to be a mod to the group policy in how authentication happens, but I can't find it.
Thanks, in advance for help.
"Nothing is so common-place as the wish to be remarkable."
--Shakespear
I've spent a long time trying to figure this out and am left with nothing but stress. It is kind of embarrassing, but here goes:
I'm consulting to a company with:
- Win 2k8 R1 32bit Server (Jack of all trades- DC, DNS, DHCP, File, Print)
- Win 7 Pro 64 bit clients
The network is fine and we're all fat dumb and happy.
I'm trying to access a shared folder on the server with my Linux (openSuSE 11.4) laptop. This computer is not part of the domain, nor does it want to be. I connect to the VPN to get to the network.
From what I can tell (and I've done this with other networks) I should be able to get to the share via:
Code:
smbclient //x.x.x.x/Share -U user -W domain
However, when I do so, I get
Code:
session setup failed: NT_STATUS_LOGON_FAILURE
I figure this has to be a mod to the group policy in how authentication happens, but I can't find it.
Thanks, in advance for help.
"Nothing is so common-place as the wish to be remarkable."
--Shakespear