There may be multiple causes for this error. Suggestions
1. Double check the NIC settings.
2. Make sure you have latest NIC drive, especially in server2 with 64bit.
3. It could be MTU issue too.
The following search results may help too.
a.. specified network name is not longer available
System error 64 - The specified network name is no longer available.
System error 53. The network path was not found. Event ID 3013 -
Description: The ...
http://www.chicagotech.net/troublesh...temerror64.htm - Similar
a.. network name is not longer available
But when I try to copy a file from my PC to the Server, it hangs for a
minute and then returns "The Network name is no longer available" (we're
talking 1mb ...
www.chicagotech.net/Q&A/vpn17.htm
--
Bob Lin, Microsoft-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
"snagrat" <(E-Mail Removed)> wrote in message
news:92248b7a-e595-4234-b587-(E-Mail Removed)...
> Hi.
>
> I have managed to set up many VPNs to our clients before for users to
> access shares from at home. Everything works OK on many sites.
>
> However this current one I am having isues with. There are two
> servers:
>
> Server1 - AD, DHCP, DNS, Win2008 x86 SP2
> Server2 - File Server, RRAS/NPS Win2008 x64 SP2
>
> The VPN connections work, the user authenticates and show as connected
> in RRAS. It is possible to ping both servers and get a reply.
>
> If I go to \\server1 then I get to see all the shares on that server.
>
> However if I go to \\server2 (or via IP address) then I get an error
> saying "The specific network name is no longer available". The user
> has access to the shares, even if I try a specific share nameit
> doesn't work.
>
> I thought itmay be a problem with my rules so I went back to basics
> but no joy. Even imported rules from a working VPN server but still no
> luck.
>
> Has anyone got an idea as to why this is happening??
>
> Thanks all