Howcome I continue to ping by IP and by name but MAP a shared folder establishes and then after lets say one hour map network drive disconnect and is not accessible any more.
Office:
I have an small office that has one windows 2012 R2 Standard server (which is a Domain controller too .) with several other workstations and all seems to works fine.
The office use Sonic wall TZ300w Firewall.
Home Office:
I have an home office with windows 7 Pro that was joined with the Domain prior to be moved and relocated to Home office.
The Home Office use Sonicwall TZ100
The Sonicwall GVC (VPN Client) is used to connect the windows 7 Pro to the Office. Upon established connection, I can ping the server or any other computer by IP and also by Name, in addition I can Map the resources of the shared folder on the server.
The above statement will be true from the office and I can connect to the windows 7 shared folder (MAP) and can ping by IP and by name. However after a while everything stay the same except the map driver to windows 7 will break and is not available. I still can ping the the remote windows 7 by name and IP but \\192.168.168.5 or \\homebackup will fail.
Can someone please assist where the problem might be (TZ100, TZ300, GVC, Server)?
BackupChart.pdf
I have an small office that has one windows 2012 R2 Standard server (which is a Domain controller too .) with several other workstations and all seems to works fine.
The office use Sonic wall TZ300w Firewall.
Home Office:
I have an home office with windows 7 Pro that was joined with the Domain prior to be moved and relocated to Home office.
The Home Office use Sonicwall TZ100
The Sonicwall GVC (VPN Client) is used to connect the windows 7 Pro to the Office. Upon established connection, I can ping the server or any other computer by IP and also by Name, in addition I can Map the resources of the shared folder on the server.
The above statement will be true from the office and I can connect to the windows 7 shared folder (MAP) and can ping by IP and by name. However after a while everything stay the same except the map driver to windows 7 will break and is not available. I still can ping the the remote windows 7 by name and IP but \\192.168.168.5 or \\homebackup will fail.
Can someone please assist where the problem might be (TZ100, TZ300, GVC, Server)?
BackupChart.pdf
ASKER
Hello,
I believe I was miss understood or I did not get it. From client site I have no problem. I ping by name, IP and I can map to resources on the server at the office and the GVC is very much stable and the environment was working for more than a year and still works fine.
From office, the shared folder on client resource become the problem. When I reboot the server I can map to a shared folder on GVC computer and after a while that map connection drops and I can not see the client any more while I can ping the client by name and by IP.
I must say your solution is perfect but they want to use GVC rather site-to-site.
Thank you
I believe I was miss understood or I did not get it. From client site I have no problem. I ping by name, IP and I can map to resources on the server at the office and the GVC is very much stable and the environment was working for more than a year and still works fine.
From office, the shared folder on client resource become the problem. When I reboot the server I can map to a shared folder on GVC computer and after a while that map connection drops and I can not see the client any more while I can ping the client by name and by IP.
I must say your solution is perfect but they want to use GVC rather site-to-site.
Thank you
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
The this action solve the problem
A better more stable solution would be to create a S2S (Site-to-Site) VPN between the two SonicWALLs especially in a backup scenario. In this solution you'd have Keep Alive heartbeats that persist so the tunnel remains up and the mapping does as well.
What you are experiencing is most likely due to the virtual mapping of the C2S (Client-to-Site) VPN in Windows especially if the home computer is no longer on the domain. IPsec does not encapsulate NetBIOS broadcast traffic, unless the IP Helper is used to explicitly direct these broadcasts to a particular zone. Otherwise, when mapping a drive you should use the IP address opposed to FQDN for your particular environment.
Let me know if you have any questions!