Uncategorized

We had a call from a customer with 3 surface pros that were no longer charging. We discovered it was a known problem. The fix is to go into the “Device Manager” and uninstall the battery. Make sure to not remove the AC device. Restart and the correct driver will re-install. There is one more step to run a fix. This will keep this issue from coming back. We found the fix on this page.

https://support.microsoft.com/en-us/help/4023536/surface-surface-battery-wont-charge

Let us know if this helped you…

EDIT: The entire point of the SHAREUSER account was to do one of two things. Either a) allow remote scanning across this particular client’s VPN. or b) authenticate with a shared network folder across the VPN without posing a security risk due to the amount of floaters who use this PC. This is now deprecated in case B. In case A, you want to keep the credentials, due to remote scanning still relying on corporate resources.

Background:

if you have a network share that you access often, instead of having to type the IP in the address all the time, you can add it to the hosts file in %windir%\System32\drivers\etc\ like so…

192.168.1.5          myserver

…then for every time you type \\myserver in windows explorer window, it’d be the same as typing \\192.168.1.5

days, months, years go by and now you can’t access the shared folder via it’s IP \\192.168.1.5. You may still be able to access it via \\myserver but not via ip.

Solution:

Open Credential Manager in Control Panel and look for the IP address under Windows Credentials (it would have a username as XXXX\SHAREUSER);  click “Remove from vault”

Had a customer with Outlook 2007 that started receiving this message after a recent Microsoft update.

I used the advice from this video to help solve the issue.

https://www.youtube.com/watch?v=uFnXPaMxyUo

Let us know if this helps you…

Scenario:

Downloaded Sonicwall Firewall (multiple versions 4.10.2.0428, 4.10.1.0317, 4.9.22.0822, 4.9.14.0427, 4.9.9.1016) and tried one at a time. The connection is solid. The client connects to the home office just fine, you CAN ping resources via IP, but you CAN’T browse to intranet site although you can ping it.

Trying to navigate to an intranet site using Chrome or Internet Explorer, you’d get the following error:

After spending countless hours troubleshooting in the wrong direction, the simple and only resolution was to enable Jumbo Frame for the NIC card in use. 

Here’s how…

1. Open ‘Network and Sharing Center‘ – (you can type that in the start menu)
   
2. Click ‘Change adapter settings’ from the left pane
3. Right-click the NIC for which you want to enable jumbo frames and select ‘Properties‘.
   
4. Click on ‘Configure‘ Under the Networking tab
   
5. Click on the ‘Advanced‘ tab
6. Select Jumbo Frame on the left and change the value from disabled to the desired value, I put mine at 9kB MTU
   
7. Then click ‘OK‘

That’s all!

EDIT: This issue is caused by Sonicwall’s Global VPN client not playing nicely with certain ethernet drivers, namely intel and realtek. The above solution might work, however experience says that it does not more often than it does. A workaround for this issue is to install an external wireless adapter or network card that requires different drivers, preferably onces that play nicely with Sonicwall’s garbage VPN client.