Home | Site Map | Cisco How ToNet How To | Wireless |Search | Forums | Services | Donations | Careers | About Us | Contact Us|

System error 64 specified network name is no longer availabl

RRAS, VPN, TS/RDP, Routing and remote Access.

System error 64 specified network name is no longer availabl

Postby chicagotech » Fri May 09, 2008 7:41 am

I agree with Bob. If your site to site link is working, you simply have
two subnets joined by an (slow) IP router. If you have installed WINS and
have all the machines in both sites set as WINS clients the browser service
should work fine. Browstat is the tool to troubleshoot the browser service.


> Setup WINS is the solution. You may want to use browstat.exe to
> troubleshooting. Or these search results may help.
>
> Computer Browser
> The computer browser is to display a directory of all known computers
> or domains that the computer can reach. The purpose of the browser service
> is to ...
> www.chicagotech.net/browser.htm - Similar pages
>
> Troubleshooting computer browsing issues
> The Computer Browser service on local computer started and stopped ·
> The Computer Browser service terminated with the following error: This
> operation ...
> www.chicagotech.net/computerbrowsingissues.htm
>
>
> --
> Bob Lin, MS-MVP, MCSE & CNE
> Networking, Internet, Routing, VPN Troubleshooting on
> http://www.ChicagoTech.net
> How to Setup Windows, Network, VPN & Remote Access on
> http://www.HowToNetworking.com

>> Hello,
>>
>> I've been trying to fix a weird problem with windows network across
>> sites.
>> Firstly let me describe my configuration:
>>
>> There are only two sites.
>>
>> On each site there is a domain controller, one being the PDC. On the
>> other
>> site there is an additional server running Terminal Services and also
>> some
>> shares.
>>
>> There are a number of Windows XP workstations on each site, and one Vista
>> workstation (we're testing our software works on it).
>>
>> There is a network-level VPN connecting the two sites together. Each
>> site
>> has its own 192.168.x.y subnet.
>>
>> Here's the problem:
>>
>> If I log onto a XP workstation, I can't connect to any file shares stored
>> on
>> a server on the foreign site, however:
>>
>> I can ping perfectly well across sites.
>>
>> I can use terminal services without difficulty.
>>
>> I can access file shares through \\192.168.x.y, but not \\DNS-name.
>>
>> but ping DNS-name works OK.
>>
>> If I do net use x: \\svr\share it says System error 64, "The specified
>> network name is no longer available". (net use \\192.168.x.y\share works
>> fine but takes ages to complete)
>>
>> Servers and Vista workstations work without problems.
>>
>> I have tried:
>>
>> Configuring WINS which appears to be working.
>>
>> Updated Veritas on one server which was alleged to cause some problems in
>> some limited cases.
>>
>> Restarted everything.
>>
>> Restarted everything again.
>>
>> Restarted everything again.
>>
>> Removed much hair through tearing.
>>
>> Restarted everything again.
>>
>>
>> Any suggestions would be much welcomed - please feel free to ask
>> questions
>> if I've missed some vital detail.
Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on http://www.HowToNetworking.com
chicagotech
Site Admin
 
Posts: 7096
Joined: Mon Nov 27, 2006 1:24 pm
Location: Chicago USA

Re: System error 64 specified network name is no longer availabl

Postby chicagotech » Mon Nov 06, 2017 5:06 pm

If it is MV, Disable each of the following TCP offload options, and then click OK:
•IPv4 Checksum Offload
•Large Receive Offload
•Large Send Offload
•TCP Checksum Offload
Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on http://www.HowToNetworking.com
chicagotech
Site Admin
 
Posts: 7096
Joined: Mon Nov 27, 2006 1:24 pm
Location: Chicago USA

Re: System error 64 specified network name is no longer availabl

Postby chicagotech » Mon Nov 06, 2017 5:23 pm

In our case, it is SMB 1.0/CIFS File Sharing Support issue. By default, Windows 10 and server 2012 SMB 1.0/CIFS File Sharing Support is disabled.

Most our workstations can access a external USB drive except some windows 2012 R2 server. Enabling SMB 1.0/CIFS File Sharing Support resolve the problem.

To enable SMB 1.0/CIFS File Sharing Support go to Turn Windows features on or off on client OS and go tot add Roles in the server.
Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on http://www.HowToNetworking.com
chicagotech
Site Admin
 
Posts: 7096
Joined: Mon Nov 27, 2006 1:24 pm
Location: Chicago USA


Return to VPN, TS and Remote Access

Your Ad Here

Who is online

Users browsing this forum: No registered users and 3 guests