Displaying 3 results from an estimated 3 matches for "nt_status_invalid_network".
2024 Apr 11
1
Ancient SMB client issues
...ebian/Samba 4.19 server with the intention of moving over the SMB shares that the robots need to this server. If I connect from Windows 10 clients to the Samba servers shares, no issues. If I try the same from the robot (ancient SMB) then it fails with the rather bleak ?protocol negotiation failed: NT_STATUS_INVALID_NETWORK?. I get this error regardless of the min protocol level (NT1 or SMB2) on the server.
In short, are we doomed to stay with the unsafe Windows share connections, or is there another way to migrate from Windows to Linux? Maybe running an ancient Samba too, but that does not sound too attractive?
2024 Apr 11
1
Ancient SMB client issues
...ith the intention
> of moving over the SMB shares that the robots need to this server. If
> I connect from Windows 10 clients to the Samba servers shares, no
> issues. If I try the same from the robot (ancient SMB) then it fails
> with the rather bleak ?protocol negotiation failed:
> NT_STATUS_INVALID_NETWORK?. I get this error regardless of the min
> protocol level (NT1 or SMB2) on the server.
>
> In short, are we doomed to stay with the unsafe Windows share
> connections, or is there another way to migrate from Windows to
> Linux? Maybe running an ancient Samba too, but that does not...
2024 Apr 11
1
Ancient SMB client issues
...t;> of moving over the SMB shares that the robots need to this server. If
>> I connect from Windows 10 clients to the Samba servers shares, no
>> issues. If I try the same from the robot (ancient SMB) then it fails
>> with the rather bleak ?protocol negotiation failed:
>> NT_STATUS_INVALID_NETWORK?. I get this error regardless of the min
>> protocol level (NT1 or SMB2) on the server.
>>
>> In short, are we doomed to stay with the unsafe Windows share
>> connections, or is there another way to migrate from Windows to
>> Linux? Maybe running an ancient Samba too...