Link to home
Start Free TrialLog in
Avatar of rookie_b
rookie_bFlag for United Kingdom of Great Britain and Northern Ireland

asked on

Cannot connect to linux smb share from Windows 7 - error 64 the specified network name is no longer available

Hello,

I cannot connect to linux smb share from Windows 7 - error 64 the specified network name is no longer available is the error I get, but also network path not found error 53, and the specified server cannot perform the requested information

I have tried using the netbios name, the fqdn and ip address of the smb server.

Any ideas?

Thanks!
SOLUTION
Avatar of dipopo
dipopo
Flag of United Kingdom of Great Britain and Northern Ireland image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of rookie_b

ASKER

Hi,


Thanks for the quick response!

I am able to ping the ip, as well as the fqdn
it is not a new share, I am able to browse the share from a server 2208r2 and server2012 on the same domain as the windows 7 machines
I have disable firewall on the client
I can telnet into the tcp ports 139 and 445
OK, can you restart the workstation service on your PC and try the UNC path again?
tried it, no change. Multiple windows 7 pcs exhibit the same behaviour
ASKER CERTIFIED SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
I tried that, and it seems that the connection is being re-set immediately. It happens when I try to connect to any unix based smb share, not just that particular one.
Are you able to filter for the traffic to the SMB server on your capture and post here if unsure.
I managed to narrow it down to one local  security policy setting:

"Microsoft network client: Digitally sign communications (always) - enabled"

The default appears  to be disabled, at least on all other machines I checked - enabling it causes the problem. I would very much like to know what caused this setting to become enabled. I don't think it is a GPO, as it keeps it  after moving the machine to a different OU (containing machines that work fine and don't have the setting enabled), or even after removing the PC from the domain altogether.

 It is a pretty standard image - Windows 7 Enterprise + updates, + management framework 3, + dependencies (.net 4.5, ms visual c++ redist, flash, java)+ U-EV client, Application Jukebox client. We have recently implemented PKI, if that may have something to do with it,  but as i said it seems to be a local policy, not a group one.


Any ideas on what might be the reason the setting became enabled?

Thanks!
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial