Unable to access network share files from one server


Recommended Posts

Hi all,

 

Unable to access network files (e.g. \\servername\c$) from newly build windows server 2012.

FYI, By IP address of target network server we can access the ping, RDP as well as network files, and if we do 2012 server reboot then this will work for 2-3 days or longer as a week. 

This issue occurred for just for one single server others 700 servers are working as expected.

Guys, please help me for this issue.    

 

 

  On 20/03/2014 at 11:32, Chandgude said:

Then how it will works after win2012 server reboot?? 

 

One more information I would like to add, If I tried to access same network server from any windows 2008 or other 2012 servers it is working fine. but same userID this is not working in one particular windows server 2012. 

And what error do you get?  From a command line when you try and access \\servername\c$ what do you get for an error?

 

net use \\servername\c$

 

do you get access denied and asked for credentials?  Do you have any other sessions open to this machine?  You say you can access not admin shares just fine?

 

Are you sure the shares are there?  They could be recreated on reboot.. So what does net share look like when ran on the server?

 

exmaple

 

post-14624-0-09940200-1395315814.png

 

 

edit:

"but same userID this is not working in one particular windows server 2012."

 

That points to this box you can not access other server from having a session open to the server that does not have the rights to access the admin shares to me - your saying it can access other network shares?  Check what sessions this machine has open.  For example if something mapped to this server as user X, you can then not access server as user Y.

  On 20/03/2014 at 11:32, Chandgude said:

Then how it will works after win2012 server reboot??

Your OP wasn't clear, sorry.

Maybe someone is messing around with permissions or they are getting reset...

What is the exact error when you try to access the network share?

  On 20/03/2014 at 11:43, BudMan said:

And what error do you get?  From a command line when you try and access \\servername\c$ what do you get for an error?

 

net use \\servername\c$

 

do you get access denied and asked for credentials?  Do you have any other sessions open to this machine?  You say you can access not admin shares just fine?

 

Are you sure the shares are there?  They could be recreated on reboot.. So what does net share look like when ran on the server?

 

exmaple

 

attachicon.gifadminshares.png

 

 

edit:

"but same userID this is not working in one particular windows server 2012."

 

That points to this box you can not access other server from having a session open to the server that does not have the rights to access the admin shares to me - your saying it can access other network shares?  Check what sessions this machine has open.  For example if something mapped to this server as user X, you can then not access server as user Y.

 

Hi Budman,

 

net use \\servername\c$  

Got below error message,

 

System error 64 has occurred.
 
The specified network name is no longer available.
 
by IP it's gave success msg...
 
But same I have tried on my 2008 server there I got, The command completed successfully message
Also i have tried from three different userID from different machines and we successfully access the \\servername\c$.

So that is a really generic error.. what do you get when you do net view \\servername ?

 

Your saying you can access all the other shares on this box, just not C$ from this location?

  On 20/03/2014 at 12:55, BudMan said:

So that is a really generic error.. what do you get when you do net view \\servername ?

 

Your saying you can access all the other shares on this box, just not C$ from this location?

 

Same issue for \\servername, or \\Servername\c$ or servername\D$... 

My concern is only that what is the reason that am not able to access network server from one 2012 server????

 

let me clear the scenario, 

 

e.g. I have below servers in my organization. 

 

PC1 = Hostname is SCCMwin2012

PC2 = Hostname is SQLwin2008

PC3 = Hostname is webwin2008

PC4 = Hostname is SCOMwin2012

PC5 = Hostname is DCwin2008

PC6 = Hostname is DHCPwin2008

PC7 = Hostname is Serverwin2008

PC8 = Hostname is server2win2012

 

All above machine in one domain, and can be ping each other, accessing data by using \\servername\**$ (any drive) but but but.

 

from PC1(SCCMwin2012) can not access data of server PC2 (SQLwin2008). (\\servername, \\servername\C$ any share not working here.) if I do reboot SCCMwin2012 server then only able to access SQLwin2008 data from network.

 

pls let me know if in case still any concerns. 

\\servername doesn't work....hmmm, active directory?  if so what are your dns servers in ip properties (ipconfig/all)...sounds like  you are trying to resolve by name and you can't, if you can connect via IP address. 

  On 20/03/2014 at 13:59, CCS-IT said:
  On 20/03/2014 at 13:59, CCS-IT said:
  On 20/03/2014 at 13:59, CCS-IT said:
 
  On 20/03/2014 at 16:20, CCS-IT said:

 

  On 20/03/2014 at 13:59, CCS-IT said:
  On 20/03/2014 at 13:59, CCS-IT said:
  On 20/03/2014 at 13:59, CCS-IT said:

 

Found following events in windows server 2012 machine.... {ID 30620, Warning_Microsoft-Windows-SMBClient Microsoft-Windows-SMBClient/Operational - Connection to server \servername IP Address x.x.x.x:445 was aborted.}

 

FYI. NIC MTU is set as 1500 on source and destination machine. 

So your saying this SCCMwin2012 can not access any other server?  And if you reboot it you can only access the one SQLwin2008 box?

 

how are you checking mtu? 

 

C:\>netsh interface ipv4 show subinterfaces

   MTU  MediaSenseState   Bytes In  Bytes Out  Interface
------  ---------------  ---------  ---------  -------------
4294967295                1          0      23269  Loopback Pseudo-Interface 1
  1500                5          0          0  Wireless Network Connection
  1500                1  347094734   21410209  Local Area Connection
  1500                5          0          0  Local Area Connection* 11
  1400                5          0          0  Local Area Connection* 17
  1500                1   21162628    1569741  vpn

 

This show 1500?

  On 20/03/2014 at 18:59, BudMan said:

So your saying this SCCMwin2012 can not access any other server?  And if you reboot it you can only access the one SQLwin2008 box?

 

how are you checking mtu? 

 

C:\>netsh interface ipv4 show subinterfaces

   MTU  MediaSenseState   Bytes In  Bytes Out  Interface

------  ---------------  ---------  ---------  -------------

4294967295                1          0      23269  Loopback Pseudo-Interface 1

  1500                5          0          0  Wireless Network Connection

  1500                1  347094734   21410209  Local Area Connection

  1500                5          0          0  Local Area Connection* 11

  1400                5          0          0  Local Area Connection* 17

  1500                1   21162628    1569741  vpn

 

This show 1500?

 

Yes, I checked MYU by using same command as you mentioned. and I sow 1500 MTU from that command output.

 

SCCMwin2012 can access all servers which are listed in my previous post, except  SQLwin2008... I can ping SQLwin2008 from SCCMwin2012 server but can not access the RDP as well as data from SQLwin2008 machine. 

"but can not access the RDP as well as data from SQLwin2008 machine. "

 

Well RDP is completely different -- do you get prompted for access and denied, or get told can not find.. What error do you get when you try and RDP to its IP address.  And your saying other machines can rdp to sqlwin2008 just fine.

Budman,

As per the weekend patching we have rebooted SQLwin2008 server, hence as I told earlier post that after reboot issue getting resolved and now we all are accessing the server resources from our WinSCCM2012 machine.

 

FYI error msg: "Specified network name is no longer available" while accessing network data.. (\\servername\c$) if we do \\10.xx.xx.xx\c$ it's accessible perfectly. 

 

I'll keep you posted once issue re-occur.

  • 2 weeks later...
This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • I am afraid to ask but what specific crowd are you talking about? Most people wanted Mozilla to concentrate on the browser but of course are still complaining when they do that. Anyway Firefox works just fine for me. We all deserve the Chrome only future that is coming.
    • Such a missed opportunity for a company with arena sized buckets of cash. The first on device AI and they never really improved it all those years. They could have been leading this charge.
    • Glow 25.06 by Razvan Serea Glow provides detailed reporting on every hardware component in your computer, saving you valuable time typically spent searching for CPU, motherboard, RAM, graphics card, and other stats. With Glow, all the information is conveniently presented in one clean interface, allowing you to easily access and review the comprehensive hardware details of your system. Glow provides detailed information on various system aspects, including OS, motherboard, processor, memory, graphics card, storage, network, battery, drivers, and services. The well-organized format ensures easy access to the required information. You can export all the gathered data to a plain text file, facilitating sharing with others for troubleshooting purposes. No installation needed. Just decompress the archive, launch the executable, and access computer-related information. Glow runs on Windows 11 and Windows 10 64-bit versions. Glow 25.06 release notes: What's new Support provided for Windows 11 24H2 May 2025 update. Support provided for Intel Arrow Lake-H series processors. Support for AMD Ryzen AI series processors. Support for NVIDIA RTX 50 series graphics cards. Support for AMD RX 9000 series graphics cards. Support for processors and graphics cards from Intel, AMD and NVIDIA until May 2025. Support for GDDR7 graphics memory. .NET Framework June 2025 security update has been integrated. Fixed Bugs Fixed DPI bug in the Memory Test Tool that caused buttons to be nested with the table at 150% DPI and above. Fixed a translation bug in the Cache Cleanup Tool that caused an incorrect character encoding set in the Russian language. Fixed various DPI bug and character encoding bug fixes. Note: Always unzip the program before using it. Otherwise you may get an error. Download: Glow 25.06 | 2.0 MB (Open Source) View: Glow Homepage | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • How to enable the redesigned Windows 11 Start menu by Taras Buria This week, Microsoft started testing a big redesign for Windows 11's Start menu. It is now rolling out to Windows Insiders in the Dev and Beta Channels, addressing quite a few pain points in the original Start menu, which was shipped in late 2021. Nearly four years later, we finally have the long-anticipated redesign (announced earlier this year). The updated menu now features a single-page view, with all your pins and apps on one scrollable page. You can change the list of all apps between three variants: list, grid, and category. More importantly, you can now hide the recommended section in the Start menu settings (one of the most requested Start menu-related changes). The new Start menu is available in this week's Dev and Beta update. However, like always, Microsoft is rolling out changes gradually, which means you might not have the lucky ticket even on the latest build. If you do not want to wait, you can force-enable the new Start menu and its Phone Link button using a few commands in the ViVeTool app. Here is how to do that: Download ViveTool from GitHub and unpack the files in a convenient and easy-to-find folder. Run Command Prompt as Administrator and navigate to the folder containing the ViveTool files with the CD command. For example, if you have placed ViveTool in C:\Vive, type CD C:\Vive. Type vivetool /enable /id:47205210,49221331,49381526,49402389,49820095,55495322,48433719 and press Enter. Restart your computer. As usual, keep in mind that stuff in preview builds is less stable, so be aware of the risks of running preview builds. While Microsoft is not saying when the new Start menu will be available to all users, it will probably not take too long before it shows up in Release Preview and non-security updates. By the way, if you are curious, check out some of the prototypes that Microsoft considered when designing the new Start menu. Credit for the IDs goes to @phantomofearth on X.
    • reddit's "bottom of the barrel" > 99% of neowin front page "news"
  • Recent Achievements

    • Week One Done
      IAMFLUXX earned a badge
      Week One Done
    • One Month Later
      Æhund earned a badge
      One Month Later
    • One Month Later
      CoolRaoul earned a badge
      One Month Later
    • First Post
      Kurotama earned a badge
      First Post
    • Collaborator
      Carltonbar earned a badge
      Collaborator
  • Popular Contributors

    1. 1
      +primortal
      505
    2. 2
      ATLien_0
      268
    3. 3
      +FloatingFatMan
      234
    4. 4
      +Edouard
      201
    5. 5
      snowy owl
      162
  • Tell a friend

    Love Neowin? Tell a friend!