sonicwall netextender no internet access

What tipped me off was that 191, which he was connected to when we were on the phone troubleshooting, had a lease expiration set to tomorrow, 5/24/13, while the rest were all the 30th or later. I suppose what I should've been looking for was whether the MAC address listed for the DHCP's leased IP matched his network card. Not necessarily a VPN-DHCP conflict as a rule, but instead an individual IP conflict that's resolved by setting the VPN's target IPs outside the range of IPs that might be leased at random to other machines. My home Internet performs about 13Mbps Down and 2.5Mbps up, the office is 60Mbps Down and 15Mbps up. Still from home, using a new brand computer with Windows 7 64, netextender will perform up to 1.1 Mbps Down and up. He'd said it was working fine previously, and that was because in the screenshot he'd sent me of it working, he had been given 195, an unleased address on the DHCP. At home, using a computer with XP SP3, netextender can do up to 256Kbps Down and 100Kbps Up when connecting to the office. What I think was causing it is we have devices leased at 190 and 191, and when I tried to ping him, I was actually pinging those devices. To fix it, I set the VPN range to 70-89, outside of the DHCP range. The IP range selected for the VPN services (190-199) was entirely within the range of Server 08's DHCP range (.150-.255). The bad news is, if person A has the file open, person B can't tell that person A has it open.I found the answer. Then when they are done editing, it will push the copy back to the server as a single one shot file. This will open a local copy on the PC while the VPN is working. The other possible fix is if the share is not to big, and your clients only need access to parts of the share(s), you can turn on 'available off line' from Windows. Also, it does not matter who's VPN you use, they all can have this issue with SMB file shares.

Sorry, this is not ideal, but it's what I've seen before. Or tell them to copy to the file locally, work on it, then push it back. Your fix for this might be to use Remote Desktop to a local PC/Server to handle file shares.

If so, you might find that a person on a 'not go good' ISP/carrier is having more issues than the higher ups who pay for a better internet connection. It deals with SMB being very 'chatty', and one hold up, lost packet, and the share shuts off without so much as a goodbye. You can google/duckduckgo/bing where almost every VPN has an issue with SMB. For IPSec VPN, SonicWall Global VPN Client enables the client system to download the VPN client for a more traditional client-based VPN experience. Ok, this is different, and it's not a Sonicwall issue, but a SMB issue. For SSL VPN, SonicWall NetExtender provides thin client connectivity and clientless Web-based remote access for Windows, Windows Mobile, Mac and Linux-based systems.

Sonicwall netextender no internet access