Link to home
Start Free TrialLog in
Avatar of Alex DeViney
Alex DeViney

asked on

Network Share Issues

Hello,

I have a problem occurring with one of my users machines network shares. I cannot C$ in to the machine and cannot seem to figure out why. The error I receive is "The specified network name is no longer available". I can ping the machine fine and VNC in to it with no issue.

This is a Windows 7 Enterprise x64 Dell T3600.

I will list all the troubleshooting I have done so far:

  • Reset the network settings including a flushdns
  • Gave it a static IP to see if there was a conflict with the IP address
  • Removed and re-added to the domain
  • Deleted and re-created the C$ share
  • Updated the NIC Drives
  • Updated the BIOS
  • Swapped out the NIC
  • Tried different network ports
  • Done a winsock reset
  • Turned off all firewalls
  • Turned off/on network sharing
  • Did a telnet 445 test (came back good)
  • Checked the clock time on DC to ensure was not different
  • Enabled LM and NTLM sessions from within the LAN Manager Authentication

I cannot re-install windows on this machine because it contains a piece of software that cannot be re-installed. I tried to do a system restore but it was disabled so that is not an option either. This had been working for months with no issue until two days ago and I have been wracking my brain over what it could be.

Any help would be much appreciated.
Avatar of Fethi ABASSI
Fethi ABASSI
Flag of Tunisia image

Try with:
Disabling Ant-virus
Entering on Windows Safe mode with network
Changing IP address
You said you could pint the computer but I don't see where you mention how you access/address the computer.

Are you using
\\[computername]
or are you using
\\[ip_address]  ?

I'd try the \\[ip_address] if you haven't done this.
Avatar of Alex DeViney
Alex DeViney

ASKER

I tried safe mode, no good.

As far as the ping, I can do it via IP but not computer name. However on the share I have tried both IP and  computer name on share, neither have worked.
If ping doesn't work with computername then there's an issue with name service.
This implies that ONLY the ip address will work .. if that.
Sorry, I stand corrected. Name does work along with IP. We had a brief outage about 20 minutes ago when I was doing my testing. I have confirmed the name does resolve over PING.
disabling IPv6 on your NIC Card !
Will try that now and let you know.
No luck with IPv6 off. Not sure if it is worth mentioning but I cannot even access the share ON THE MACHINE that is having the issue. Obviously I can get to C:\ manually but if I try \\computername\c$ from the machine or another domain machine, I receive the error. I think something is broken with the actual windows share service.

I know back in the 95/98 days you could actually uninstall/re-install the service but I do not think that is possible on Windows 7.

Thoughts?
Did you try to access it using the IP instead of the computer name? And what are the DNS server settings like? Internal servers only?

The antivirus mention is a solid suggestion. Try that as well.
Yes I have tried as mentioned above, IP does not resolve. I have also disabled the antivirus as well and killed the service, no change.

All other machines on the domain are able to get to the share, I do not think it is a DNS server issue but something with the actual machine.
1. Try command line:
Sfc /scannow
I ran that and says it found corrupt files and successfully repaired them. I have attached the log file to this comment. However, after a reboot no change in the share.
CBS.log
ASKER CERTIFIED SOLUTION
Avatar of Fethi ABASSI
Fethi ABASSI
Flag of Tunisia 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
Which antivirus do you have? And does that machine have issues on the internet at all?
Let me test the services and SMB first.

We have webroot and aside from the share, no internet issues at all.
SMB worked!!!

Thank you Fethi!!
This was the answer I needed, SMB was disabled and as soon as I enabled it via powershell, I could c$ in.