7

Setup: Computer A has a file share called "ABC" with full control for a specific user X in the given domain. OS on all machines: Windows Server 2008 R2 with no antivirus software

A service running on Computers B and C logged in as user X need to write to this share "ABC" on computer "A".

From time to time, the share "abc" will be visible only to computer B and not to computer C unless it is rebooted. But the share can be accessed sometimes (again very random) if I use \ipaddress\abc from computer C instead of \hostname\abc.

Also when this happens, we cannot establish a sql server connection from service to computer A from computer C.

SO I have checked the usual suspects from other related questions in this forum:

  1. No windows credentials are cached on the target and client computers.
  2. nslookup correctly displays the domain controler ip and the target computer's ip.
  3. When I run tracert from the client computer, target computer is reached in 1 hop.
  4. When I use net view targetcomputer, I get System Error 53. I also flushed and registered dns from the computer C with no success.

I am out of ideas at this point other than rebooting. and I can't rely on rebooting since we can only reboot during maintenance hours. Any help is very appreciated.

  • 2
    You need to sniff the traffic from "Computer C" during the outage. This is going to tell you a lot about what's going on. Wireshark will be your friend for this one for sure. – Evan Anderson Oct 28 '14 at 0:06
  • Is the error you get at point 4 a BSOD error, or something else? – Davidw Oct 28 '14 at 1:02
  • I ran wireshark on Computer C, but not sure what to look for. Also I created another share on Computer A and I could access it without any problem from computer C. On the wireshark trace, I am getting OBJECT_STATUS_NOT_FOUND for some desktop.ini file. But I got the same trace accessing the other new share too. – user2608613 Oct 28 '14 at 22:26
  • The error I get at point 4 is from cmd line when I issued net view targetcomputer. SO today I restarted computer C and I can view the share on computer A but I cannot view its contents. i.e net use targetcomputer/share can be mapped to a drive. But when I try to access the drive, it errors out. – user2608613 Oct 28 '14 at 22:28
  • 1
    Also, when you're having the problem on computer C, can you access shares (and SQL servers if you have others) on computers others than A without any trouble? – I say Reinstate Monica Oct 30 '14 at 1:35
1

Sounds like a DNS issue to me. To confirm, I'd add server name and IP to the hosts file on the computer with issues and see if that resolves the problem.

  • 1
    It seems to be a DNS issue but the ping "hostname " works though. I can access the remote server using ipaddress, so that would mean adding the hosts entry would work. But we do not want to add host entries as there are quite a few servers and they all can talk to each other. – user2608613 Dec 18 '14 at 19:46

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.