Hello All, I am having this issue that seems to be a problem. In my situation, the users' computers were re-imaged with Win7 Enterprise x64, now these users are able to access some network shares while two specific network shares are not showing up. I have tried many suggestions to no avail and since this situation is unique in the sense that some share drives show up in the users' profiles but two specific ones do not show up. Our server team said the user's permissions have not changed on any of the shares, so I am unsure where else to look. Windows Firewall is off via Group Policy. File & Printer Sharing and Network Discovery are enabled. I have uninstalled Symantec Enterprise AV but that did not solve the problem so I re-installed it. But there is still no consistency as to why just these two shares are the only ones affected when other shares show up. The inconsistency is not making sense unless there is an issue on the server end which I doubt but unsure about since that is another team and they already said nothing has changed. The server is Windows Server 2003. When I try using the server name, it gives the check spelling error but if I use the server IP address in the path it says the mapped network drive could not be created because the following error has occurred: The account is not authorized to log in from this station. This was addressed in this MS article which points me at group policy, I tried updating and it says it has updated but does not prompt for a reboot as it is supposed when it really updates; http://support.microsoft.com/kb/281648 Safe Mode with Networking yielded the same results but logging in on a totally different computer running XP Pro showed the drives including those that fail to show up in Win7. Thanks, J

Hi, It sounds like a SMB Signing issue. Please made this change in the registry to troubleshoot this problem. HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\lanmanworkstation\parameters Enablesecuritysignature [REG_DWORD] = 0x0 For more information about SMB Signing: Overview of Server Message Block signing http://support.microsoft.com/kb/887429/en-us Kim Zhou TechNet Community Support

Things Microsoft Upgraded. 1. 2003 Server and XP, Vista Uses SMB 1.0 Protocol , Whereas, 2008 Server and Windows 7 & Win8 Uses SMB 2.0 Protocol 2.Server 2008 and Windows 7,8 Has Got Kerberos 7.0 ..but xp , vista has running on 3.0 versions there is always Forward and Backward Compatibilty Issues in Windows Products,Be it Service Packs Or RC1 or RC2 . Everytimes they Push Updates , Hot fixes blah blah ...so that is the thing make Linux users to annoy over Windows If There is Any Update Out For Linux Distros it will available free for users , But For Windows Users only Legitimate can Update Heres how Windows Behaves it can help u find the root cause analysics, when we know the problem the closer we are to resolve it Here's how SMB is used when related to SMB versions: When a Windows Server 2008/Vista "client" connects to a Windows Server 2008/Vista "server", SMB 2.0 is used. When a Windows Server 2008/Vista "client" connects to a Windows 2000/XP/2003 "server", SMB 1.0 is used. When a Windows 2000/XP/2003 "client" connects to a Windows Server 2008/Vista "server", SMB 1.0 is used. When a Windows 2000/XP/2003 "client" connects to a Windows 2000/XP/2003 "server", SMB 1.0 is used. coming to point , so when u Connect to server with the recent SMB 2.0 Version u may unable to connect, So i want u to disable the SMB2.0 in Windows 7 ... To Disable the SMB 2.0 Fire Up the Command Prompt with Elevated Mode: type the below: Quote: sc config lanmanworkstation depend= bowser/mrxsmb10/nsi sc config mrxsmb20 start= disabled Note there's an extra " " (space) after the "=" sign. To Enable SMB 2.0 Command Prompt: Quote: sc config lanmanworkstation depend= bowser/mrxsmb10/mrxsmb20/nsi sc config mrxsmb20 start= auto Again, note there's an extra " " (space) after the "=" sign. To Disable it in Server 2008 Regedit-> Fly to This PLace by Yourself : HKLM\System\CurrentControlSet\Services\LanmanServer\Parameters Add a new REG_DWORD key with the name of "Smb2" (without quotation mark) Value name: Smb2 Value type: REG_DWORD 0 = disabled 1 = enabled Set the value to 0 to disable SMB 2.0, or set it to 1 to re-enable SMB 2.0. Reboot the server.Face the fact tat we all have plenty to learn about this field. Deal wit the failures, use tem as motivation, learn something new everyday. Claiming false credentials & phantom skillsets will not get you far, especially when 63248651487512645876531864 people in the universe know how 2 use the internet Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. Please VOTE as HELPFUL if the post helps you. This can be beneficial to other community members reading the thread.

I hope this Will be Very Helpfull i have answered to a post same as your problem 0*80070035 Error , How to Fix it ? Thanks, SurenFace the fact tat we all have plenty to learn about this field. Deal wit the failures, use tem as motivation, learn something new everyday. Claiming false credentials & phantom skillsets will not get you far, especially when 63248651487512645876531864 people in the universe know how 2 use the internet Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. Please VOTE as HELPFUL if the post helps you. This can be beneficial to other community members reading the thread.

Thanks for the responses. I have enabled NetBIOS over TCP/IP, Safe mode with networking, disabled Windows firewall, uninstalled McAfee AV (but not the agent), etc. When the user log into another computer with a different image, all her drives including the ones missing on the other computer show up. So it is certainly something on the computer. Even someone from the server team has been working on it to no avail. I will try the SMB Signing suggestion to see if it resolves the issue before wiping the computer with the new image.

Things Microsoft Upgraded. 1. 2003 Server and XP, Vista Uses SMB 1.0 Protocol , Whereas, 2008 Server and Windows 7 & Win8 Uses SMB 2.0 Protocol 2.Server 2008 and Windows 7,8 Has Got Kerberos 7.0 ..but xp , vista has running on 3.0 versions there is always Forward and Backward Compatibilty Issues in Windows Products,Be it Service Packs Or RC1 or RC2 . Everytimes they Push Updates , Hot fixes blah blah ...so that is the thing make Linux users to annoy over Windows If There is Any Update Out For Linux Distros it will available free for users , But For Windows Users only Legitimate can Update Heres how Windows Behaves it can help u find the root cause analysics, when we know the problem the closer we are to resolve it Here's how SMB is used when related to SMB versions: When a Windows Server 2008/Vista "client" connects to a Windows Server 2008/Vista "server", SMB 2.0 is used. When a Windows Server 2008/Vista "client" connects to a Windows 2000/XP/2003 "server", SMB 1.0 is used. When a Windows 2000/XP/2003 "client" connects to a Windows Server 2008/Vista "server", SMB 1.0 is used. When a Windows 2000/XP/2003 "client" connects to a Windows 2000/XP/2003 "server", SMB 1.0 is used. coming to point , so when u Connect to server with the recent SMB 2.0 Version u may unable to connect, So i want u to disable the SMB2.0 in Windows 7 ... To Disable the SMB 2.0 Fire Up the Command Prompt with Elevated Mode: type the below: Quote: sc config lanmanworkstation depend= bowser/mrxsmb10/nsi sc config mrxsmb20 start= disabled Note there's an extra " " (space) after the "=" sign. To Enable SMB 2.0 Command Prompt: Quote: sc config lanmanworkstation depend= bowser/mrxsmb10/mrxsmb20/nsi sc config mrxsmb20 start= auto Again, note there's an extra " " (space) after the "=" sign. To Disable it in Server 2008 Regedit-> Fly to This PLace by Yourself : HKLM\System\CurrentControlSet\Services\LanmanServer\Parameters Add a new REG_DWORD key with the name of "Smb2" (without quotation mark) Value name: Smb2 Value type: REG_DWORD 0 = disabled 1 = enabled Set the value to 0 to disable SMB 2.0, or set it to 1 to re-enable SMB 2.0. Reboot the server.Face the fact tat we all have plenty to learn about this field. Deal wit the failures, use tem as motivation, learn something new everyday. Claiming false credentials & phantom skillsets will not get you far, especially when 63248651487512645876531864 people in the universe know how 2 use the internet Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. Please VOTE as HELPFUL if the post helps you. This can be beneficial to other community members reading the thread.

If the drive is missing when user logged on another compputer means its due to group policy not updated in her machine bro Please check gpresult on client computer to see if the group policy is applied or not. Check Event log and see if there is any related error. Also test to manually map the drive on a client computer. Thanks, SurenFace the fact tat we all have plenty to learn about this field. Deal wit the failures, use tem as motivation, learn something new everyday. Claiming false credentials & phantom skillsets will not get you far, especially when 63248651487512645876531864 people in the universe know how 2 use the internet Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. Please VOTE as HELPFUL if the post helps you. This can be beneficial to other community members reading the thread.