crcsupport
asked on
Netbios and UNC path network path not found
I have a backup program which relies on netbios name connection to connect to a computer to upload files for backup.
One day, it started failing to connect. I ran following commands and the results are shown.
Firewall is turned off on both. What could be the problem?
Computer A: source to backup, windows 8
Computer B: server with backup software, windows 2003
From Computer A:
One day, it started failing to connect. I ran following commands and the results are shown.
Firewall is turned off on both. What could be the problem?
Computer A: source to backup, windows 8
Computer B: server with backup software, windows 2003
From Computer A:
ping A_hostname : OK
ping A_IP_Address: OK
net view \\A_hostname: System error 64 has occured. The specified network name is no longer available. Sometimes system error 53 has occured
net view \\A_IP_Address: System error 64 has occured. The specified network name is no longer available.
nbtstat -c: shows the entry for computer A correctly
Going to Network Places/Domain, double-clicking the Computer A shows the same error 'The specified network name is no longer available.'
Firewall on Computer A is turned off
Restarting Computer A doesn't help
Restarting Computer A's network card doesn't help
What could be the problem? I have feeling it's something wrong with netbios on Computer A, but did try many things, still not able to point out the problem.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
PS C:\WINDOWS\system32> Get-SmbServerConfiguration | fl *
AnnounceComment :
AnnounceServer : False
AsynchronousCredits : 64
AutoDisconnectTimeout : 0
AutoShareServer : True
AutoShareWorkstation : True
CachedOpenLimit : 5
DurableHandleV2TimeoutInSe conds : 30
EnableAuthenticateUserShar ing : True
EnableDownlevelTimewarp : False
EnableForcedLogoff : True
EnableLeasing : True
EnableMultiChannel : True
EnableOplocks : True
EnableSecuritySignature : False
EnableSMB1Protocol : True
EnableSMB2Protocol : False
EnableStrictNameChecking : True
EncryptData : False
IrpStackSize : 15
KeepAliveTime : 2
MaxChannelPerSession : 32
MaxMpxCount : 50
MaxSessionPerConnection : 16384
MaxThreadsPerQueue : 20
MaxWorkItems : 1
NullSessionPipes :
NullSessionShares :
OplockBreakWait : 35
PendingClientTimeoutInSeco nds : 120
RejectUnencryptedAccess : True
RequireSecuritySignature : False
ServerHidden : True
Smb2CreditsMax : 2048
Smb2CreditsMin : 128
SmbServerNameHardeningLeve l : 0
TreatHostAsStableStorage : False
ValidateAliasNotCircular : True
ValidateShareScope : True
ValidateShareScopeNotAlias ed : True
ValidateTargetName : True
PSComputerName :
CimClass : ROOT/Microsoft/Windows/SMB :MSFT_SmbS erverConfi guration
CimInstanceProperties : {AnnounceComment, AnnounceServer, AsynchronousCredits,
AutoDisconnectTimeout...}
CimSystemProperties : Microsoft.Management.Infra structure. CimSystemP roperties
AnnounceComment :
AnnounceServer : False
AsynchronousCredits : 64
AutoDisconnectTimeout : 0
AutoShareServer : True
AutoShareWorkstation : True
CachedOpenLimit : 5
DurableHandleV2TimeoutInSe
EnableAuthenticateUserShar
EnableDownlevelTimewarp : False
EnableForcedLogoff : True
EnableLeasing : True
EnableMultiChannel : True
EnableOplocks : True
EnableSecuritySignature : False
EnableSMB1Protocol : True
EnableSMB2Protocol : False
EnableStrictNameChecking : True
EncryptData : False
IrpStackSize : 15
KeepAliveTime : 2
MaxChannelPerSession : 32
MaxMpxCount : 50
MaxSessionPerConnection : 16384
MaxThreadsPerQueue : 20
MaxWorkItems : 1
NullSessionPipes :
NullSessionShares :
OplockBreakWait : 35
PendingClientTimeoutInSeco
RejectUnencryptedAccess : True
RequireSecuritySignature : False
ServerHidden : True
Smb2CreditsMax : 2048
Smb2CreditsMin : 128
SmbServerNameHardeningLeve
TreatHostAsStableStorage : False
ValidateAliasNotCircular : True
ValidateShareScope : True
ValidateShareScopeNotAlias
ValidateTargetName : True
PSComputerName :
CimClass : ROOT/Microsoft/Windows/SMB
CimInstanceProperties : {AnnounceComment, AnnounceServer, AsynchronousCredits,
AutoDisconnectTimeout...}
CimSystemProperties : Microsoft.Management.Infra
ASKER
Both Computer A and B, firewall is off
ASKER
One thing I noticed, I have two windows 8.1 computers. The other Windows 8.1 computer doesn't have this problem, all windows version OS can browse the computer with \\net view. So I compared the get-smbserverconfiguration , ont thing I noticed different;
Computer A(troubled computer):
EnableAuthenticateUserShar ing : True
Computer C (working without any problme, all Windows (xp, 7, 8.1) can browse this compuer using net view \\C_hostname):
EnableAuthenticateUserShar ing : False
I made this paramter on Computer A to 'False', but not working, but this is the only different value when I compare the two computers.
Computer A(troubled computer):
EnableAuthenticateUserShar
Computer C (working without any problme, all Windows (xp, 7, 8.1) can browse this compuer using net view \\C_hostname):
EnableAuthenticateUserShar
I made this paramter on Computer A to 'False', but not working, but this is the only different value when I compare the two computers.
ASKER
I changed EnableAuthenticateUserShar ing to False then restarted PC, it works PERFECT.
Anyone knows what this parameter is? I can't find good explanation in powershell manual..
I think this parameter was changed after windows update, my guess..
Anyone knows what this parameter is? I can't find good explanation in powershell manual..
I think this parameter was changed after windows update, my guess..
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Reading what that parameter is for besides share permission and NTFS security. It seems like internal seperate authentication of SMB...
ASKER
I was able to generate the problem on another computer sending command 'net view \\A_hostname'.
When I disable SMB 2/3, from Windows 7 computer, it also shows system error 53. So, I guess it's smb related issue, not firewall or netbios.
But once I disable SMB 2/3 (it doesn't allow to disable only SMB 3, powershell command), I was not able to browse Computer A from all Windows version, xp,2003, 7. So, I guess somehow Computer doens't negotiate SMB down to SMB1 when 2003/xp browse to Computer A....