System error 53 windows 7 samba

You may have to wait up to 2 minutes to retry registrations. The network path was not found. What can I do? It's probably worth looking into.

Not knowing your situation, this might not be practical--for example, if it's a production server and the stuff should have been available yesterday, don't play there. Did early assembly games use hardcoded memory locations? Sorry this didn't help. Thanks for your feedback. Crutchfield Jim. They both have BitDefender Internet Security running, and I have made sure that the firewall allows all traffic from the local network.

Windows Firewall is turned off on both machines. The Win7 laptop can see the Vista machine, access shared files, etc. The Vista machine can see the Win7 laptop in Explorer and on the network map, but it can't browse the laptop or access shared files on it.

The network path was not found. Any other suggestions? What other info can I give you? Thanks for any help. This thread is locked. Step 2: If the Ping command returns all packets and no packets are lost, it means your network is set up correctly.

However, if an error occurs or you do not receive a response when pinging the server, the connection settings are incorrect. Step 3: Troubleshoot according to the results of the ping test. If not, you can try the next method. Then you can try disabling the security software and check if it was causing the issue. There are plans for replacing all the desktops this year so we have to be sure. Any suggestions are welcome. Please check if you can ping from the win10 to server R2 computer and server R2 to win 10 computer.

Please remember to mark the replies as answers if they help. If you have feedback for TechNet Subscriber Support, contact tnmff microsoft. I can ping both ways. DNS name resolution works both ways. The only service that is inaccessible on the server is File and Print Sharing, and only from that one computer.

But no access to shared resources. It's driving me nuts! Please Note: Since the web site is not hosted by Microsoft, the link may change without notice. Microsoft does not guarantee the accuracy of this information. There are 16 other computers on the network that do have access to the shares and the printers on the server.

The Windows 10 laptop is the only system that does not. Note that that same laptop has no problems accessing shares on the Samba server. So, in theory, there are is no reason why this Windows 10 laptop cannot communicate with the Windows R2 server only for File and Print Services.